stable/new: resource tracker exception
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
In Progress
|
High
|
Gary Kotton |
Bug Description
2016-10-06 20:20:30.611 8718 WARNING nova.compute.
2016-10-06 20:20:30.612 8718 INFO nova.compute.
2016-10-06 20:20:31.987 8718 ERROR nova.compute.
2016-10-06 20:20:31.987 8718 ERROR nova.compute.
2016-10-06 20:20:31.987 8718 ERROR nova.compute.
2016-10-06 20:20:31.987 8718 ERROR nova.compute.
2016-10-06 20:20:31.987 8718 ERROR nova.compute.
2016-10-06 20:20:31.987 8718 ERROR nova.compute.
2016-10-06 20:20:31.987 8718 ERROR nova.compute.
2016-10-06 20:20:31.987 8718 ERROR nova.compute.
2016-10-06 20:20:31.987 8718 ERROR nova.compute.
2016-10-06 20:20:31.987 8718 ERROR nova.compute.
2016-10-06 20:20:31.987 8718 ERROR nova.compute.
2016-10-06 20:20:31.987 8718 ERROR nova.compute.
Changed in nova: | |
importance: | Undecided → Critical |
tags: | added: newton-backport-potential |
The immediate cause here seems to be that there is no entry in bdms for the instance uuid. There are 2 potential sources of KeyError on that line, and we know it's not the other one because it's the guard condition of that code block.
So this line:
# Get bdms by instance uuids BlockDeviceMapp ingList. bdms_by_ instance_ uuid(
bdms = objects.
ctx, instance_uuids)
returned no bdms for this instance. I would expect there to be a BDM for at least the root disk. Can anybody confirm?