renaming availability zone doesn't modify host's availability zone
Bug #1378904 reported by
Guillaume Winter
This bug affects 10 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Andrey Volkov | ||
Rocky |
Fix Released
|
Medium
|
Andrey Volkov |
Bug Description
Hi,
After renaming our availability zones via Horizon Dashboard, we couldn't migrate any "old" instance anymore, the scheduler returning "No valid Host found"...
After searching, we found in the nova DB `instances` table, the "availability_zone" field contains the name of the availability zone, instead of the ID ( or maybe it is intentional ;) ).
So renaming AZ leaves the hosts created prior to this rename orphan and the scheduler cannot find any valid host for them...
Our openstack install is on debian wheezy, with the icehouse "official" repository from archive.
If you need any more infos, I'd be glad to help.
Cheers
Changed in nova: | |
status: | New → Confirmed |
tags: | added: compute db |
Changed in nova: | |
assignee: | nobody → Fan Guo (faguo) |
Changed in nova: | |
assignee: | nobody → Anusha Unnam (anusha-unnam) |
Changed in nova: | |
assignee: | Andrey Volkov (avolkov) → nobody |
Changed in nova: | |
assignee: | nobody → Andrey Volkov (avolkov) |
Changed in nova: | |
importance: | Low → Medium |
Changed in nova: | |
assignee: | Andrey Volkov (avolkov) → Matt Riedemann (mriedem) |
Changed in nova: | |
assignee: | Matt Riedemann (mriedem) → Andrey Volkov (avolkov) |
Changed in nova: | |
assignee: | Andrey Volkov (avolkov) → Matt Riedemann (mriedem) |
Changed in nova: | |
assignee: | Matt Riedemann (mriedem) → Andrey Volkov (avolkov) |
Changed in nova: | |
assignee: | Andrey Volkov (avolkov) → Matt Riedemann (mriedem) |
Changed in nova: | |
assignee: | Matt Riedemann (mriedem) → Andrey Volkov (avolkov) |
To post a comment you must log in.
I faced the same problem on my setup:
OS: Ubuntu 14.04
OpenStack: Kilo from the ubuntu-cloud repo
I could rename the availability-zone from the dashboard or the API but I couldn't migrate the instances anymore. I had to edit the following fields:
db->nova, table-> instances, row->availabili ty_zone table-> ports,row- >device_ owner
db->neutron,
after the manually update the VMs could be migrated again.