yahoo-eng-team team mailing list archive

[Sylvain Bauza <sbauza@xxxxxxx>]

Public bug reported:

https://bugs.launchpad.net/nova/+bug/1490236 was focusing on correcting
the volume-update API so that it was idempotent. Unfortunately, the
merged solution is introducing a huge regression by incorrectly
providing the old volume ID as the new attachment information.

Consequently, it's now impossible for an end-user to detach a volume if
some operator updated the BDM to point to a different volume.


Evidence here: http://paste.openstack.org/show/582248/


What's unfortunate is that the original bug is about to be worked around by just detaching/attaching the volume to the instance before swapping back...

** Affects: nova
     Importance: High
     Assignee: Sylvain Bauza (sylvain-bauza)
         Status: Confirmed


** Tags: newton-rc-potential volumes

** Tags added: volumes

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

Title:
  Volume detach is broken when using volume-update first

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  https://bugs.launchpad.net/nova/+bug/1490236 was focusing on
  correcting the volume-update API so that it was idempotent.
  Unfortunately, the merged solution is introducing a huge regression by
  incorrectly providing the old volume ID as the new attachment
  information.

  Consequently, it's now impossible for an end-user to detach a volume
  if some operator updated the BDM to point to a different volume.

  
  Evidence here: http://paste.openstack.org/show/582248/

  
  What's unfortunate is that the original bug is about to be worked around by just detaching/attaching the volume to the instance before swapping back...

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