nova boot fails with rbd backend
Bug #1361840 reported by
Jens Rosenboom
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Mehdi Abaakouk |
Bug Description
Booting a VM in a plain devstack setup with ceph enabled, I get an error like:
libvirtError: internal error: process exited while connecting to monitor: qemu-system-x86_64: -drive file=rbd:
even though config_drive is set to false.
This seems to be related to https:/
Changed in nova: | |
importance: | Undecided → High |
Changed in nova: | |
assignee: | nobody → Mehdi Abaakouk (sileht) |
status: | New → In Progress |
Changed in nova: | |
milestone: | none → juno-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | juno-3 → 2014.2 |
To post a comment you must log in.
After looking around a bit further, I'm not sure whether the correct fix would be to revert using image_type=None instead of 'raw' again at https:/ /github. com/openstack/ nova/blob/ master/ nova/virt/ libvirt/ driver. py#L3315 or whether this just uncovers some other bug that has been hiding out for longer.
In the log before the error, the config drive is created on local storage, but why is it created at all if the instance does not call for it?