Cannot boot instance with metadata
Bug #833856 reported by
Brian Waldon
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Brian Waldon | ||
Bug Description
Here's the command I ran:
nova boot --image=1 --flavor=2 --meta one=two trouser
The flat_injected flag is set to 'false'. I get the following traceback from nova-compute.log: http://
Related branches
lp:~rackspace-titan/nova/boot-failure-lp833856
- Dan Prince (community): Approve
- Ed Leafe (community): Approve
- Josh Kearney (community): Approve
-
Diff: 14 lines (+2/-3)1 file modifiednova/virt/xenapi/vmops.py (+2/-3)
lp:~rackspace-titan/nova/build-failure-lp833856-d4
- OpenStack release team: Pending requested
-
Diff: 14 lines (+2/-3)1 file modifiednova/virt/xenapi/vmops.py (+2/-3)
Revision history for this message
| Brian Waldon (bcwaldon) wrote | #1 |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → diablo-4 |
| Changed in nova: | |
| milestone: | diablo-4 → 2011.3 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
The recent config-drive MP added a code path that bypassed the flat_injected flag in virt/xenapi/