Andrew Laski
9b090aeb7e
When booting an instance there is logic in the conductor to check if a delete has been issued. This is done by looking for a BuildRequest object and discontinuing the build if it's not found. However the conductor then deletes the BuildRequest so a reschedule attempt will not find the BuildRequest object. This incorrectly stops the reschedule. The filter_properties dict is updated with the number of scheduling attempts for each reschedule so by looking at the value found there we know if a reschedule is being attempted. If that's the case then bypass the logic that checks for, and deletes, the BuildRequest object. Change-Id: Ibf28d1d8f54703b465ccc497281419356cd0136e Closes-Bug: 1628530
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
and OpenStack Ironic.
OpenStack Nova is distributed under the terms of the Apache
License, Version 2.0. The full terms and conditions of this
license are detailed in the LICENSE file.
API
---
To learn how to use Nova's API, consult the documentation
available online at:
http://developer.openstack.org/api-guide/compute/
http://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs,
please see:
http://www.openstack.org/appdev/
http://developer.openstack.org/
Operators
---------
To learn how to deploy and configure OpenStack Nova, consult the
documentation available online at:
http://docs.openstack.org
For information about the different compute (hypervisor) drivers
supported by Nova, please read:
http://docs.openstack.org/developer/nova/feature_classification.html
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:
http://bugs.launchpad.net/nova
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:
http://docs.openstack.org/developer/nova/