yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

*** This bug is a duplicate of bug 1733736 ***
    https://bugs.launchpad.net/bugs/1733736

** This bug is no longer a duplicate of bug 1463856
   Cinder volume isn't available after instance soft-deleted timer expired while volume is still attached
** This bug has been marked a duplicate of bug 1733736
   reclaim_instance_interval causes dirty attached volume

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1555045

Title:
  Volume wouldn't been detach after delete with
  reclaim_instance_interval

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  Nova can assign seconds to reclaim_instance_interval option which is Interval in seconds for reclaiming deleted instances.
  If users delete server which had attached volumes ( or boot from volume), those servers will been disappear in server list.
  Their volumes would still in use and it will have "Attached to **** on /dev/vdb".
  After interval seconds, nova compute would begin to reclaim those servers.
  But it will not release those volumes.
  This cause those volumes became "Attached to None on /dev/vdb".
  Users need to reset volumes state then can use they again.
  But those volumes will have "Attached to None on /dev/vdb Attached to **** on /dev/vdb""

  We should not only actually delete instances but also detach volumes
  in reclaiming instances.

  My environment was deployed by devstack which is upstream code.
  devstack: 6fff3cc03589cb0fdf02b4bedf1c35bcb000f28d
  nova-client: 3.3.0
  nova: 3d7e403cc7a5d9ebcd9a011d6c2055bfbf56cb05

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1555045/+subscriptions