Sylvain Bauza
ee2c0a00db
The below commit introduced a regression by updating the wrong value to
the attachment field when calling the volume-update swap operation where
the value is now the previous volume ID instead of the current volume
ID. It litterally makes it now imposible to detech the volume from the
instance once it has been swapped (even after the first swap).
Given the original issue can be worked around by detaching and then
attaching the volume before swapping back to the original volume, and
because the original bug only impacts an admin API while here it impacts
a user API, it's preferrable to directly revert the regression and then
work on the next cycle about the root problem rather than leaving the
change and try to fix something which is hard to troubleshoot, also
given the lack of functional tests around the volume operations.
This reverts commit be553fb155.
Change-Id: Ibad1afa5860d611e0e0ea0ba5e7dc98ae8f07190
Closes-Bug: #1625660
OpenStack Nova
==============
OpenStack Nova provides a cloud computing fabric controller,
supporting a wide variety of compute technologies, including:
libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer
and OpenStack Ironic.
OpenStack Nova is distributed under the terms of the Apache
License, Version 2.0. The full terms and conditions of this
license are detailed in the LICENSE file.
API
---
To learn how to use Nova's API, consult the documentation
available online at:
http://developer.openstack.org/api-guide/compute/
http://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs,
please see:
http://www.openstack.org/appdev/
http://developer.openstack.org/
Operators
---------
To learn how to deploy and configure OpenStack Nova, consult the
documentation available online at:
http://docs.openstack.org
For information about the different compute (hypervisor) drivers
supported by Nova, please read:
http://docs.openstack.org/developer/nova/feature_classification.html
In the unfortunate event that bugs are discovered, they should
be reported to the appropriate bug tracker. If you obtained
the software from a 3rd party operating system vendor, it is
often wise to use their own bug tracker for reporting problems.
In all other cases use the master OpenStack bug tracker,
available at:
http://bugs.launchpad.net/nova
Developers
----------
For information on how to contribute to Nova, please see the
contents of the CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed
in the HACKING.rst file, and pass all unit tests.
Further developer focused documentation is available at:
http://docs.openstack.org/developer/nova/