yahoo-eng-team team mailing list archive

[Rajesh Tailor <1982040@xxxxxxxxxxxxxxxxxx>]

Marking this bug Invalid, as it is resolved after providing microversion
with the command.

** Changed in: nova
       Status: Incomplete => Invalid

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

Title:
  stable/xena unable to attach multi-attach volume via "openstack nova
  add volume"

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Dear all

  I have encountered an error with Openstack Heat but I think this is
  something that is also affecting (or even caused by) a possible issue
  with nova.

  Here my post for HEAT team
  https://storyboard.openstack.org/#!/story/2010157

  I have installed stable/xena using openstack-ansible and I am
  operating several test vms in my ecosystem before to move to a
  production stage. Currently I am using Cinder integrated with Ceph (if
  you think it may be of any interest).

  Just to summarize a possible test procedure (for convenience I simply use CLI but with Horizon there is another workaround that I presented in the storyboard's post above):
  - create a multi-attach volume
  - create 2 instances that potentially want to share the volume
  - attach the volume to the first instance [it will work great!]
  - attache the volume to a second instance... you should receive the following error:

  openstack server add volume <serverID> <volumeID> --device /dev/vdb
  Multiattach volumes are only supported starting with compute API version 2.60. (HTTP 400) (Request-ID: req-5a60e72a-b7e2-49d6-81b2-c15753e054a2)

  BUT
  If I use the following command on the second attach:

  nova volume-attach <serverID> <volumeID> auto
  +-----------------------+--------------------------------------+
  | Property              | Value                                |
  +-----------------------+--------------------------------------+
  | delete_on_termination | False                                |
  | device                | /dev/vdb                             |
  | id                    | c292cdd5-7dc5-4714-bdb3-a309e8416232 |
  | serverId              | 7b6a0651-f4cd-4018-a042-58f695ab73aa |
  | tag                   | -                                    |
  | volumeId              | c292cdd5-7dc5-4714-bdb3-a309e8416232 |
  +-----------------------+--------------------------------------+

  it works properly!
  Is it expected because of some implementation task or is it a potential bug?

  Actually I am able to create and use multi-attach volumes but only by
  making manually the attachment with the commands reported above.

  Thanks for your kind attention and looking forward to hear by you.
  Best regards,
  Davide

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