Convergence stack stuck in update/rollback in progress for concurrent update
Bug #1528560 reported by
Rakesh H S
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Anant Patil |
Bug Description
Consider the following scenario:
template1:
rsrc_A
template2:
rsrc_B
NOTE that when updating with template2, rsrc_A is DELETE_IN_PROGRESS and taking time to delete.
In the mean time another update is triggered:
template3:
rsrc_A
Now since rsrc_A is still in DB, while calculating graph we need not store the resource in DB again.
However there is possibility that after calculating the graph template2 successfully deletes rsrc_A (which clears the rsrc from DB)
Now template3 will be stuck in progress because of:
https:/
Changed in heat: | |
assignee: | nobody → Rakesh H S (rh-s) |
Changed in heat: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → mitaka-3 |
Changed in heat: | |
milestone: | mitaka-3 → mitaka-rc1 |
Changed in heat: | |
milestone: | mitaka-rc1 → newton-1 |
Changed in heat: | |
assignee: | Rakesh H S (rh-s) → Anant Patil (ananta) |
Changed in heat: | |
assignee: | Anant Patil (ananta) → Rakesh H S (rh-s) |
Changed in heat: | |
assignee: | Rakesh H S (rh-s) → Anant Patil (ananta) |
Changed in heat: | |
assignee: | Anant Patil (ananta) → Rakesh H S (rh-s) |
Changed in heat: | |
assignee: | Rakesh H S (rh-s) → Anant Patil (ananta) |
Changed in heat: | |
assignee: | Anant Patil (ananta) → Rakesh H S (rh-s) |
Changed in heat: | |
assignee: | Rakesh H S (rh-s) → Anant Patil (ananta) |
Changed in heat: | |
milestone: | newton-1 → newton-2 |
To post a comment you must log in.
While searching for best candidate from DB to represent a resource from current template, we should ignore the ones marked for deletion and add a new resource in DB. The creation of this new resource should depend on deletion of old resource which was marked for deletion.