Instances always get mapped into the last processed cell in conductor
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Dan Smith | ||
Pike |
Fix Committed
|
High
|
Matt Riedemann |
Bug Description
This was a regression introduced in Pike here: https:/
The schedule_
The problem is the 2nd for loop doesn't do the same cell lookup based on the host:
It just re-uses the last set cell variable from the first for loop, so we could have a case where an instance is created in cell1, and then another instance is created in cell2, and then when the 2nd loop maps the first instance, it maps it to cell2 but it really lives in cell1.
Not to mention the BDMs and tags would be created in the wrong cell.
Changed in nova: | |
assignee: | Dan Smith (danms) → Matt Riedemann (mriedem) |
Changed in nova: | |
assignee: | Matt Riedemann (mriedem) → Dan Smith (danms) |
Fix proposed to branch: master /review. openstack. org/501452
Review: https:/