Error message misleading when cross_az is false
Bug #1739368 reported by
Marc Koderer
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Switching cross_az volume attachment to false the end-user see the following error when trying to boot from a different AZ:
openstack server create --volume mko_test01 --flavor m1.small --nic net-id=
Block Device Mapping is Invalid: failed to get volume 96eec88d-
Actually there is no problem in "getting the volume" - Cinder response with 200. But the AZ check raises an exception that is nested in this area.
| Changed in nova: | |
| assignee: | nobody → Marc Koderer (m-koderer) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #1 |
| Changed in nova: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on nova (master) | #2 |
| Changed in nova: | |
| status: | In Progress → Confirmed |
| assignee: | Marc Koderer (m-koderer) → nobody |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/