different availability zone for nova and cinder when AZ is not explicitly given
Bug #1497253 reported by
Jiri Suchomel
This bug affects 10 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Dan Smith |
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_
" Instance %(instance)s and volume %(vol)s are not in the same availability_
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.
tags: | added: az volumes |
summary: |
- different availability zone for nova and cinder + different availability zone for nova and cinder when AZ is not + explicitly given |
Changed in nova: | |
importance: | Undecided → Low |
tags: | added: scheduler |
Changed in nova: | |
assignee: | Jiri Suchomel (jsuchome) → Roman Podoliaka (rpodolyaka) |
Changed in nova: | |
assignee: | Roman Podoliaka (rpodolyaka) → Matt Riedemann (mriedem) |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/225119
Review: https:/