yahoo-eng-team team mailing list archive

[Joe Gordon <1189070@xxxxxxxxxxxxxxxxxx>]

This is a nova side issue, a node should not be able to be part of two
AZs, this is in the process of being fixed in nova

** Changed in: python-novaclient
       Status: New => Invalid

-- 
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/1189070

Title:
  Availability zones in nested host aggregates are concatenated

Status in OpenStack Compute (Nova):
  Confirmed
Status in Python client library for Nova:
  Invalid

Bug description:
  If I create two host aggregates with unique availability zones for the
  same host (named 'global' and '1' here), a subsequent call to 'nova
  availability-zone-list' reports the following:

  $ nova availability-zone-list
  +----------+-----------+
  | Name     | Status    |
  +----------+-----------+
  | 1,global | available |
  +----------+-----------+

  
  I would suggest we don't join the AZ names and report them individually like this:

  $ nova availability-zone-list
  +--------+-----------+
  | Name   | Status    |
  +--------+-----------+
  | 1      | available |
  | global | available |
  +--------+-----------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1189070/+subscriptions