yahoo-eng-team team mailing list archive

[zhu zhu <zhuzhubj@xxxxxxxxxx>]

Public bug reported:

1. create a cinder from an existed image

cinder create 2 --display-name hbvolume-newone --image-id 9769cbfe-2d1a-
4f60-9806-16810c666d7f

2. set the created volume with error status
cinder reset-state --state error 76f5e521-d45f-4675-851e-48f8e3a3f039

3. boot a vm from the created volume
nova boot --flavor 2 --block-device-mapping vda=76f5e521-d45f-4675-851e-48f8e3a3f039:::0 device-mapping-test2 --nic net-id=231eb787-e5bf-4e65-a822-25d37a84eab8

# cinder list
+--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
|                  ID                  |   Status  |   Display Name  | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
| 21c50923-7341-49ba-af48-f4a7e2099bfd | available |       None      |  1   |     None    |  false   |             |
| 76f5e521-d45f-4675-851e-48f8e3a3f039 |   error   |    hbvolume-2   |  2   |     None    |   true   |             |
| 92de3c7f-9c56-447a-b06a-a5c3bdfca683 | available | hbvolume-newone |  2   |     None    |   true   |             |
+--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+

#RESULTS
it reports "failed to get the volume"
ERROR (BadRequest): Block Device Mapping is Invalid: failed to get volume 76f5e521-d45f-4675-851e-48f8e3a3f039. (HTTP 400)

#Expected Message:
report the status of the volume is not correct to boot a VM

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

Title:
  Nova prompt wrong message when boot from a error status volume

Status in OpenStack Compute (Nova):
  New

Bug description:
  1. create a cinder from an existed image

  cinder create 2 --display-name hbvolume-newone --image-id 9769cbfe-
  2d1a-4f60-9806-16810c666d7f

  2. set the created volume with error status
  cinder reset-state --state error 76f5e521-d45f-4675-851e-48f8e3a3f039

  3. boot a vm from the created volume
  nova boot --flavor 2 --block-device-mapping vda=76f5e521-d45f-4675-851e-48f8e3a3f039:::0 device-mapping-test2 --nic net-id=231eb787-e5bf-4e65-a822-25d37a84eab8

  # cinder list
  +--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
  |                  ID                  |   Status  |   Display Name  | Size | Volume Type | Bootable | Attached to |
  +--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
  | 21c50923-7341-49ba-af48-f4a7e2099bfd | available |       None      |  1   |     None    |  false   |             |
  | 76f5e521-d45f-4675-851e-48f8e3a3f039 |   error   |    hbvolume-2   |  2   |     None    |   true   |             |
  | 92de3c7f-9c56-447a-b06a-a5c3bdfca683 | available | hbvolume-newone |  2   |     None    |   true   |             |
  +--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+

  #RESULTS
  it reports "failed to get the volume"
  ERROR (BadRequest): Block Device Mapping is Invalid: failed to get volume 76f5e521-d45f-4675-851e-48f8e3a3f039. (HTTP 400)

  #Expected Message:
  report the status of the volume is not correct to boot a VM

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