evacuate rebuild claim will not use any image_meta so it can miss numa_topology claims
Bug #1785318 reported by
Matt Riedemann
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Matt Riedemann | ||
Ocata |
Triaged
|
Medium
|
Unassigned | ||
Pike |
Triaged
|
Medium
|
Unassigned | ||
Queens |
Triaged
|
Medium
|
Unassigned | ||
Rocky |
Fix Committed
|
Medium
|
Matt Riedemann |
Bug Description
I found this in the starlingx diff for nova:
For volume-backed instances, the instance image_meta comes from the volume_
Then during an evacuate of a volume-backed instance, the rebuild_claim in the ResourceTracker won't actually get the proper image_meta because of this code in ComputeManager.
The only thing in the claims code that cares about image_meta is for calculating numa_topology claims:
I'm not even totally sure if evacuate fully works with an instance using numa topology, but this can't help.
tags: | added: starlingx |
To post a comment you must log in.
This is more than just volume-backed instances, it's evacuate in general. The API doesn't pass down the image_ref so we just pass {} to the rebuild_claim during evacuate in all cases, volume-backed or not.