yahoo-eng-team team mailing list archive

[lyanchih <lyan.h@xxxxxxxxxxxxxx>]

Public bug reported:

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

** Affects: nova
     Importance: Undecided
     Assignee: lyanchih (lyanchih)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => lyanchih (lyanchih)

-- 
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):
  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