disk_bus might be ignored when booting from volume
Bug #1281989 reported by
Xavier Queralt
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
There are several ways of selecting the disk_bus for a BDM. One of them is using the hw_disk_bus image property which, if present, is inherited by volumes created from an image.
When booting from a volume that has this property defined, even though we might think it will be considered when selecting the bus, it is ignored because the code that guesses the bus and device name for volume BDMs expects it to be defined in the same BDM.
| summary: |
- disk_bus may be ignored when booting from volume + disk_bus might be ignored when booting from volume |
| Changed in nova: | |
| assignee: | nobody → Xavier Queralt (xqueralt) |
| Changed in nova: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to nova (master) | #1 |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → icehouse-3 |
| Changed in nova: | |
| status: | Fix Committed → Fix Released |
| Changed in nova: | |
| milestone: | icehouse-3 → 2014.1 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 060c0e120846913
Author: Xavier Queralt <email address hidden>
Date: Wed Feb 19 10:08:49 2014 +0100
Use disk_bus when guessing the device name for vol
Even though the disk bus could be set through hw_disk_bus property,
the libvirt driver didn't guess the proper bus and device name for the
root volume and expected it to be defined in the BDM.
With this patch, we consider the predefined disk_bus when going to guess
the volume device name and bus instead of just relying on the one
defined in the BDM.
Change-Id: Ic6434ee2b29dc2
Closes-Bug: 1281989