Go to file
Balazs Gibizer a3c556963e Reproduce bug 1721652 in the functional test env
When bug 1709902 was fixed in I0df401a7c91f012fdb25cb0e6b344ca51de8c309
the fix assumed that when the _destroy_evacuated_instances() is called
during the init of the nova-compute service the resource tracker
already knows the compute node ids associated to the given compute
host. This is not true and therefore _destroy_evacuated_instances fails
with an exception and does not clean up the evacuated instance.

The solution for the original bug included a functional regression
test. However the functional test env is not capable of fully simulate
a nova-compute service restart. The service only stopped then started
again. This allows some in memory state of the compute service to
survive the simulated restart. This caused that the functional test
was not able to catch that the above described assumption is not
correct.

Related-Bug: #1721652
Related-Bug: #1709902
Change-Id: Icaf1bae8cb040b939f916a19ce026031ddb84af7
2017-10-12 08:45:49 +00:00
2017-09-07 15:42:31 +02:00
2017-08-07 16:00:10 +01:00
2017-01-04 11:05:16 +00:00
2014-05-07 12:14:26 -07:00
2012-02-08 19:30:39 -08:00
2010-05-27 23:05:26 -07:00
2017-09-07 15:42:31 +02:00
2017-10-09 08:24:40 -05:00
2017-03-02 11:50:48 +00:00
2017-03-02 14:30:16 +08:00

Team and repository tags

image

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:

Description
OpenStack Compute (Nova)
Readme 1.7 GiB
Languages
Python 97.6%
Smarty 2.3%
Shell 0.1%