Booting an image without a kernel/initrd on baremetal fails without telling user why
Bug #1100589 reported by
Clint Byrum
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
aeva black |
Bug Description
Steps to reproduce:
1. setup baremetal hypervisor
2. upload image without specifying kernel/initrd
3. boot server with said image
4. Wait till nova list/show shows the server as "ACTIVE"
5. observe system failing to boot with "invalid kernel" message after deploy kernel boots properly and lays image down.
6. on tftp server note that "kernel" is written as a json file that looks like a response from keystone about images.
What would I expect:
The node should immediately go into ERROR state, or preferably would fail on asking to boot with a baremetal flavor and no kernel.
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in nova: | |
assignee: | nobody → Devananda (devananda) |
status: | Triaged → Confirmed |
Changed in nova: | |
milestone: | none → grizzly-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-3 → 2013.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/19954
Review: https:/