
This test uses the ServersTestBase._wait_for_state_change method which waits for the status to change *from* what is provided, so when creating a server and waiting for the status to change from ACTIVE makes _wait_for_state_change return immediately since the status starts as BUILD. This can lead to a failure when the test tries to migrate a server that is in BUILD status rather than ACTIVE status. This fixes the test by using this version of _wait_for_state_change correctly, not to be confused with the same method in InstanceHelperMixin which is more accurate (it waits for the terminal status of the server operation). Change-Id: I56ff050194d0eb465b8c41795fdea2a8b0d764d6 Closes-Bug: #1850514
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: