Different behavior when user gets list of resources of non-existent stack by stack id and name
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Invalid
|
Undecided
|
Pradeep Kumar Singh | ||
openstack-api-site |
Fix Released
|
Low
|
Pradeep Kumar Singh |
Bug Description
Steps to reproduce:
1. heat stack-create --template-file test_stack.yaml -P network=net_id -P InstanceType=
2. heat stack-list (execute to be sure that stack was created)
3. heat resource-list test (execute to check that all stack resources were created and we can get list of resources using stack _name_)
4. heat resource-list <stack_id> (execute to check that all stack resources were created and we can get list of resources using stack _id_)
5. heat stack-delete test
6. heat stack-list (execute it to be sure that stack was deleted)
7. heat resource-list test (user got: Stack not found: test)
8. heat resource-list <stack_id> (user got list of stack resources with DELETE_COMPLETE statuses)
Observed result:
User has to see "Stack not found" exception after execution step 8
summary: |
- Different behavior when user get list of resources of non-existent stack - by stack id and name + Different behavior when user gets list of resources of non-existent + stack by stack id and name |
Changed in heat: | |
assignee: | nobody → pradeep kumar singh (pradeep-singh-u) |
Changed in heat: | |
status: | In Progress → Invalid |
Changed in openstack-api-site: | |
assignee: | nobody → pradeep kumar singh (pradeep-singh-u) |
status: | New → In Progress |
importance: | Undecided → Low |
milestone: | none → liberty |
I can't see how this behaviour can be any different. Stacks are soft-deleted so are still accessible via UUID. Also we enforce unique stack names on non-deleted stacks.
I'm inclined to just document that deleted stacks can only be fetched via UUID.