yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
   Importance: Medium => Undecided

** Changed in: nova
       Status: Confirmed => Expired

** Changed in: nova
     Assignee: Anseela M M (anseela-m00) => (unassigned)

-- 
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/1153842

Title:
  nova volume-attach <vmid> <volumeid> auto returns always /dev/sdb on
  Hyper-V

Status in compute-hyperv:
  New
Status in OpenStack Compute (nova):
  Expired

Bug description:
  To reproduce the issue it's enough to attach two volumes to a VM
  without providing an explicit mount point.

  cinder create 1
  cinder create 1

  nova boot ... vm1

  nova volume-attach vmid <volumeid1> auto
  nova volume-attach vmid <volumeid2> auto

  As a result:

  1) When the machine is deleted only one of the volumes becomes available again on Cinder, the second one figures as still attached.
  2) Live migration fails as only one volume is reported in the "block_device_info" dict.

  More inconsistent behaviours can happen, for example during cold
  migration / resize.

  Workaround:

  Always provide a mount point e.g.:

  nova volume-attach vmid <volumeid1> /dev/sdb
  nova volume-attach vmid <volumeid2> /dev/sdc

To manage notifications about this bug go to:
https://bugs.launchpad.net/compute-hyperv/+bug/1153842/+subscriptions