d75b995d03
Change I0c4ca6a81f213277fe7219cb905a805712f81e36 added more error handling to the _ensure_resource_provider flow but didn't account for @safe_connect returning None when calling _create_resource_provider in the case that nova-compute is started before placement is running. If that happens, we fail with a TypeError during the nova-compute startup because we put None in the resource provider cache and then later blindly try to use it because the compute node resource provider uuid is in the cache, but mapped to None. This adds the None check back in _ensure_resource_provider and if None is returned from _create_resource_provider we raise the same exception that _create_resource_provider would raise if it couldn't create the provider. Conflicts: nova/scheduler/client/report.py: entire method conflicted as provider_tree changes have not been backported. nova/tests/unit/scheduler/client/test_report.py - didn't conflict but referenced non-existant methods. Re-implemented based on test_ensure_resource_provider_create_fail changing mocked create_resource_provider to return None instead of raising an exception. Change-Id: If9e1581db9c1ae14340b787d03c815d243d5a50c Closes-Bug: #1767139 (cherry picked from commit |
||
---|---|---|
api-guide/source | ||
api-ref/source | ||
contrib | ||
devstack | ||
doc | ||
etc/nova | ||
gate | ||
nova | ||
placement-api-ref/source | ||
plugins/xenserver | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.testr.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-functional-py3.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: