yahoo-eng-team team mailing list archive

[NidhiMittalHada <nidhimittal19@xxxxxxxxx>]

Public bug reported:

stack@controller:~/devstack$ nova help volume-attach
usage: nova volume-attach <server> <volume> [<device>]

Attach a volume to a server.

Positional arguments:
  <server>  Name or ID of server.
  <volume>  ID of the volume to attach.
  <device>  Name of the device e.g. /dev/vdb. Use "auto" for autoassign (if
            supported). Libvirt driver will use default device name.


As shown below:

[root@greglinux2 ~(keystone_admin)]# nova volume-attachments e9c63adc-e837-4108-b5cf-10a8f147a5ab
+----+--------+-----------+-----------+
| ID | DEVICE | SERVER ID | VOLUME ID |
+----+--------+-----------+-----------+
+----+--------+-----------+-----------+
[root@greglinux2 ~(keystone_admin)]# 
[root@greglinux2 ~(keystone_admin)]# 
[root@greglinux2 ~(keystone_admin)]# 

[root@greglinux2 ~(keystone_admin)]# nova volume-attach e9c63adc-e837-4108-b5cf-10a8f147a5ab f0990f38-8fc5-4710-b9ac-e846b6c634cb /dev/vdb
+----------+--------------------------------------+
| Property | Value                                |
+----------+--------------------------------------+
| device   | /dev/vdb                             |>>>>>>>>>  attached as device /dev/vdb
| id       | f0990f38-8fc5-4710-b9ac-e846b6c634cb |
| serverId | e9c63adc-e837-4108-b5cf-10a8f147a5ab |
| volumeId | f0990f38-8fc5-4710-b9ac-e846b6c634cb |
+----------+--------------------------------------+
[root@greglinux2 ~(keystone_admin)]# 
[root@greglinux2 ~(keystone_admin)]# 


[root@greglinux2 ~(keystone_admin)]# 
[root@greglinux2 ~(keystone_admin)]# 
[root@greglinux2 ~(keystone_admin)]# nova volume-attach e9c63adc-e837-4108-b5cf-10a8f147a5ab f0990f38-8fc5-4710-b9ac-e846b6c634cb /dev/vdc >>>
+----------+--------------------------------------+
| Property | Value                                |
+----------+--------------------------------------+
| device   | /dev/vdb                             | >>>>> Still attached as /dev/vdb !!!!
| id       | f0990f38-8fc5-4710-b9ac-e846b6c634cb |
| serverId | e9c63adc-e837-4108-b5cf-10a8f147a5ab |
| volumeId | f0990f38-8fc5-4710-b9ac-e846b6c634cb |
+----------+--------------------------------------+
[root@greglinux2 ~(keystone_admin)]# 
[root@greglinux2 ~(keystone_admin)]# 


It looks like nova is not considering <device> parameter at all.
Is it expected?
Looking into code to reason this.

** Affects: nova
     Importance: Undecided
     Assignee: NidhiMittalHada (nidhimittal19)
         Status: In Progress

** Changed in: nova
     Assignee: (unassigned) => NidhiMittalHada (nidhimittal19)

** Changed in: nova
       Status: New => In Progress

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

Title:
  Nova volume-attach doesnt care for <device> name given

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  stack@controller:~/devstack$ nova help volume-attach
  usage: nova volume-attach <server> <volume> [<device>]

  Attach a volume to a server.

  Positional arguments:
    <server>  Name or ID of server.
    <volume>  ID of the volume to attach.
    <device>  Name of the device e.g. /dev/vdb. Use "auto" for autoassign (if
              supported). Libvirt driver will use default device name.

  
  As shown below:

  [root@greglinux2 ~(keystone_admin)]# nova volume-attachments e9c63adc-e837-4108-b5cf-10a8f147a5ab
  +----+--------+-----------+-----------+
  | ID | DEVICE | SERVER ID | VOLUME ID |
  +----+--------+-----------+-----------+
  +----+--------+-----------+-----------+
  [root@greglinux2 ~(keystone_admin)]# 
  [root@greglinux2 ~(keystone_admin)]# 
  [root@greglinux2 ~(keystone_admin)]# 

  [root@greglinux2 ~(keystone_admin)]# nova volume-attach e9c63adc-e837-4108-b5cf-10a8f147a5ab f0990f38-8fc5-4710-b9ac-e846b6c634cb /dev/vdb
  +----------+--------------------------------------+
  | Property | Value                                |
  +----------+--------------------------------------+
  | device   | /dev/vdb                             |>>>>>>>>>  attached as device /dev/vdb
  | id       | f0990f38-8fc5-4710-b9ac-e846b6c634cb |
  | serverId | e9c63adc-e837-4108-b5cf-10a8f147a5ab |
  | volumeId | f0990f38-8fc5-4710-b9ac-e846b6c634cb |
  +----------+--------------------------------------+
  [root@greglinux2 ~(keystone_admin)]# 
  [root@greglinux2 ~(keystone_admin)]# 

  
  [root@greglinux2 ~(keystone_admin)]# 
  [root@greglinux2 ~(keystone_admin)]# 
  [root@greglinux2 ~(keystone_admin)]# nova volume-attach e9c63adc-e837-4108-b5cf-10a8f147a5ab f0990f38-8fc5-4710-b9ac-e846b6c634cb /dev/vdc >>>
  +----------+--------------------------------------+
  | Property | Value                                |
  +----------+--------------------------------------+
  | device   | /dev/vdb                             | >>>>> Still attached as /dev/vdb !!!!
  | id       | f0990f38-8fc5-4710-b9ac-e846b6c634cb |
  | serverId | e9c63adc-e837-4108-b5cf-10a8f147a5ab |
  | volumeId | f0990f38-8fc5-4710-b9ac-e846b6c634cb |
  +----------+--------------------------------------+
  [root@greglinux2 ~(keystone_admin)]# 
  [root@greglinux2 ~(keystone_admin)]# 


  It looks like nova is not considering <device> parameter at all.
  Is it expected?
  Looking into code to reason this.

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