*** This bug is a duplicate of bug 1489575 ***
https://bugs.launchpad.net/bugs/1489575
** This bug has been marked a duplicate of bug 1489575
Cinder always tries to create volumes in Cinder AZ with same name as Nova AZ
--
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
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
