live-migration fails when instance booted without specified availability_zone
Bug #1451921 reported by
Timofey Durakov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Low
|
Timofey Durakov |
Bug Description
If instance is booted without availability-zone parameter. It's value in instances table equal NULL.
If live-migrate such instance, all hosts, even those, which belongs to another availability zone are correct.
This could cause problems with attached volumes, and whole live-migration
Changed in nova: | |
assignee: | nobody → Timofey Durakov (tdurakov) |
To post a comment you must log in.
That all comes to the problem that the scheduler is bypassed when you're specifying a target host, so the AZFilter is not called.
I'm working on a blueprint for adding a check even if the target host is provided, see https:/ /blueprints. launchpad. net/nova/ +spec/check- destination- on-migrations
Leaving that bug confirmed but I think we need the blueprint I mentioned for correctly fixing the bug.