Handle the case of there being no kernel-id in the cloud meta-data

Bug #920453 reported by Andreas Hasenack on 2012-01-23
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Client
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.

Thomas Herve (therve) on 2012-01-24
Changed in landscape-client:
milestone: backlog → 12.01.2
assignee: nobody → Thomas Herve (therve)
Thomas Herve (therve) on 2012-01-24
Changed in landscape-client:
status: New → In Progress
Thomas Herve (therve) on 2012-01-24
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.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers