yahoo-eng-team team mailing list archive

[OpenStack Infra <1479214@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/280391
Committed: https://git.openstack.org/cgit/openstack/api-site/commit/?id=bc38fb73477a4ac4d031dc3228c4956a6c083f5d
Submitter: Jenkins
Branch:    master

commit bc38fb73477a4ac4d031dc3228c4956a6c083f5d
Author: Matt Riedemann <mriedem@xxxxxxxxxx>
Date:   Mon Feb 15 12:42:41 2016 -0800

    Note that nova libvirt driver no longer honors device name on volume attach
    
    Commit 0283234e837d9faf807e6e8da6ec6321ee56b31a in Liberty changed the
    nova libvirt driver to no longer honor user-supplied device names on the
    volume attachment request.
    
    This change updates the API docs to add a note about so users are aware
    that if they know they are hitting a libvirt-managed compute, device names
    for volume attachment are auto-generated.
    
    Change-Id: I42fbc5645414af99fedc49d5299c1e15d619d5bd
    Closes-Bug: #1479214


** Changed in: openstack-api-site
       Status: In Progress => Fix Released

-- 
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:
  Fix Released

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