63c10d2d53
The create_incomplete_consumers online data migration was added in Rocky via change Id609789ef6b4a4c745550cde80dd49cabe03869a. That relies on hitting some tables in the API (or placement) database. The DB API code for that migration relies on a placement context manager which looks like it was regressed with change I2fff528060ec52a4a2e26a6484bdf18359b95f77 (also in Rocky). This results in a DB error trying to query the projects table but because of a generic try/except in _run_migration, the failure was missed in CI testing. Similarly, the nova-status upgrade check "_check_resource_providers" routine also uses the placement DB API context manager to count the number of compute resource providers in the API (or placement) DB, which is returning 0 because it's not using the proper DB connection. This was not caught in the nova-status CLI tests because they use the DatabaseFixture which *does* configure the global placement DB API context manager. This adds the configuration of the global placement DB API context manager so we can properly query the placement-related tables. The blanket problematic try/except from _run_migration is left as-is in this change but will be addressed in a separate patch. Integration testing of this fix is being performed with devstack: https://review.openstack.org/599847/ Change-Id: I9d97b7a904e2b7d15c763e2a067cc5909cc6c9c5 Closes-Bug: #1790701 Closes-Bug: #1790721
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: