yahoo-eng-team team mailing list archive

[John Griffith <1387945@xxxxxxxxxxxxxxxxxx>]

This is a VERY old and long running issue with how things work on the
Nova side of the house.  The volumes are going to get attached to the
next available drive mapping (vdb, vdc, vdd) based on the Block Device
Mapping table in Nova.  The specification you provide to attach-volume
is really more of a hint than anything else.

Anyway, over the past the answer has been "just use 'auto'" and save
yourself the false sense of control here.  Not acceptable for some,
regardless this is a Nova operation and Cinder actually has no control
or input here.

Marking invalid for Cinder and adding Nova.

** Changed in: cinder
       Status: New => Invalid

** Also affects: nova
   Importance: Undecided
       Status: New

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

Title:
  "nova volume-attach" is giving wrong device ID

Status in Cinder:
  Invalid
Status in OpenStack Compute (Nova):
  New

Bug description:
  Sometimes while attaching volume to the instance using "nova volume-
  attach" it is giving wrong device ID (mountpoint : /dev/vdb).

  root@techpatron:~# nova volume-attach VM1 201b2fe8-7f77-446d-a6e4-5d077914329c
  +----------+--------------------------------------+
  | Property | Value                                |
  +----------+--------------------------------------+
  | device   | /dev/vdd                             |
  | id       | 201b2fe8-7f77-446d-a6e4-5d077914329c |
  | serverId | 2f319155-06d2-4aca-9f0f-49b415112568 |
  | volumeId | 201b2fe8-7f77-446d-a6e4-5d077914329c |
  +----------+--------------------------------------+

  Here it is showing "/dev/vdd", but volume actually attached as
  "/dev/vdc" to the instance "VM1".

  Because of this when I am running some automation scripts (which will
  perform operations on the attached device with in the instance) facing
  problem. From the output that script taking the device id as
  "/dev/vdd" but device is attached to some other mount point.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1387945/+subscriptions