yahoo-eng-team team mailing list archive

[Nikola Đipanov <ndipanov@xxxxxxxxxx>]

Ok so I've looked at this and seems to work as expected now:

$ for i in {1..5}; do cinder create --display-name volume_$i 1; done
$ cinder list
+--------------------------------------+-----------+----------+------+-------------+----------+-------------+
|                  ID                  |   Status  |   Name   | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+-----------+----------+------+-------------+----------+-------------+
| 0afc6137-bb95-433b-bf47-31edb4f22109 | available | volume_5 |  1   |     None    |  false   |             |
| 4368ddd6-6d1c-436f-abf2-328de4af4c14 | available | volume_2 |  1   |     None    |  false   |             |
| 5899a09f-a052-4328-80a1-dccefde7ffbb | available | volume_4 |  1   |     None    |  false   |             |
| 65bb1a41-39c9-47bf-b48e-3f873ece7cc8 | available | volume_3 |  1   |     None    |  false   |             |
| a163bc28-7980-4c50-8ae3-cde63037096f | available | volume_1 |  1   |     None    |  false   |             |
+--------------------------------------+-----------+----------+------+-------------+----------+-------------+
$ cinder list | grep "^| \w" | awk '{ print $2 }' | xargs -P5 -I {} nova volume-attach d6544df8-7e3a-4f45-ad60-deff250e07c3 {}
</ volume attach output snipped>
$ cinder list 
+--------------------------------------+--------+----------+------+-------------+----------+--------------------------------------+
|                  ID                  | Status |   Name   | Size | Volume Type | Bootable |             Attached to              |
+--------------------------------------+--------+----------+------+-------------+----------+--------------------------------------+
| 0afc6137-bb95-433b-bf47-31edb4f22109 | in-use | volume_5 |  1   |     None    |  false   | d6544df8-7e3a-4f45-ad60-deff250e07c3 |
| 4368ddd6-6d1c-436f-abf2-328de4af4c14 | in-use | volume_2 |  1   |     None    |  false   | d6544df8-7e3a-4f45-ad60-deff250e07c3 |
| 5899a09f-a052-4328-80a1-dccefde7ffbb | in-use | volume_4 |  1   |     None    |  false   | d6544df8-7e3a-4f45-ad60-deff250e07c3 |
| 65bb1a41-39c9-47bf-b48e-3f873ece7cc8 | in-use | volume_3 |  1   |     None    |  false   | d6544df8-7e3a-4f45-ad60-deff250e07c3 |
| a163bc28-7980-4c50-8ae3-cde63037096f | in-use | volume_1 |  1   |     None    |  false   | d6544df8-7e3a-4f45-ad60-deff250e07c3 |
+--------------------------------------+--------+----------+------+-------------+----------+--------------------------------------+

So based on the above I will mark as invalid for Nova

** Changed in: nova
       Status: Confirmed => 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/944383

Title:
  There is no way to recover/cleanup  a volume in an "attaching" state

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

Bug description:
  While trying to attach more than one volume to an instance two volumes
  hung in an "attaching" state.   A volume-detach on that volume returns
  a 404  and a volume-delete returns a 500.

  It seems that a volume-force-detach is needed to clean up volumes in a
  hung state.

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