image-store does not support images without a ramdisk

[Scott Moser]

the lucid images do not need a ramdisk to boot in uec. as such, we're not shipping one.

The image store proxy expects that there is a ramdisk and will fail if there is not.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: python-image-store-proxy 1.0.4-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-21.32-server 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-server x86_64
Architecture: amd64
Date: Fri Apr 30 08:09:32 2010
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: image-store-proxy

[Scott Moser (smoser)]

In maverick, we hope to not ship ramdisks separately from the kernel at all. That makes this bug critical for Maverick images.

[Scott Moser (smoser)]

(comment 2 should have said "separately from the image")

[Gustavo Niemeyer (niemeyer)]

I have discussed this with Scott over the phone a while ago, but didn't write anything in the bug about it. Sorry about that.

So here are the possible outcomes with this bug:

1) I fix the problem myself
2) I guide someone else to fixing the problem
3) The feature is removed from the Image Store
4) The feature goes broken in Maverick

(1) has been hard for me in the last couple of months, due to the work in Ensemble; (2) would be ideal for me, but it seems we have no one else willing to invest time in fixing the problem; (3) and (4) would be quite unfortunate IMO, since it makes the image installation a boring manual process for the end user, and thus damages the bootstrapping use cases.

[Gustavo Niemeyer (niemeyer)]

Oh, there's another one which I missed:

5) Provide a ramdisk and kernel to images installed via the store.

This would be pretty easy from an Image Store perspective, of course.

[Dave Walker (davewalker)]

Is there an update on the situation of this issue? What is blocking progression?

Thanks.

[Scott Moser (smoser)]

As this doesn't look like its going to be fixed in image-store-proxy anytime soon, it looks like we will have to work around the issue.

What we'll do is:
a.) karmic images: use the ramdisk they have
b.) lucid images: copy ramdisk out of image, and use it
c.) maverick images:
  - for maverick host (that use the loader capability): register bogus (or very small) and un-used ramdisk
  - for lucid or older hosts: copy out ramdisk in the image and use it.\

[Thierry Carrez (ttx)]

Downgrading to Medium with the workaround

[Thierry Carrez (ttx)]

@Kate: I'll obviously leave it to you, but I'm not sure this is releasenotes material. It's an internal bug that affects our procedures to publish into the image store, not really a public-facing limitation.

[Thierry Carrez (ttx)]

Invalidating based on last comment

[Rolf Leggewie (r0lf)]

Karmic has long since stopped to receive any updates. Marking the Karmic task for this ticket as "Won't Fix".

[Rolf Leggewie (r0lf)]

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".