← Back to team overview

openstack team mailing list archive

Re: Can't attach a RBD volume to an instance

 

On 05/25/2012 01:31 AM, Sébastien Han wrote:
Hi everyone,

I setup a ceph cluster and I use the RBD driver for nova-volume.
I can create volumes and snapshots but currently I can't attach them to
an instance.
Apparently the volume is detected as busy but it's not, no matter which
name I choose.
I tried from horizon and the command line, same issue.

$ nova --debug volume-attach de3743be-69be-4ec3-8de3-fc7df6903a97 12
/dev/vdc
connect: (localhost, 5000)
send: 'POST /v2.0/tokens HTTP/1.1\r\nHost:
localhost:5000\r\nContent-Length: 100\r\ncontent-type:
application/json\r\naccept-encoding: gzip, deflate\r\naccept:
application/json\r\nuser-agent: python-novaclient\r\n\r\n{"auth":
{"tenantName": "admin", "passwordCredentials": {"username": "admin",
"password": "admin"}}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Type: application/json
header: Vary: X-Auth-Token
header: Date: Fri, 25 May 2012 08:29:46 GMT
header: Transfer-Encoding: chunked
connect: (172.17.1.6, 8774)
send: u'GET
/v2/d1f5d27ccf594cdbb034c8a4123494e9/servers/de3743be-69be-4ec3-8de3-fc7df6903a97
HTTP/1.1\r\nHost: 172.17.1.6:8774
<http://172.17.1.6:8774>\r\nx-auth-project-id: admin\r\nx-auth-token:
37ff6354b9114178889128175494c666\r\naccept-encoding: gzip,
deflate\r\naccept: application/json\r\nuser-agent:
python-novaclient\r\n\r\n'
reply: 'HTTP/1.1 200 OK\r\n'
header: X-Compute-Request-Id: req-fc7686dd-7dff-4ea2-b2dd-be584dadb7c1
header: Content-Type: application/json
header: Content-Length: 1371
header: Date: Fri, 25 May 2012 08:29:46 GMT
send: u'POST
/v2/d1f5d27ccf594cdbb034c8a4123494e9/servers/de3743be-69be-4ec3-8de3-fc7df6903a97/os-volume_attachments
HTTP/1.1\r\nHost: 172.17.1.6:8774
<http://172.17.1.6:8774>\r\nContent-Length: 60\r\nx-auth-project-id:
admin\r\naccept-encoding: gzip, deflate\r\naccept:
application/json\r\nx-auth-token:
37ff6354b9114178889128175494c666\r\nuser-agent:
python-novaclient\r\ncontent-type:
application/json\r\n\r\n{"volumeAttachment": {"device": "/dev/vdc",
"volumeId": 12}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: X-Compute-Request-Id: req-4a22f603-4aad-4ae9-99a2-6a7bcacf974f
header: Content-Type: application/json
header: Content-Length: 48
header: Date: Fri, 25 May 2012 08:29:46 GMT
$ echo $?
0

See the logs here:
http://paste.openstack.org/show/18163/

Hi Seb,

It looks like the DeviceIsBusy exception is raised when libvirt
returns failure for any reason when attaching a volume. Try turning on
debug logging for libvirt and attaching again, and posting the logs
from libvirt.

You might need to upgrade libvirt - the version in Ubuntu 12.04 should
work, or upstream libvirt 0.9.12.

Josh

If you need more information let me know :)
Thank you in advance.

Cheers.

~Seb


Follow ups

References