yahoo-eng-team team mailing list archive

[YaoZheng_ZTE <zheng.yao1@xxxxxxxxxx>]

Public bug reported:

Reproducing method as following:
1、create one instance

[root@opencosf0ccfb2525a94ffa814d647f08e4d6a4 ~(keystone_admin)]# nova list
+--------------------------------------+---------+--------+------------+-------------+-------------------+
| ID                                   | Name    | Status | Task State | Power State | Networks          |
+--------------------------------------+---------+--------+------------+-------------+-------------------+
| dc7c8242-9e02-4acf-9ae4-08030380e629 | test_zy | ACTIVE | -          | Running     | net=192.168.0.111 |
+--------------------------------------+---------+--------+------------+-------------+-------------------+
2、run "nova volume-attach instance_id  volume_id ".

3、after step2, the volume attached the instance successfuly.

4、run "nova volume-attach instance_id  volume_id ", you will find the exception as following:
[root@opencosf0ccfb2525a94ffa814d647f08e4d6a4 ~(keystone_admin)]# nova volume-attach  dc7c8242-9e02-4acf-9ae4-08030380e629  1435df8a-c4d6-4993-a0fd-4f57de66a28e
ERROR (BadRequest): Invalid volume: volume '1435df8a-c4d6-4993-a0fd-4f57de66a28e' status must be 'available'. Currently in 'in-use' (HTTP 400) (Request-ID: req-45902cbb-1f00-432f-bfbf-b041bdcc2695)

5、Execute command : nova reboot --hard <instance_id> ,
  then login to the instance , you will find the volume attached as /dev/vdb don't work ok

** 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/1471167

Title:
  A volume attached one instance not working properly in K version

Status in OpenStack Compute (Nova):
  New

Bug description:
  Reproducing method as following:
  1、create one instance

  [root@opencosf0ccfb2525a94ffa814d647f08e4d6a4 ~(keystone_admin)]# nova list
  +--------------------------------------+---------+--------+------------+-------------+-------------------+
  | ID                                   | Name    | Status | Task State | Power State | Networks          |
  +--------------------------------------+---------+--------+------------+-------------+-------------------+
  | dc7c8242-9e02-4acf-9ae4-08030380e629 | test_zy | ACTIVE | -          | Running     | net=192.168.0.111 |
  +--------------------------------------+---------+--------+------------+-------------+-------------------+
  2、run "nova volume-attach instance_id  volume_id ".

  3、after step2, the volume attached the instance successfuly.

  4、run "nova volume-attach instance_id  volume_id ", you will find the exception as following:
  [root@opencosf0ccfb2525a94ffa814d647f08e4d6a4 ~(keystone_admin)]# nova volume-attach  dc7c8242-9e02-4acf-9ae4-08030380e629  1435df8a-c4d6-4993-a0fd-4f57de66a28e
  ERROR (BadRequest): Invalid volume: volume '1435df8a-c4d6-4993-a0fd-4f57de66a28e' status must be 'available'. Currently in 'in-use' (HTTP 400) (Request-ID: req-45902cbb-1f00-432f-bfbf-b041bdcc2695)

  5、Execute command : nova reboot --hard <instance_id> ,
    then login to the instance , 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/1471167/+subscriptions