yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => havana-3

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

Title:
  nova aggregate-add-host should limit user to  set different
  availability zone for a host

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  user can use "nova aggregate-add-host" to set different availability
  zone for a host, then the host will be available for multi
  availability zone. When user  try to boot instance in the host using
  second or third availability zone, the instance will still be assigned
  to the first availability zone which set at first time the host added
  to a host aggregate of the availability zone. It works as design, but
  it confuse the user, it make user to think that a host can be assigned
  to multi availability zone. So I think we should add checking to limit
  user to add host to host aggregates in different availability zone.

  Here are steps to recreate the issue:

  1)   create one AZ
  nova aggregate-create test-az test-az
  the AZ test-az id is 1 
   
  2)   add host to AZ
  nova aggregate-add-host 1 WIN-UJAK7KN9LRA

  3)  boot one instance
   nova boot --flavor 2 --image  26c6ddd1-3db7-440e-930c-f3dbc146c7f2   --availability-zone  test-az test-vm-1

  In this steps, it prints | OS-EXT-AZ:availability_zone         | nova
  |

  4) check test-vm-1

  nova show d752aa55-b2dd-4966-a770-4ab2972c6dd7

  
  OS-EXT-AZ:availability_zone         | test-az                                                  |


  5)
  then create another AZ
               nova aggregate-create test-az-2 test-az-2

  Add host to AZ
               nova aggregate-add-host 2 WIN-UJAK7KN9LRA

  check AZs
              nova  availability-zone-list
                       | test-az-2,test-az     | available                              |
                               | |- WIN-UJAK7KN9LRA    |                                        |
                               |  | |- nova-compute     | enabled :-) 2013-06-26T03:16:47.764046 |

  boot one instance
             nova boot --flavor 2 --image  26c6ddd1-3db7-440e-930c-f3dbc146c7f2   --availability-zone  test-az-2 test-vm-4

      still the print is | OS-EXT-AZ:availability_zone         | nova
  |

  check instance info
              | OS-EXT-AZ:availability_zone         | test-az                                                  |

  
   The new instance is in test-az, the passed option test-az-2 seems not work. We may should add checking logic to limit users to do operations like " nova aggregate-add-host 2 WIN-UJAK7KN9LRA" in step #5

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