
We just recently enable this scenario test [1] but it's causing the nova-next job to intermittently fail because the nova-next job runs the tempest compute API and scenario tests concurrently (unlike the tempest-full job which runs the API tests concurrently and then the scenario tests serially) and the scenario test is creating a public shared network which causes the compute API tests, when creating a server without specifying a network, to fail since nova doesn't know which network to use. So for now just blacklist the scenario test until the related tempest bug is fixed. [1] https://review.opendev.org/#/c/697180/ Change-Id: Ie0e6136e88bedb2c4c6d0b742319627d58da147e Related-Bug: #1844568
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: