yahoo-eng-team team mailing list archive

[Joe Gordon <1240374@xxxxxxxxxxxxxxxxxx>]

** 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/1240374

Title:
  some times availability-zone not take effect after it created

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  1. create a availability-zone: second_zone, add ns17 to the aggregate
  [root@ns11 nova]# nova availability-zone-list
  +----------------------------------+----------------------------------------+
  | Name                             | Status                                 |
  +----------------------------------+----------------------------------------+

  | first_zone                       | available                              |
  | |- ns11.sce.cn.ibm.com           |                                        |
  | | |- nova-compute                | enabled :-) 2013-09-25T09:51:54.352341 |

  | second_zone                      | available                              |
  | |- ns17-osee.cn.ibm.com          |                                        |
  | | |- nova-compute                | enabled :-) 2013-09-25T09:51:58.283034 |
  +----------------------------------+----------------------------------------+

  2. nova boot with the zone:
  [root@ns11 ˜]# nova boot --image d7c64f67-3de7-4aa0-88fb-1292ff520404 --flavor 1 --availability-zone second_zone:ns17-osee.cn.ibm.com test_zone17_2

  3.  [root@ns11 nova]# nova list
  +--------------------------------------+-----------------+---------+-------------+-------------+------------------------+
  | ID                                   | Name            | Status  | Task State  | Power State | Networks               |
  +--------------------------------------+-----------------+---------+-------------+-------------+------------------------+

  | 6f3ec942-6c8e-46fa-ad7e-d2c900921f65 | test_zone17     | ACTIVE  | None        | Running     | flat_net01=172.10.0.16 |
  | 7273973d-a9e1-4917-ad59-c54ece9b0765 | test_zone17_1   | ACTIVE  | None        | Running     | flat_net01=172.10.0.18 |
  | 27f71b26-b775-4516-ba2a-13d9e91e96dd | test_zone17_2   | ACTIVE  | None        | Running     | flat_net01=172.10.0.19 |
  | 6350a439-2dd3-4b14-b99e-219fad27111b | zhikun_testvm   | ACTIVE  | None        | Running     | flat_net01=172.10.0.13 |
  +--------------------------------------+-----------------+---------+-------------+-------------+------------------------+

  4.  but the zone of the vm is: nova
  [root@ns11 nova]# nova show 27f71b26-b775-4516-ba2a-13d9e91e96dd
  +--------------------------------------+----------------------------------------------------------+
  | Property                             | Value                                                    |
  +--------------------------------------+----------------------------------------------------------+
  | status                               | ACTIVE                                                   |
  | flat_net01 network                   | 172.10.0.19                                              |
  | updated                              | 2013-09-25T09:50:23Z                                     |
  | OS-EXT-STS:task_state                | None                                                     |
  | OS-EXT-SRV-ATTR:host                 | ns17-osee.cn.ibm.com                                     |
  | key_name                             | None                                                     |
  | image                                | cirros_kvm (d7c64f67-3de7-4aa0-88fb-1292ff520404)        |

  | accessIPv6                           |                                                          |
  | progress                             | 0                                                        |
  | OS-EXT-STS:power_state               | 1                                                        |
  | OS-EXT-AZ:availability_zone          | nova                                                     |
  | config_drive                         |                                                          |
  +--------------------------------------+----------------------------------------------------------+

  [root@ns11 nova]# date
  Wed Sep 25 18:05:26 CST 2013

  5.  I did not configure default_zone in nova.conf

  6.  It is very strange that this problem could not always been
  recreated. usually it happens when we create a new AZ, and then use
  the AZ boot instance. Seems wait for some time, may be one night or
  sooner, the AZ will become to correct one. I'm confused.

  # Expected  results
  The AZ should take effect any time if we did not set default AZ in nova.conf

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