commit 9b090aeb7e2d4e4adc0b2a80402cbfb09830bd94
Author: Andrew Laski <email address hidden>
Date: Wed Sep 28 09:47:12 2016 -0400
Ignore BuildRequest during an instance reschedule
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.
Reviewed: https:/ /review. openstack. org/378636 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=9b090aeb7e2 d4e4adc0b2a8040 2cbfb09830bd94
Committed: https:/
Submitter: Jenkins
Branch: master
commit 9b090aeb7e2d4e4 adc0b2a80402cbf b09830bd94
Author: Andrew Laski <email address hidden>
Date: Wed Sep 28 09:47:12 2016 -0400
Ignore BuildRequest during an instance reschedule
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: Ibf28d1d8f54703 b465ccc49728141 9356cd0136e
Closes-Bug: 1628530