StackAction can't be used with ephemeral heat
Bug #1936138 reported by
Rabi Mishra
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
In Progress
|
High
|
Unassigned |
Bug Description
With ephemeral heat we create a new stack every time and StackAction is always 'CREATE'. There is a bunch of deployment logic that exists today based on StackAction. Though the deployment actions are 'normally' expected to be idempotent, I've seen cases where re-run of some of those create issues.
We should fix those as the behavior would be different from before.
- Node network configuration based on StackAction[1]
- Restarting HA services during stack update[2]
- Run octavia_
There may be more that I've missed.
Changed in tripleo: | |
importance: | Undecided → High |
milestone: | none → xena-3 |
status: | New → Triaged |
Changed in tripleo: | |
status: | Triaged → In Progress |
To post a comment you must log in.
...or we could follow the path of the virtual stack update mark used for undercloud deployment via ephemeral heat