** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1223611
Title:
Can not attach a volume to a running compute instance
Status in OpenStack Compute (Nova):
Invalid
Bug description:
When I attempt to attach a volume using the nova cli or horizon:
$ nova volume-attach 7a0a3ffa-603a-4758-8533-32ffd9974d03
66e834db-0f98-45fd-bfa0-6386f4a965a4 /dev/vdb
+----------+--------------------------------------+
| Property | Value |
+----------+--------------------------------------+
| device | /dev/hdb |
| serverId | 7a0a3ffa-603a-4758-8533-32ffd9974d03 |
| id | 66e834db-0f98-45fd-bfa0-6386f4a965a4 |
| volumeId | 66e834db-0f98-45fd-bfa0-6386f4a965a4 |
+----------+--------------------------------------+
(note the returned device is /dev/hdb not /dev/vdb)
In the error logs on the compute host:
... a large stack dump and ...
/var/log/nova/nova-compute.log: 2013-09-10 16:57:26.979 4774 TRACE
nova.openstack.common.rpc.amqp libvirtError: unsupported configuration: disk
bus 'ide' cannot be hotplugged.
/var/log/libvirt/libvirtd.log: 2013-09-10 23:57:23.529+0000: 1886: error :
qemuDomainAttachDeviceDiskLive:5870 : unsupported configuration: disk bus 'ide'
cannot be hotplugged.
libvirt uses the device name as a hint as to what driver to use when
attaching a new device. The instance has been booted from another volume which
means volumes can be attached successfully (but only on boot.)
I have also tried specifying /dev/sdb, /dev/xvdb with the same
failure. Specifying just 'vdb' raises InvalidDevicePath.
I am running nova-compute on Ubuntu from a package, version
2013.1.2-0ubuntu1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1223611/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
