yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

-- 
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/1158942

Title:
  Volume detach fails after unrescuing a instance after trying to detach
  while instance in rescue state doesn't work.

Status in OpenStack Compute (Nova):
  Fix Released
Status in Tempest:
  Fix Released

Bug description:
  When an instance with a volume attached is brought into a rescue mode
  and a negative test is run against it to detach the volume it returns
  the expected error code. However if you attempt to detach the volume
  again after unrescuing the vm it will not detach properly. The volume
  state goes from detaching to in-use, and it is never detached.

  Steps to reproduce:

  1. Create a server and wait for it to get to ACTIVE state
  2. Create a volume and wait for it to get to AVAILABLE state
  3. Attach the volume to the server and wait for the volume to get to "IN USE" state
  4. Rescue the VM and wait for the VM to get to the "RESCUE" state
  5. Detach the volume from the server, which should fail with 409
  6. Unrescue the VM and wait for it to get to ACTIVE state
  7. Try to detach the volume from the Volume again from the server

  Watching the status of the volume it will go from detaching to in-use
  and remain there.

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