Convergence: engine restart doesn't start provisioning of the in progress stacks
Bug #1559389 reported by
Anant Patil
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
On of the prime goals in convergence was that engine restarts/system reboots shouldn't affect the in progress stack. The stacks that were in progress should start from where they were left. The design of convergence makes sure that enough data is there in DB to re-provision the stack from where it was left.
This approach contradicts the approach taken in legacy engine, where the stack and resources are marked as failed and user intervention is required to re-provision the stack.
Changed in heat: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
Changed in heat: | |
milestone: | none → no-priority-tag-bugs |
To post a comment you must log in.