boot from image created with nova image-create from a volume backed instance is rejected
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Balazs Gibizer |
Bug Description
It is not possible to boot the image that was created with nova image-create from a volume backed instance.
Steps to reproduce:
stack@stack:
+------
| Property | Value |
+------
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-STS:vm_state | building |
| OS-SRV-
| OS-SRV-
| accessIPv4 | |
| accessIPv6 | |
| adminPass | wvUa22QCTaoR |
| config_drive | |
| created | 2014-10-
| flavor | install-test (100) |
| hostId | |
| id | 9ad985f6-
| image | Attempt to boot from volume - no image supplied |
| key_name | - |
| metadata | {} |
| name | volume-backed |
| os-extended-
| progress | 0 |
| security_groups | default |
| status | BUILD |
| tenant_id | 89dda4659c7e403
| updated | 2014-10-
| user_id | 4c9283c1cbc54d6
+------
stack@stack:
+------
| Property | Value |
+------
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-STS:vm_state | active |
| OS-SRV-
| OS-SRV-
| accessIPv4 | |
| accessIPv6 | |
| config_drive | |
| created | 2014-10-
| flavor | install-test (100) |
| hostId | 337fdcb2bd1ee3a
| id | 9ad985f6-
| image | Attempt to boot from volume - no image supplied |
| key_name | - |
| metadata | {} |
| name | volume-backed |
| os-extended-
| private network | 10.0.0.2 |
| progress | 0 |
| security_groups | default |
| status | ACTIVE |
| tenant_id | 89dda4659c7e403
| updated | 2014-10-
| user_id | 4c9283c1cbc54d6
+------
stack@stack:
stack@stack:
+------
| Property | Value |
+------
| OS-EXT-
| created | 2014-10-
| id | c0283b1b-
| metadata bdm_v2 | True |
| metadata block_device_
| metadata checksum | 4eada48c2843d2a
| metadata container_format | ami |
| metadata disk_format | ami |
| metadata image_id | 70b5a8e8-
| metadata image_name | cirros-
| metadata kernel_id | 3d8e1ae1-
| metadata min_disk | 0 |
| metadata min_ram | 0 |
| metadata ramdisk_id | 5634fe26-
| metadata root_device_name | /dev/vda |
| metadata size | 25165824 |
| minDisk | 0 |
| minRam | 0 |
| name | image-from-
| progress | 100 |
| status | ACTIVE |
| updated | 2014-10-
+------
stack@stack:
ERROR (BadRequest): Block Device Mapping is Invalid: Boot sequence for the instance and image/block device mapping combination is not valid. (HTTP 400) (Request-ID: req-87ae0d82-
It seems that it is only a validation problem on API level as the same image can be booted with --image parameter.
Changed in nova: | |
assignee: | nobody → Balazs Gibizer (balazs-gibizer) |
Changed in nova: | |
importance: | Undecided → Low |
Changed in nova: | |
milestone: | none → kilo-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | kilo-3 → 2015.1.0 |
Fix proposed to branch: master /review. openstack. org/128891
Review: https:/