yahoo-eng-team team mailing list archive

[Takashi NATSUME <natsume.takashi@xxxxxxxxxxxxx>]

Public bug reported:

Environment:
nova 2014.2.1
python-novaclient 2.20.0
Ubuntu 14.04.1 LTS

Two host aggregates in same AZ(availability zone) have same compute node.
And then one host aggregate is updated to a different AZ.
As a result, the compute node belongs to host aggregates in defferent AZs at the same time.

[Steps to Reproduce]
stack@devstack-juno:/opt/devstack$ nova aggregate-list
+----+------+-------------------+
| Id | Name | Availability Zone |
+----+------+-------------------+
| 1  | agg1 | AZ1               |
| 2  | agg2 | AZ1               |
+----+------+-------------------+
stack@devstack-juno:/opt/devstack$ nova aggregate-details agg1
+----+------+-------------------+-----------------+-------------------------+
| Id | Name | Availability Zone | Hosts           | Metadata                |
+----+------+-------------------+-----------------+-------------------------+
| 1  | agg1 | AZ1               | 'devstack-juno' | 'availability_zone=AZ1' |
+----+------+-------------------+-----------------+-------------------------+
stack@devstack-juno:/opt/devstack$ nova aggregate-details agg2
+----+------+-------------------+-----------------+-------------------------+
| Id | Name | Availability Zone | Hosts           | Metadata                |
+----+------+-------------------+-----------------+-------------------------+
| 2  | agg2 | AZ1               | 'devstack-juno' | 'availability_zone=AZ1' |
+----+------+-------------------+-----------------+-------------------------+
stack@devstack-juno:/opt/devstack$ nova aggregate-update agg2 agg2 AZ2
Aggregate 2 has been successfully updated.
+----+------+-------------------+-----------------+-------------------------+
| Id | Name | Availability Zone | Hosts           | Metadata                |
+----+------+-------------------+-----------------+-------------------------+
| 2  | agg2 | AZ2               | 'devstack-juno' | 'availability_zone=AZ2' |
+----+------+-------------------+-----------------+-------------------------+
stack@devstack-juno:/opt/devstack$ nova aggregate-details agg1
+----+------+-------------------+-----------------+-------------------------+
| Id | Name | Availability Zone | Hosts           | Metadata                |
+----+------+-------------------+-----------------+-------------------------+
| 1  | agg1 | AZ1               | 'devstack-juno' | 'availability_zone=AZ1' |
+----+------+-------------------+-----------------+-------------------------+
stack@devstack-juno:/opt/devstack$ nova aggregate-details agg2
+----+------+-------------------+-----------------+-------------------------+
| Id | Name | Availability Zone | Hosts           | Metadata                |
+----+------+-------------------+-----------------+-------------------------+
| 2  | agg2 | AZ2               | 'devstack-juno' | 'availability_zone=AZ2' |
+----+------+-------------------+-----------------+-------------------------+

Because the cause of the bug is wrong check logic in is_safe_to_update_az method in nova/compute/api.py,
the bug would occur in master.

** Affects: nova
     Importance: Undecided
     Assignee: Takashi NATSUME (natsume-takashi)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Takashi NATSUME (natsume-takashi)

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

Title:
  A compute node can belong to host aggregates in defferent AZs

Status in OpenStack Compute (Nova):
  New

Bug description:
  Environment:
  nova 2014.2.1
  python-novaclient 2.20.0
  Ubuntu 14.04.1 LTS

  Two host aggregates in same AZ(availability zone) have same compute node.
  And then one host aggregate is updated to a different AZ.
  As a result, the compute node belongs to host aggregates in defferent AZs at the same time.

  [Steps to Reproduce]
  stack@devstack-juno:/opt/devstack$ nova aggregate-list
  +----+------+-------------------+
  | Id | Name | Availability Zone |
  +----+------+-------------------+
  | 1  | agg1 | AZ1               |
  | 2  | agg2 | AZ1               |
  +----+------+-------------------+
  stack@devstack-juno:/opt/devstack$ nova aggregate-details agg1
  +----+------+-------------------+-----------------+-------------------------+
  | Id | Name | Availability Zone | Hosts           | Metadata                |
  +----+------+-------------------+-----------------+-------------------------+
  | 1  | agg1 | AZ1               | 'devstack-juno' | 'availability_zone=AZ1' |
  +----+------+-------------------+-----------------+-------------------------+
  stack@devstack-juno:/opt/devstack$ nova aggregate-details agg2
  +----+------+-------------------+-----------------+-------------------------+
  | Id | Name | Availability Zone | Hosts           | Metadata                |
  +----+------+-------------------+-----------------+-------------------------+
  | 2  | agg2 | AZ1               | 'devstack-juno' | 'availability_zone=AZ1' |
  +----+------+-------------------+-----------------+-------------------------+
  stack@devstack-juno:/opt/devstack$ nova aggregate-update agg2 agg2 AZ2
  Aggregate 2 has been successfully updated.
  +----+------+-------------------+-----------------+-------------------------+
  | Id | Name | Availability Zone | Hosts           | Metadata                |
  +----+------+-------------------+-----------------+-------------------------+
  | 2  | agg2 | AZ2               | 'devstack-juno' | 'availability_zone=AZ2' |
  +----+------+-------------------+-----------------+-------------------------+
  stack@devstack-juno:/opt/devstack$ nova aggregate-details agg1
  +----+------+-------------------+-----------------+-------------------------+
  | Id | Name | Availability Zone | Hosts           | Metadata                |
  +----+------+-------------------+-----------------+-------------------------+
  | 1  | agg1 | AZ1               | 'devstack-juno' | 'availability_zone=AZ1' |
  +----+------+-------------------+-----------------+-------------------------+
  stack@devstack-juno:/opt/devstack$ nova aggregate-details agg2
  +----+------+-------------------+-----------------+-------------------------+
  | Id | Name | Availability Zone | Hosts           | Metadata                |
  +----+------+-------------------+-----------------+-------------------------+
  | 2  | agg2 | AZ2               | 'devstack-juno' | 'availability_zone=AZ2' |
  +----+------+-------------------+-----------------+-------------------------+

  Because the cause of the bug is wrong check logic in is_safe_to_update_az method in nova/compute/api.py,
  the bug would occur in master.

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