| 2016-09-20 14:48:15 |
Sylvain Bauza |
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... |
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.
https://github.com/openstack/nova/commit/be553fb15591c6fc212ef3a07c1dd1cbc43d6866
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... |
|
