[Yahoo-eng-team] [Bug 1378904] Re: renaming availability zone doesn't modify host's availability zone
** Changed in: nova Assignee: Matt Riedemann (mriedem) => Andrey Volkov (avolkov) ** Also affects: nova/rocky Importance: Undecided Status: New ** Changed in: nova/rocky Assignee: (unassigned) => Andrey Volkov (avolkov) ** Changed in: nova/rocky Status: New => Fix Released ** Changed in: nova/rocky Importance: Undecided => Medium -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1378904 Title: renaming availability zone doesn't modify host's availability zone Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) rocky series: Fix Released 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.gplhost.com/debian/, up to date. If you need any more infos, I'd be glad to help. Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1378904/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1378904] Re: renaming availability zone doesn't modify host's availability zone
Reviewed: https://review.openstack.org/509206
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=8e19ef4173906da0b7c761da4de0728a2fd71e24
Submitter: Zuul
Branch:master
commit 8e19ef4173906da0b7c761da4de0728a2fd71e24
Author: Andrey Volkov
Date: Tue Oct 3 15:42:55 2017 +0300
Check hosts have no instances for AZ rename
Update aggregate and update aggregate metadata API calls have the
ability to update availability zone name for the aggregate. If the
aggregate is not empty (has hosts with instances on it)
the update leads to discrepancy for objects saving availability zone as a
string but not reference.
From devstack DB they are:
- cinder.backups.availability_zone
- cinder.consistencygroups.availability_zone
- cinder.groups.availability_zone
- cinder.services.availability_zone
- cinder.volumes.availability_zone
- neutron.agents.availability_zone
- neutron.networks.availability_zone_hints
- neutron.router_extra_attributes.availability_zone_hints
- nova.dns_domains.availability_zone
- nova.instances.availability_zone
- nova.volume_usage_cache.availability_zone
- nova.shadow_dns_domains.availability_zone
- nova.shadow_instances.availability_zone
- nova.shadow_volume_usage_cache.availability_zone
Why that's bad?
First, API and Horizon show different values for host and instance for
example. Second, migration for instances with changed availability
zone fails with "No valid host found" for old AZ.
This change adds an additional check to aggregate an Update Aggregate API
call.
With the check, it's not possible to rename AZ if the corresponding
aggregate has instances in any hosts.
PUT /os-aggregates/{aggregate_id} and
POST /os-aggregates/{aggregate_id}/action return HTTP 400 for
availability zone renaming if the hosts of the aggregate have any instances.
It's similar to conflicting AZ names error already available.
Change-Id: Ic27195e46502067c87ee9c71a811a3ca3f610b73
Closes-Bug: #1378904
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1378904
Title:
renaming availability zone doesn't modify host's availability zone
Status in OpenStack Compute (nova):
Fix Released
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.gplhost.com/debian/, up to date.
If you need any more infos, I'd be glad to help.
Cheers
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1378904/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1378904] Re: renaming availability zone doesn't modify host's availability zone
Fix proposed to branch: master Review: https://review.openstack.org/509206 ** Changed in: nova Status: Won't Fix => In Progress ** Changed in: nova Assignee: Radoslav Gerganov (rgerganov) => Andrey Volkov (avolkov) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1378904 Title: renaming availability zone doesn't modify host's availability zone Status in OpenStack Compute (nova): In Progress 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.gplhost.com/debian/, up to date. If you need any more infos, I'd be glad to help. Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1378904/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1378904] Re: renaming availability zone doesn't modify host's availability zone
There is clear upstream consensus on the fact that since availability zones are for end-users, updating an AZ from an operator point-of-view would confuse their users. Let me explain further : say you'd like to change AZ "foo" into "bar". For end-users looking at the AZ API before booting their instances, they can see "foo" as a valid target. So they just use --availability_zone foo in their instance boot calls and they expect to see their instances in AZ foo. Now, what if operator turns "foo" into "bar" ? If I'm an end-user, I'd be very surprised to see my instances being now in "bar" while I explicitely asked "foo"! As a clear design decision, we really want to make it explicit that renaming an AZ should be forbidden if there are active instances hosted within that AZ. Closing that bug as Wontfix since I feel not being able to modify an AZ is not a bug but rather a design decision, but I feel we also need to modify the aggregates API to return a HTTP40x if someone is wanting to update an aggregate metadata containing AZ information when there are instances attached to it. ** Changed in: nova Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1378904 Title: renaming availability zone doesn't modify host's availability zone Status in OpenStack Compute (nova): Won't Fix 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.gplhost.com/debian/, up to date. If you need any more infos, I'd be glad to help. Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1378904/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1378904] Re: renaming availability zone doesn't modify host's availability zone
CONFIRMED FOR: MITAKA $ nova-manage --version 13.0.0 # Reproduce Steps: 1) Create a HA/AZ. ie., "AZ1" 2) Add compute nodes to "AZ1" (Admin->System->Host Aggregates->Manage Hosts) 3) Launch VM in this AZ. 4) Live migrate/migrate VM - will succeed 5) Create a new HA/AZ. ie., "AZ2" 6) Remove compute nodes from "AZ1" 7) Add compute nodes to "AZ2" 8) Try to migrate VM Fails with ERROR: Error: No valid host was found. There are not enough hosts available. compute-1: (AvailabilityZoneFilter) avail zone az1 not in host AZ: set([u'az2']) # nova-scheduler.log 2016-11-17 21:08:38.690 168453 INFO nova.filters [req-e9cede77-e888-4553-83d6-4e112a8e44a7 59d4a769c88545acb86f646b2464f4d1 93dd4afc2ddb4bfd88d8b5d13d348998 - - -] AvailabilityZoneFilter: (compute-1) REJECT: avail zone az1 not in host AZ: set([u'az2']) # nova show displays correct AZ for VM | OS-EXT-AZ:availability_zone | az2 # however nova --debug list displays in the RESP BODY: "OS-EXT-AZ:availability_zone": "az1" # check the VM in DB, availability_zone is still listed as 'az1' as well. ** Changed in: nova Status: Expired => New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1378904 Title: renaming availability zone doesn't modify host's availability zone Status in OpenStack Compute (nova): New 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.gplhost.com/debian/, up to date. If you need any more infos, I'd be glad to help. Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1378904/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1378904] Re: renaming availability zone doesn't modify host's availability zone
This is an automated cleanup. This bug report has been closed because it is older than 18 months and there is no open code change to fix this. After this time it is unlikely that the circumstances which lead to the observed issue can be reproduced. If you can reproduce the bug, please: * reopen the bug report (set to status "New") * AND add the detailed steps to reproduce the issue (if applicable) * AND leave a comment "CONFIRMED FOR: " Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON). Valid example: CONFIRMED FOR: LIBERTY ** Changed in: nova Status: Confirmed => Expired ** Changed in: nova Assignee: Fan Guo (faguo) => (unassigned) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1378904 Title: renaming availability zone doesn't modify host's availability zone Status in OpenStack Compute (nova): Expired 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.gplhost.com/debian/, up to date. If you need any more infos, I'd be glad to help. Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1378904/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
