yahoo-eng-team team mailing list archive

[zhangtralon <zhangchunlong1@xxxxxxxxxx>]

Public bug reported:

when specifying a volume to create a virtual machine, if the virtual machine fails to be created  for the first time with the parameter  delete_on_termination being set “true”, the specified volume will be deleted, which causes that the rescheduling fails.
for example:
1. upload a image
| 62aa6627-0a07-4ab4-a99f-2d99110db03e | cirros-0.3.2-x86_64-uec         | ACTIVE 
2.create a boot volume by the above image
cinder create --image-id 62aa6627-0a07-4ab4-a99f-2d99110db03e --availability-zone nova 1
| b821313a-9edb-474f-abb0-585a211589a6 | available | None |  1   |     None    |   true   |             |
3. create a virtual machine
nova boot --flavor m1.tiny  --nic net-id=28216e1d-f1c2-463b-8ae2-330a87e800d2 tralon_disk1  --block-device-mapping vda=b821313a-9edb-474f-abb0-585a211589a6::1:1
ERROR (BadRequest): Block Device Mapping is Invalid: failed to get volume b821313a-9edb-474f-abb0-585a211589a6. (HTTP 400) (Request-ID: req-486f7ab5-dc08-404e-8d4c-ac570d4f4aa1)
4. use the "cinder list" to find that the volume  b821313a-9edb-474f-abb0-585a211589a6 has been deleted
+----+--------+------+------+-------------+----------+-------------+
| ID | Status | Name | Size | Volume Type | Bootable | Attached to |
+----+--------+------+------+-------------+----------+-------------+
+----+--------+------+------+-------------+----------+-------------+

** Affects: nova
     Importance: Undecided
     Assignee: zhangtralon (zhangchunlong1)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => zhangtralon (zhangchunlong1)

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

Title:
  the boot volume will be deleted when  creating a virtual machine fails
  with the parameter delete_on_termination being set true

Status in OpenStack Compute (Nova):
  New

Bug description:
  when specifying a volume to create a virtual machine, if the virtual machine fails to be created  for the first time with the parameter  delete_on_termination being set “true”, the specified volume will be deleted, which causes that the rescheduling fails.
  for example:
  1. upload a image
  | 62aa6627-0a07-4ab4-a99f-2d99110db03e | cirros-0.3.2-x86_64-uec         | ACTIVE 
  2.create a boot volume by the above image
  cinder create --image-id 62aa6627-0a07-4ab4-a99f-2d99110db03e --availability-zone nova 1
  | b821313a-9edb-474f-abb0-585a211589a6 | available | None |  1   |     None    |   true   |             |
  3. create a virtual machine
  nova boot --flavor m1.tiny  --nic net-id=28216e1d-f1c2-463b-8ae2-330a87e800d2 tralon_disk1  --block-device-mapping vda=b821313a-9edb-474f-abb0-585a211589a6::1:1
  ERROR (BadRequest): Block Device Mapping is Invalid: failed to get volume b821313a-9edb-474f-abb0-585a211589a6. (HTTP 400) (Request-ID: req-486f7ab5-dc08-404e-8d4c-ac570d4f4aa1)
  4. use the "cinder list" to find that the volume  b821313a-9edb-474f-abb0-585a211589a6 has been deleted
  +----+--------+------+------+-------------+----------+-------------+
  | ID | Status | Name | Size | Volume Type | Bootable | Attached to |
  +----+--------+------+------+-------------+----------+-------------+
  +----+--------+------+------+-------------+----------+-------------+

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