Handle the case of there being no kernel-id in the cloud meta-data
Bug #920453 reported by
Andreas Hasenack
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Client |
Fix Released
|
High
|
Thomas Herve | ||
Bug Description
As we do with the ramdisk-id, handling the case where it is not available, we now have to do the same for the kernel-id.
On openstack, if there is no kernel-id associated with the image, openstack assumes the image is bootable and tries to boot it. In our internal cloud, from oneiric onwards that's the case.
In amazon, the same happens with hvm images/instances I'm told.
Related branches
lp:~therve/landscape-client/cloud-missing-kernel
- Alberto Donato (community): Approve
- Free Ekanayaka (community): Approve
-
Diff: 83 lines (+27/-5)3 files modifiedlandscape/broker/registration.py (+8/-4)
landscape/broker/tests/test_registration.py (+18/-0)
landscape/message_schemas.py (+1/-1)
| Changed in landscape-client: | |
| milestone: | backlog → 12.01.2 |
| assignee: | nobody → Thomas Herve (therve) |
| Changed in landscape-client: | |
| status: | New → In Progress |
| Changed in landscape-client: | |
| status: | In Progress → Fix Committed |
| Changed in landscape-client: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
