When finish_revert_migration is called, the caller of finish_revert_migration already includes context as a parameter, but finish_revert_migration did not reuse this parameter and still re-generate the context inside finish_revert_migration, we should add context as a new parameter for finish_revert_migration so that the functions inside of it can reuse context when needed. For the function _create_domain_and_network in libvirt/driver.py, it set context as an optional parameter, but context isn't really an optional parameter for this method. We should always pass a context down because it might be needed somewhere inside _create_domain_and_network(). The patch includes two parts: 1) Add context as a new parameter for finish_revert_migration 2) Set context as a required parameter for _create_domain_and_network Change-Id: I72d131fc8dce903400e3080d51ba0fc0a1320751 Closes-Bug: #1251261
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
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