yahoo-eng-team team mailing list archive

[Jiri Suchomel <jsuchome@xxxxxxxx>]

Public bug reported:

When booting an instance from image, which should create new volume,
when AZ zone is not specified, instance could end in different AZ than
the image.

That doesn't hurt with cross_az_attach=true, but if this is set to
False, creating the volume will fail with

" Instance %(instance)s and volume %(vol)s are not in the same
availability_zone...." error.


Nova actually decides at some point, which AZ it should use (when none was specified), so I think we just need to move this decision before the point when the volume is created, so nova can pass correct AZ value to cinder API.

** Affects: nova
     Importance: Undecided
     Assignee: Jiri Suchomel (jsuchome)
         Status: In Progress

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

Title:
  different availability zone for nova and cinder

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  When booting an instance from image, which should create new volume,
  when AZ zone is not specified, instance could end in different AZ than
  the image.

  That doesn't hurt with cross_az_attach=true, but if this is set to
  False, creating the volume will fail with

  " Instance %(instance)s and volume %(vol)s are not in the same
  availability_zone...." error.

  
  Nova actually decides at some point, which AZ it should use (when none was specified), so I think we just need to move this decision before the point when the volume is created, so nova can pass correct AZ value to cinder API.

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