Boot from volume faild with availability_zone option, in case of cinder do not have availability_zone
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Matt Riedemann | ||
Kilo |
Fix Released
|
Medium
|
Matt Riedemann |
Bug Description
My envirement ,Nova has 2 availability_zone and Cinder has no availability_zone.
When I run two command "cinder create" and "nova boot" separately , it is finished normally.
But run at one time, and an error occurs as below.(It is the same on the dashboard)
----
$ nova boot --flavor m1.small --block-device source=
$ nova list
+------
| ID | Name | Status | Task State | Power State | Networks |
+------
| a0dc0f03-
+------
$ nova show
+------
| Property | Value |
+------
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-STS:vm_state | error |
| OS-SRV-
| OS-SRV-
| accessIPv4 | |
| accessIPv6 | |
| config_drive | |
| created | 2015-09-
| fault | {"message": "Build of instance a0dc0f03-
| | filter_properties) |
| | File \"/usr/
| | 'create.error', fault=e) |
| | File \"/usr/
| | six.reraise(
| | File \"/usr/
| | block_device_
| | File \"/usr/
| | return self.gen.next() |
| | File \"/usr/
| | reason=msg) |
| | ", "created": "2015-09-
| flavor | m1.small (090955df-
| hostId | bf381a5d2d9136f
| id | a0dc0f03-
| image | Attempt to boot from volume - no image supplied |
| key_name | - |
| metadata | {} |
| name | test1 |
| os-extended-
| status | ERROR |
| tenant_id | 3296a2ca68a04a1
| updated | 2015-09-
| user_id | ab2a6867991f4cd
+------
Version : Kilo
description: | updated |
description: | updated |
Changed in nova: | |
assignee: | nobody → Ikuo Kumagai (i-kumagai) |
tags: | added: availability-zones spawn volumes |
Changed in nova: | |
importance: | Undecided → Medium |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Is there more stacktrace to that error? I'd expect to see something failing down in the nova.virt. block_device attach code somewhere, or maybe an error in the cinder logs?