eaf6340847
Change Ib984c30543acb3ca9cb95fb53d44d9ded0f5a5c8, which was added in Newton when cells v2 was optional, added some transitional code to the API for looking up an instance, which didn't rely on instance mappings in a cell to find the instance if the minimum nova-osapi_compute service version was from before Ocata. People have reported this being a source of confusion when upgrading from before Ocata, when cells v2 wasn't required, to Ocata+ where cells v2 along with the mapping setup is required. That's because they might have older nova-osapi_compute service version records in their 'nova' (cell) database which makes the API think the code is older than it actually is, and results in an InstanceNotFound error. This change does two things: 1. Adds a warning to the compute API code in this scenario to serve as a breadcrumb if a deployment hits this issue. 2. A nova-status check to look for minimum nova-osapi_compute service versions across all cells and report the issue as a warning. It's not an upgrade failure since we don't know how the nova-api service is configured, but leave that investigation up to the deployer. This is also written in such a way that we should be able to backport this through to stable/ocata. Change-Id: Ie2bc4616439352850cf29a9de7d33a06c8f7c2b8 Closes-Bug: #1759316
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: