yahoo-eng-team team mailing list archive

[Praveen Kumar Dubey <pkdubey4u@xxxxxxxxx>]

Public bug reported:

Nova show command shows availability zone as "AZ1" but nova database
shows as 'nova' after live migrating VM to other node which is in
different availability zone. This is for Juno release.

nova show a5bbc4fa-7ffb-42c3-b60e-b54885227bdd | grep availibility_zone
| OS-EXT-AZ:availability_zone          | AZ1                   |


node:~# mysql -e "use nova; select availability_zone from instances where uuid='a5bbc4fa-7ffb-42c3-b60e-b54885227bdd';"
+-------------------+
| availability_zone |
+-------------------+
| nova              |
+-------------------+

This is causing problem while trying to resize the vm from m1.large to
m1.xlarge flavor. The node (with availability zone as 'nova') doesn't
have enough memory left. After live migrating this VM to another node
(with availability zone as 'AZ1'), it tries to launch on same node (with
availability zone as 'nova') during resize procedure. After changing the
DB value to 'AZ1', VM was resized successfully.

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

Title:
  Incorrect availability zone shown by nova show command

Status in OpenStack Compute (nova):
  New

Bug description:
  Nova show command shows availability zone as "AZ1" but nova database
  shows as 'nova' after live migrating VM to other node which is in
  different availability zone. This is for Juno release.

  nova show a5bbc4fa-7ffb-42c3-b60e-b54885227bdd | grep availibility_zone
  | OS-EXT-AZ:availability_zone          | AZ1                   |

  
  node:~# mysql -e "use nova; select availability_zone from instances where uuid='a5bbc4fa-7ffb-42c3-b60e-b54885227bdd';"
  +-------------------+
  | availability_zone |
  +-------------------+
  | nova              |
  +-------------------+

  This is causing problem while trying to resize the vm from m1.large to
  m1.xlarge flavor. The node (with availability zone as 'nova') doesn't
  have enough memory left. After live migrating this VM to another node
  (with availability zone as 'AZ1'), it tries to launch on same node
  (with availability zone as 'nova') during resize procedure. After
  changing the DB value to 'AZ1', VM was resized successfully.

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