Comment 2 for bug 1560300

Yeah, i was working on this before i submitted this bug. Sorry, i forgot to
assign to myself when submit it.

On Tue, Mar 22, 2016 at 3:06 PM, Wenzhi Yu <wenzhi_yu@163.com> wrote:

> Hi apporc, are you working on this?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1560300
>
> Title:
> nova soft-delete leaves "Attached to None" volumes
>
> Status in OpenStack Compute (nova):
> New
>
> Bug description:
> 1. version
>
> `git log -1`
> c4763d46fe76c524363a0cf55d1e8afe4bd23f53
>
> 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.manager [req-7bbc1701-fbce-41bc-8182-b2cbb6e5ac93
> None None] [instance: a3645529-6b11-437e-b1e4-773e87db7223] Ignoring
> EndpointNotFound: The service catalog is empty.
>
> 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_instance_interval in
> /etc/nova/nova.conf on both nova-controller and nova-compute nodes.
> reclaim_instance_interval=10, eg. This enables soft-delete feature.
>
> (2) Create an instance with this:
>
> nova boot --flavor xxx --block-device id=<image
> id>,source=image,dest=volume,size=<volume size>,bootindex=0 --nic net-
> id=<network uuid> test
>
> (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_instance_interval is ended, until then nova-compute are going
> to really terminate the instance]:
>
> "WARNING nova.compute.manager [req-7bbc1701-fbce-
> 41bc-8182-b2cbb6e5ac93 None None] [instance: a3645529-6b11-437e-
> b1e4-773e87db7223] Ignoring EndpointNotFound: The service catalog is
> empty."
>
> (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.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nova/+bug/1560300/+subscriptions
>

--
Regards,
apporc