I'm marking the nova bug as won't fix since this is working as designed
for the libvirt driver since liberty, the libvirt driver ignores the
requested device name now. It was never really working with the
requested device name, you'd just get lucky if it worked. Things are
more explicit now.
I've added the openstack-api-site project to this bug since we should
update the volume attach API docs to note this wrinkle.
** Also affects: openstack-manuals
Importance: Undecided
Status: New
** Also affects: openstack-api-site
Importance: Undecided
Status: New
** No longer affects: openstack-manuals
** Changed in: nova
Status: Confirmed => Won't Fix
--
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/1479214
Title:
nova can't attach volume to specific device name
Status in OpenStack Compute (nova):
Won't Fix
Status in openstack-api-site:
New
Bug description:
Nova attach volume cli support one option named device, it can specify this
volume where to mount.
But it doesn't work. Volume will be attached to device which is determined by
nova compute.
Maybe this bug was caused at following code:
https://github.com/openstack/nova/blob/c5db407bb22e453a4bca22de1860bb6ce6090782/nova/virt/libvirt/driver.py#L6823
It will ignore device name which user assign, then auto select disk from
blockinfo.
My nova git environment is
nova: 14d00296b179fcf115cf13d37b2f0b5b734d298d
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1479214/+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
