[openstack-dev] [nova] notification impact of moving the instance create to the conductor

Balazs Gibizer balazs.gibizer at ericsson.com
Wed Feb 15 17:07:25 UTC 2017


It seems that the Move instance creation to conductor commit [1] 
changed when and how the instance.delete notification is emitted for an 
unscheduled instance. Unfortunately the legacy notification doesn't 
have test coverage and the versioned notification coverage are still on 
review [2] for this case.

Before [1] the instance.delete for an unscheduled instance is emitted 
from here [3]. But after [1] the execution of the same delete operation 
goes to a new direction [4] and never reaches [3].
Before [1] the new test coverage in [2] was passing but now after [1] 
is merged the test_create_server_error fails as the instance.delete 
notification is not emitted.

Is it an intentional change or a bug? If it is a bug could you give me 
some pointers how to restore the original notification behavior?


[1] https://review.openstack.org/#/c/319379
[2] https://review.openstack.org/#/c/410297
[3] https://review.openstack.org/#/c/410297/9/nova/compute/api.py@1860
[4] https://review.openstack.org/#/c/319379/84/nova/compute/api.py@1790

More information about the OpenStack-dev mailing list