yahoo-eng-team team mailing list archive

[Guillaume Winter <guillaume.winter@xxxxxxxxxxxxxx>]

Public bug reported:

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

** Affects: nova
     Importance: Undecided
         Status: 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