nova soft-delete leaves "Attached to None" volumes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
In Progress
|
Low
|
Anusha Unnam |
Bug Description
1. version
`git log -1`
c4763d46fe76c52
This is the version i used to test on my devstack, but in fact this bug exists from at least Juno release till now as i know.
2. Relevant log:
When a soft-delete is made on one instance boot from volume. There will be one line like this in nova-compute.log:
WARNING nova.compute.
This is because nova-compute uses a separate thread to do reclaiming instances job, which has an admin context. Since there is no service_catalog in admin context, nova-compute will raise exception EndpointNotFound while it tries to detach the volume.
3. Reproduce steps:
(1) Set a non-zero value for reclaim_
reclaim_
(2) Create an instance with this:
nova boot --flavor xxx --block-device id=<image id>,source=
(3) Delete the created instance:
nova delete test
(4) On the nova-compute node which hosted "test", there will be one warnging in nova-compute.log like this[NOTE: you should wait until the reclaim_
"WARNING nova.compute.
(5) if you list your volumes, you can find there still exists one volume attached to the deleted "test" instance. Check that on dashboard, the volume info says "Attached to None".
(6) If you try to delete the that volume with " cinder delete <volume id >". It says the volume is unable to be deleted because it is in attached status.
4. Expected result:
soft-delete detached instance's volume.
5. Actual result:
the volume is still left attached, and undeletable.
Changed in nova: | |
assignee: | nobody → Wenzhi Yu (yuywz) |
Changed in nova: | |
assignee: | Wenzhi Yu (yuywz) → apporc (appleorchard2000) |
Changed in nova: | |
assignee: | apporc (appleorchard2000) → Anusha Unnam (anusha-unnam) |
Hi apporc, are you working on this?