f292a92a89
This adds a functional regression recreate test for bug 1837955 which was introduced with change Iae904afb6cb4fcea8bb27741d774ffbe986a5fb4 in the Queens release. In this scenario, the primary (and potentially alternate) hosts for a server build fail and reschedule to conductor. Eventually all alternate hosts are exhausted and specifically trying to claim allocations against the alternates fails, probably because between the time of initial scheduling and rescheduling something else took up the spare capacity on the alternate host. When this happens, MaxRetriesExceeded is raised but the instance is stuck in BUILD status rather than set to ERROR status with a fault message. NOTE(mriedem): In this backport the test is changed slighty since change Id8b5c48a6e8cf65dc0a7dc13a80a0a72684f70d9 is not in Rocky so the ProviderUsageBaseTestCase.neutron attribute does not exist. Change-Id: I4ca64dd60d883356880680fb1f04cee4136c2e00 Related-Bug: #1837955 (cherry picked from commit |
||
---|---|---|
api-guide/source | ||
api-ref/source | ||
contrib | ||
devstack | ||
doc | ||
etc/nova | ||
gate | ||
nova | ||
placement-api-ref | ||
playbooks/legacy | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.stestr.conf | ||
.zuul.yaml | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MAINTAINERS | ||
README.rst | ||
babel.cfg | ||
bindep.txt | ||
lower-constraints.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: