Karmic server upgrade loses kernel metapackages

Bug #441629 reported by Scott Kitterman
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Fix Released
High
Unassigned
Karmic
Fix Released
High
Unassigned

Bug Description

Binary package hint: update-manager

I just upgraded my test server to karmic and both linux and linux-image were removed by update-manager. I would gather this is related to the move from a -server to a -generic kernel. Users that don't notice these metapackages have been removed won't get abi bump kernel updates which could have security implications post release.

Changed in update-manager (Ubuntu):
importance: Undecided → High
milestone: none → karmic-updates
milestone: karmic-updates → ubuntu-9.10
Revision history for this message
to be removed (liw) wrote :

Suggestion: have a "quirk" in the update-manager code that checks whether linux and linux-image were installed before the upgrade, and if so, either refuses to remove them or installs them back.

However, should the dependencies of linux and linux-image be such that they pull in the -generic kernels and don't get removed?

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

Could you please attach the output of /var/log/dist-upgrade/main.log ?

Changed in update-manager (Ubuntu Karmic):
status: New → Incomplete
Revision history for this message
Michael Vogt (mvo) wrote :

This should be fixed now, the code that does the kernel selection is more careful now.

Changed in update-manager (Ubuntu Karmic):
status: Incomplete → Fix Committed
Revision history for this message
Scott Kitterman (kitterman) wrote :
Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for the log.

From reading it, it did remove linux-server and added linux-generic. That looks correct. The log does not contain "linux" or "linux-image". I still reworked the code a bit to work better, but in this particular case i'm not sure what it should have done differently (unless there is something happening to linux/linux-image at a different point that is not covered by the logs).

Revision history for this message
Scott Kitterman (kitterman) wrote : Re: [Bug 441629] Re: Karmic server upgrade loses kernel metapackages

I had the kernel metapackages before the upgrade. I'll poke around in the
other logs and see what I can find.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package update-manager - 1:0.126

---------------
update-manager (1:0.126) karmic; urgency=low

  * DistUpgrade/DistUpgrade.cfg:
    - add gnome-app-install to the ForcedObsoletes
  * DistUpgrade/DistUpgrade.cfg.hardy:
    - add ability to upgrade from hardy to karmic (as asked for
      by Jonathan Riddell)
  * DistUpgrade/DistUpgradeQuirks.py:
    - add quirk handler to mark the dependencies of
      language-support-translations-* as manual on upgrade

      The language-support-translations- packages are removed in
      karmic and would otherwise be marked as auto-removable.
      (LP: #439296)
    - convert PASS value from 1 to 0 for ntfs entries in
      /etc/fstab (LP: #441242) and add tests for it
    - put 386 to generic transition code here and decouple from
      the kernel selection
    - inhibit gnome-screensaver once the upgrade started
      to avoid X crash (LP: #439594)
  * DistUpgrade/DistUpgradeCache.py:
    - workaround issues with kdesu when it drop the permission bits
      in a tmpdir (thanks to Jonathan Riddell)
    - fix base-installer kernel selection (LP: #441629)
    - fix log dir does not exist, create it (LP: #441959)
  * UpdateManager/backend/InstallBackendAptdaemon.py:
    - give up lock before running aptdaemon (LP: #445920)
  * po/
    - updated from launchpad (required as during a release upgrade
      we can't use langpacks)

 -- Michael Vogt <email address hidden> Thu, 08 Oct 2009 17:45:25 +0200

Changed in update-manager (Ubuntu Karmic):
status: Fix Committed → Fix Released
Revision history for this message
Scott Kitterman (kitterman) wrote :

grep server apt-term.log produces:

Found kernel: /boot/vmlinuz-2.6.28-15-server
Found kernel: /boot/vmlinuz-2.6.28-14-server
Removing linux-restricted-modules-2.6.28-11-server ...
update-initramfs: Generating /boot/initrd.img-2.6.28-11-server
Removing linux-image-2.6.28-11-server ...
Found kernel: /boot/vmlinuz-2.6.28-15-server
Found kernel: /boot/vmlinuz-2.6.28-14-server
Removing linux-restricted-modules-2.6.28-13-server ...
update-initramfs: Generating /boot/initrd.img-2.6.28-13-server
Removing linux-image-2.6.28-13-server ...
Found kernel: /boot/vmlinuz-2.6.28-15-server
Found kernel: /boot/vmlinuz-2.6.28-14-server
Removing linux-restricted-modules-2.6.28-14-server ...
update-initramfs: Generating /boot/initrd.img-2.6.28-14-server
Removing linux-image-2.6.28-14-server ...
Found kernel: /boot/vmlinuz-2.6.28-15-server
Found kernel: /boot/vmlinuz-2.6.27-11-server
Removing linux-server ...
Removing linux-image-server ...
Removing linux-restricted-modules-server ...
Removing linux-restricted-modules-2.6.28-15-server ...
update-initramfs: Generating /boot/initrd.img-2.6.28-15-server

So it the metapackage was definitely there and removed.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.