commit 96acf3db0bc9ecaddb04fc9effc4b9ca1553103d
Author: Matt Riedemann <email address hidden>
Date: Mon Dec 18 17:41:26 2017 -0500
Don't try to delete build request during a reschedule
If populate_retry failed because of MaxRetriesExceeded,
don't try to delete build requests because they should
already be gone from the initial create attempt, plus
we should assume the cell conductor can't reach the API
database anyway.
Similar for hitting NoValidHost during a reschedule. We
can tell if we're doing a reschedule by the num_attempts
value in filter_properties, populated via populate_retry,
which will be >1 during a reschedule.
Change-Id: I0b3ec6bb098ca32ffd32a61d4f9dcf426c3faf46
Closes-Bug: #1736946
(cherry picked from commit cf88a27c6250043859306d47ae82a63535ad507f)
Reviewed: https:/ /review. openstack. org/529697 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=96acf3db0bc 9ecaddb04fc9eff c4b9ca1553103d
Committed: https:/
Submitter: Zuul
Branch: stable/pike
commit 96acf3db0bc9eca ddb04fc9effc4b9 ca1553103d
Author: Matt Riedemann <email address hidden>
Date: Mon Dec 18 17:41:26 2017 -0500
Don't try to delete build request during a reschedule
If populate_retry failed because of MaxRetriesExceeded,
don't try to delete build requests because they should
already be gone from the initial create attempt, plus
we should assume the cell conductor can't reach the API
database anyway.
Similar for hitting NoValidHost during a reschedule. We
can tell if we're doing a reschedule by the num_attempts
value in filter_properties, populated via populate_retry,
which will be >1 during a reschedule.
Change-Id: I0b3ec6bb098ca3 2ffd32a61d4f9dc f426c3faf46 859306d47ae82a6 3535ad507f)
Closes-Bug: #1736946
(cherry picked from commit cf88a27c6250043