5426350348
The following 2 scenarios could result in an instance with incorrect port binding and cause subsequent rebuilds to fail. If an evacuation of an instance fails part way through, after the point where we reassign the port binding to the new host but before we change the instance host, we end up with the ports assigned to the wrong host. This change adds a check to determine if there's any port binding host mismatches and if so trigger setup of instance network. During recovery of failed hosts, neutron could get overwhelmed and lose messages, for example when active controller was powered-off in the middle of instance evacuations. In this case the vif_type was set to 'binding_failed' or 'unbound'. We subsequently hit "Unsupported VIF type" exception during instance hard_reboot or rebuild, leaving the instance unrecoverable. This commit changes _heal_instance_info_cache periodic task to update port binding if evacuation fails due to above errors so that the instance can be recovered later. Closes-Bug: #1659062 Related-Bug: #1784579 Co-Authored-By: Gerry Kopec <gerry.kopec@windriver.com> Co-Authored-By: Jim Gauld <James.Gauld@windriver.com> Change-Id: I75fd15ac2a29e420c09499f2c41d11259ca811ae Signed-off-by: Jack Ding <jack.ding@windriver.com> |
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| gate | ||
| nova | ||
| 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 | ||
| 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: