de035bbfcc
This attempts to recreate the following scenario: 1) boot instance on ocata host where the compute service does not have a uuid 2) migrate instance 3) delete the ocata service (thus deleting the compute node) 4) start compute service with the same name 5) migrate instance to newly-created compute node 6) upgrade to pike where services.uuid data migration happens 7) list instances as admin to join on the services table The failure occurs when listing instances because the deleted service with the same name as the compute host that the instance is running on gets pulled from the DB and the Service object attempts to set a uuid on it, which fails since it's not using a read_deleted="yes" context. While working on this, the service_get_all_by_binary DB API method had to be fixed to not hard-code read_deleted="no" since the test needs to be able to read deleted services, which it can control via its own context object (note that RequestContext.read_deleted already defaults to "no" so the hard-coding in the DB API is unnecessarily restrictive). Change-Id: I4d60da26fcf0a77628d1fdf4e818884614fa4f02 Related-Bug: #1764556 (cherry picked from commit |
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| contrib | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| gate | ||
| nova | ||
| placement-api-ref/source | ||
| playbooks/legacy | ||
| releasenotes | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MAINTAINERS | ||
| README.rst | ||
| babel.cfg | ||
| bindep.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tests-py3.txt | ||
| tox.ini | ||
README.rst
Team and repository tags
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, OpenStack Ironic and PowerVM.
Use the following resources to learn more.
API
To learn how to use Nova's API, consult the documentation available online at:
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
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
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:
Other Information
During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: