Instances are not rescheduled after deploy fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Shunli Zhou | ||
Ocata |
Fix Released
|
High
|
Matt Riedemann |
Bug Description
Steps to reproduce:
Pre-step. Need to force the deploy to fail in such a way that it can be rescheduled. For testing I just forced it to fail by adding raise nova.exception.
1. Make sure environment is set to retry failed deploys.
2. Attempt to deploy VM and wait for it to fail.
Expected result:
Failed instance is rescheduled and attempted on another host.
Actual result:
Deploy fails but is not rescheduled.
I am just beginning to experiment with ocata build from early March. I found that when an instance fails to deploy and throws a RescheduledExce
On initial deploy nova.conductor.
In the past it looks like populate_retry() was called in by nova.conductor.
Changed in nova: | |
status: | New → Confirmed |
assignee: | nobody → Shunli Zhou (shunliz) |
tags: | added: conductor |
Changed in nova: | |
importance: | Undecided → High |
tags: | added: ocata-backport-potential |
Changed in nova: | |
assignee: | Shunli Zhou (shunliz) → Matt Riedemann (mriedem) |
Changed in nova: | |
assignee: | Matt Riedemann (mriedem) → Shunli Zhou (shunliz) |
tried on devstack. manager. py:schedule_ and_build_ instances
nova / nova/conductor/
filter_props = request_ spec.to_ legacy_ filter_ properties_ dict() utils.populate_ filter_ properties( filter_ props,
host)
scheduler_
The filter_pros here is an empty dict,so nothing is done in _add_retry_host and the retry feature is broken.
I will investigate this and work on this problem.