yahoo-eng-team team mailing list archive

[YaoZheng_ZTE <zheng.yao1@xxxxxxxxxx>]

** Changed in: nova
       Status: Confirmed => Fix Released

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

Title:
  A volume was attached to the vm instance twice, the vm instance will
  cannot normally use this volume

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Reproducing method as following:
  1: create a vm instance named test_vm1
  2:create a volume named test_volume1
  3:run nova command : nova volume-attach   test_vm1   test_volume1 , then confirmed the volume attached the instance ok
  [root@opencos_cjl ~(keystone_admin)]# nova list
  +--------------------------------------+-------------------------------------------------------+--------+------------+-------------+-----------------------------------------------+
  | ID                                   | Name                                                  | Status | Task State | Power State | Networks                                      |
  +--------------------------------------+-------------------------------------------------------+--------+------------+-------------+-----------------------------------------------+
  | b917e46b-539f-4024-bced-73c6b7c00ea2 | TestZteOneVolumeAttatchTo2Servers-instance-1863856957 | ACTIVE | -          | Running     | zfl_internal_net=192.168.0.107                |
  | d0e5f1a4-9da1-4c39-a17d-12e43d20cd10 | TestZteOneVolumeAttatchTo2Servers-instance-8729469    | ACTIVE | -          | Running     | zfl_internal_net=192.168.0.108                |
  | 9a6c6aff-d77c-4699-a41f-abb9d8e4b09e | test2                                                 | ACTIVE | -          | Running     | zfl_internal_net=192.168.0.101, 10.43.210.232 |
  | 4a338d56-0daf-48d8-bcb5-d46de74b3887 | test_vm1                                              | ACTIVE | -          | Running     | zfl_internal_net=192.168.0.109                |
  +--------------------------------------+-------------------------------------------------------+--------+------------+-------------+-----------------------------------------------+
  [root@opencos_cjl ~(keystone_admin)]# 
  [root@opencos_cjl ~(keystone_admin)]# nova volume-list
  +--------------------------------------+-----------+--------------+------+-------------+--------------------------------------+
  | ID                                   | Status    | Display Name | Size | Volume Type | Attached to                          |
  +--------------------------------------+-----------+--------------+------+-------------+--------------------------------------+
  | 22ad798d-77d2-4031-8b82-a5512e9f9284 | in-use    | test_volume1 | 1    | None        | 4a338d56-0daf-48d8-bcb5-d46de74b3887 |
  | 76f708fe-0e47-4f1a-a43b-08001f6a65d9 | available | test         | 1    | None        |                                      |
  +--------------------------------------+-----------+--------------+------+-------------+--------------------------------------+

  4: run nova command again : nova volume-attach   test_vm1   test_volume1 , then will raise exception as following:
     
  [root@opencos_cjl ~(keystone_admin)]# nova volume-attach 4a338d56-0daf-48d8-bcb5-d46de74b3887  22ad798d-77d2-4031-8b82-a5512e9f9284
  ERROR: Invalid volume: Volume has been attached to the instance (HTTP 400) (Request-ID: req-24f8b244-9809-41e4-b8e8-8a5ca7157c1c)
  the exception is correct , but the issuse is: after the step 4, the  test_vm1 cannot normally use the  test_volume1. If you login the  test_vm1 os, you will find the volume attached as /dev/vdb don't work ok.

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