Abandon stack lacks locking
Bug #1301311 reported by
Steven Hardy
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Vijendar Komalla |
Bug Description
delete_stack in service.py contains locking logic, so we can avoid races where other actions are performed on a stack while it's being deleted.
abandon_stack does essentially the same thing, but lacks any locking, so there will be problems if one engine does an abandon while another is servicing some other lifecycle request, like a stack update for example.
Changed in heat: | |
assignee: | nobody → Vijendar Komalla (vijendar-komalla) |
Changed in heat: | |
status: | New → In Progress |
Changed in heat: | |
importance: | Undecided → High |
Changed in heat: | |
milestone: | none → juno-1 |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | juno-1 → 2014.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/86663
Review: https:/