eb3b1c80c1
When detaching block devices on rebuild we only notify Cinder it's safe to detach a volume, but don't actually tell the driver to do that first. Closes-Bug: #1440762 Change-Id: I017bf749f426717dc76cf99a387102848fb1c541 (cherry picked from commit337471bc71) --------------------------------------------------------------------- squashed with another change that fixes a bug introduced in the first --------------------------------------------------------------------- rebuild: fix rebuild of server with volume attached This was meant to be fixed by I017bf749f426717dc76cf99a387102848fb1c541 , but it didn't take into account that BDM entry was destroyed, which caused the rebuild to fail when spawning the instance. Add a new parameter to detach_volume() to bypass destroying of BDM, as we just want to detach a volume first and then re-attach it again. A Tempest test is added in I50557c69b54003d3409c8e977966f5332f4fe690 to make sure this is actually tested in the gate. Closes-Bug: #1440762 Co-Authored-By: melanie witt <melwitt@yahoo-inc.com> Conflicts: nova/compute/manager.py NOTE(mriedem): In Kilo the detach_volume method was still using the @object_compat decorator. Change-Id: I9134fbf5ce72c32cca91de90001c09e00b4e19e8 (cherry picked from commit25f15b0bc3)
OpenStack Nova README
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMware, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs.
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.
Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities.
To keep updated with new developments in the OpenStack project follow @openstack on Twitter.
To learn how to deploy OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:
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:
Developers wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at:
Developers should also join the discussion on the mailing list, at:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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:
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.
-- End of broadcast