Zaqar queue can be inadvertently deleted
Bug #1637304 reported by
Jason Dunsmore
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Low
|
Jason Dunsmore | ||
zaqar |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Zaqar creates queues lazily, which causes unexpected results in Heat.
To reproduce:
$ openstack stack create -t http://
$ openstack queue list
+------+
| Name |
+------+
| foo |
+------+
$ openstack stack create -t http://
$ openstack queue list
+------+
| Name |
+------+
| foo |
+------+
$ openstack stack delete --yes zaqar2
$ openstack queue list
(no output)
Deleting the zaqar2 stack causes the zaqar queue from the original zaqar1 stack to be deleted.
Changed in heat: | |
milestone: | ocata-1 → ocata-2 |
Changed in heat: | |
assignee: | Zane Bitter (zaneb) → Jason Dunsmore (jasondunsmore) |
Changed in heat: | |
assignee: | Jason Dunsmore (jasondunsmore) → Zane Bitter (zaneb) |
Changed in heat: | |
assignee: | Zane Bitter (zaneb) → Jason Dunsmore (jasondunsmore) |
status: | In Progress → Triaged |
Changed in heat: | |
milestone: | ocata-2 → ocata-3 |
Changed in heat: | |
status: | Triaged → Fix Released |
To post a comment you must log in.
Queues have been made to look like topics nowadays, so that behavior doesn't surprise me that much, but I can see how it can be confusing. It also a bit dangerous as you can lose messages. I'm not exactly sure what to do though. I don't think there is a bug in Zaqar. I can see 2 things in Heat:
1) Fail if the queue pre-exists in Heat. I don't think it's a backward compatible change, so we'd need to add a flag to get this behavior. But that's a good way to ensure that the queue belongs to the stack somewhat.
2) Don't delete the queue. It leads to some objects lying around, which is a bit sad.
What do you think?