karmic uec builds fail to publish due to 2 installed -ec2 kernels
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vm-builder (Ubuntu) |
Won't Fix
|
High
|
Unassigned | ||
Karmic |
Fix Released
|
High
|
Scott Moser | ||
Lucid |
Fix Released
|
High
|
Unassigned |
Bug Description
build 20100204 is the last karmic uec build to successfully publish to ec2.
The builds fail to publish with:
Thu Feb 18 05:13:57 GMT 2010: publishing -> ubuntu-
must provide kernel for each region
publish-image karmic-
failed daily build publisher: karmic /srv/ec2-
The call chain looks like:
uec-build-
publish-build-krd reads the '<prefix>
The problem is that the build ended up installing 2 versions of the -ec2 kernel (and also 2 versions of -virtual kernel). publish-build-krd expected only 1 of each type.
In investigating *why* this was the case, it can be reproduced by 'apt-get install uec^'. The uec seed data has the released versions of the kernels explicitly listed [1]. See linux-image-
There has been discussion in ubuntu-devel [2] on how Task: values would be updated with no clear solution. I believe the root issue is that the kernel linux-image packages are not the same package name (because of the ABI bump) and the program consuming or generating output doesn't realize that the -updates version replaces the released version.
This is currently only a problem on karmic, but it will become a problem on lucid as soon as there are kernels with new ABI in -updates.
--
[1] http://
[2] http://
Related branches
- Colin Watson: Approve
-
Diff: 15 lines (+0/-5)1 file modifieduec (+0/-5)
affects: | Ubuntu Lucid → vm-builder (Ubuntu Lucid) |
tags: | added: patch |
Changed in vm-builder (Ubuntu): | |
assignee: | Soren Hansen (soren) → nobody |
Changed in vm-builder (Ubuntu Lucid): | |
assignee: | Soren Hansen (soren) → nobody |
Changed in vm-builder (Ubuntu Lucid): | |
status: | Triaged → Fix Released |
per James in irc:
| it's the machine that the archive actually lives on
| what is happening is that LP is calling apt-ftparchive in such a way that it adds Task to all the packages as appropriate
| it does that using override files
| these are not generated by LP as it works
| the files list "package-name Task foo" stuff
| so we need those updated based on an updated germinate run
| however, I have no idea how to do that
| the files are owned by lp_publish, but that user doesn't have a cron job to do it or anything
| so, I don't know if it is done manually on occasion, or LP handles it out of the path of publishing