Bug 1105018

Summary: RBD support seems incomplete
Product: Red Hat Enterprise Linux 6 Reporter: Emilien Macchi <emilien.macchi>
Component: qemu-kvmAssignee: Ademar Reis <areis>
Status: CLOSED NOTABUG QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.5CC: acathrow, bsarathy, chayang, emilien.macchi, juzhang, lyarwood, mkenneth, qzhang, sluo, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1109895 (view as bug list) Environment:
Last Closed: 2014-06-16 15:09:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1109895    

Description Emilien Macchi 2014-06-05 08:37:47 UTC
Description of problem:
On OpenStack Icehouse, when attaching a volume backend by Ceph (RBD) to a VM hosted on qemu-kvm, we get this error:
ibvirtError: internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk1' could not be initialized

Complete TRACE: http://paste.openstack.org/show/bfl0XYDGwerSwB65i3ID/

It seems that RBD support is not complete in qemu-kvm

Version-Release number of selected component (if applicable):
qemu-img-rhev-0.12.1.2-2.415.el6_5.8.x86_64
qemu-kvm-rhev-0.12.1.2-2.415.el6_5.8.x86_64

How reproducible:
Every time.

Steps to Reproduce:
1. Install OpenStack Icehouse with RBD backend for Cinder
2. Create a volume in Cinder and an instance in Nova
3. Attache the volume to volume to the VM and look at nova-compute logs

Actual results:
The volume fails to be attached.

Expected results:
The volume should be attached.

Comment 2 Ademar Reis 2014-06-05 17:18:21 UTC
Emilien, thank you for taking the time to enter a bug report with us. We're not able to guarantee the timeliness or suitability of a resolution for issues entered here because this is not a mechanism for requesting support, so if this issue is critical or in any way time sensitive, please raise a ticket through your regular Red Hat support channels to make certain  it receives the proper attention and prioritization to assure a timely resolution.

For information on how to contact the Red Hat production support team, please
visit: https://www.redhat.com/support/process/production/#howto

Comment 3 Ademar Reis 2014-06-05 17:22:31 UTC
Please include the output of the following commands:

# rpm -qa | egrep -i '(rbd|ceph)
# qemu-img -h | grep Supported

We also need the full command line used to invoke qemu. One way to extract it is using this command on the machine where the VM is being run:

# ps -auxww | grep qemu

(or you can add the respective log from /var/log/libvirt)

Comment 4 Emilien Macchi 2014-06-05 19:41:04 UTC
Hi,

Here is the ticket: https://access.redhat.com/support/cases/01115331/

For your information:
ceph-libs-0.80.1-2.el6.x86_64
ceph-0.80.1-2.el6.x86_64

Supported formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat qcow2 qed vhdx parallels nbd blkdebug host_cdrom host_floppy host_device file gluster gluster gluster gluster rb

I'll provide other informations later.
Thanks

Comment 6 Ademar Reis 2014-06-16 15:09:46 UTC
Based on the discussion at Customer case 01115331, looks like the issue has been identified: the customer had packages from EPEL installed, which don't include the symlink needed to enable CEPH support in qemu-kvm-rhev at runtime. 

When using the official, supported packages from ceph.com, support is enabled as expected.

The bug has been clonned against the EPEL ceph component: Bug 1109895.

This qemu-kvm bug is being closed as NOTABUG, given that the RHEL6 part appears to be fine.

Thanks.