Trace this bug on more clear one
https://bugs.launchpad.net/nova/+bug/1379212, mark this as invalid.
** Changed in: nova
Assignee: Rui Chen (kiwik-chenrui) => (unassigned)
** Changed in: nova
Status: Confirmed => 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/1312164
Title:
using <device> as "auto" in "nova volume-attach" command caused
attach fail
Status in OpenStack Compute (Nova):
Invalid
Bug description:
Environment:
1. A lvm volume named "vol1" is created, the volume id is
"7ee430ee-0ee8-4718-90bc-21f6b47222d9".
2. A server named "gzm" is running.
Test Steps:
Execute command "nova volume-attach gzm 7ee430ee-0ee8-4718-90bc-21f6b47222d9
auto", and then return :
+----------+--------------------------------------+
| Property | Value |
+----------+--------------------------------------+
| device | /dev/hda |
| serverId | ec9ce811-4f43-4bc1-96d9-56fe65e5b63f |
| id | 7ee430ee-0ee8-4718-90bc-21f6b47222d9 |
| volumeId | 7ee430ee-0ee8-4718-90bc-21f6b47222d9 |
+----------+--------------------------------------+
In fact, when I inspected the xml of the server, I found the volume "vol1"
is not attached success.
Besides, my first vol's(volume created when creating the server) device name
was "hda"(<target dev='vda' bus='virtio'/> in xml).
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1312164/+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
