Dan Smith
20a9f9d740
Without this, we won't notice errors raised in the operation thread. Before1cd1c472bdthe unit test actually forced such errors to be raised even if in the real code it would never be raised. But that patch fixed the unit test fixture to be more realistic without realizing that such fixture error also means that we might have wrong assumptions about the code under test. Now we know that exception from the live migration thread was never raised back to the monitor thread. To improve logging we added a future.result() call after the main monitoring code finished. Also the code had complex way to signal the monitoring thread that the migration thread returned early by registering a callback on the migration thread and setting an event. This can be simplified to just check the status of the future of the migration thread. So the event and the callback is removed. All this was found because commit25fbf32f22missed to add the new parallel arg to the mock of guest.migrate() on master, but the exception was never propagated to the unit test on master. Backporting that change showed that in the old unit test env there is a valid exception. Co-authored-by: Dan Smith <dms@danplanet.com> Change-Id: I22683ad5118796c6406f80d8726053afa84fff56 Signed-off-by: Dan Smith <dansmith@redhat.com> Signed-off-by: Balazs Gibizer <gibi@redhat.com>
============== OpenStack Nova ============== OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), VMware and OpenStack Ironic. Use the following resources to learn more. API --- To learn how to use Nova's API, consult the documentation available online at: - `Compute API Guide <https://docs.openstack.org/api-guide/compute/>`__ - `Compute API Reference <https://docs.openstack.org/api-ref/compute/>`__ For more information on OpenStack APIs, SDKs and CLIs in general, refer to: - `OpenStack for App Developers <https://www.openstack.org/appdev/>`__ - `Development resources for OpenStack clouds <https://developer.openstack.org/>`__ Operators --------- To learn how to deploy and configure OpenStack Nova, consult the documentation available online at: - `OpenStack Nova <https://docs.openstack.org/nova/>`__ 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: - `Bug Tracker <https://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. To understand better the processes that the team is using, please refer to the `Process document <https://docs.openstack.org/nova/latest/contributor/process.html>`__. Further developer focused documentation is available at: - `Official Nova Documentation <https://docs.openstack.org/nova/>`__ - `Official Client Documentation <https://docs.openstack.org/python-novaclient/>`__ 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: - `Nova Specs <http://specs.openstack.org/openstack/nova-specs/>`__ .. _Summit: https://www.openstack.org/summit/ .. _Project Team Gathering: https://www.openstack.org/ptg/