quantal to raring upgrade: do-release-upgrade fails to install the new kernel

[Para Siva]

Quantal to raring upgrade fails to install new kernel and uses the old quantal kernel after the release upgrade.

Test_steps:
1. Install quantal desktop
2. Run sudo apt-get update && sudo apt-get -y dist-upgrade
3. Run sudo do-release-upgrade -d -m desktop -f DistUpgradeViewNonInteractive
4. Reboot after the upgrade and check for uname -r
5. It could be noticed that the kernel version is still the old quantal version

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: update-manager 1:0.174.3
ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6
Uname: Linux 3.7.0-3-generic x86_64
ApportVersion: 2.6.2-0ubuntu5
Aptdaemon:

Architecture: amd64
CurrentDmesg.txt:
 [ 14.764627] hda-intel: Invalid position buffer, using LPIB read method instead.
 [ 15.163723] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
Date: Wed Nov 21 17:56:37 2012
GsettingsChanges: b'com.ubuntu.update-manager' b'launch-time' b'1353516801'
InstallationDate: Installed on 2012-11-21 (0 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: update-manager
UpgradeStatus: Upgraded to raring on 2012-11-21 (0 days ago)
---
ApportVersion: 2.6.2-0ubuntu5
Aptdaemon:

Architecture: i386
CurrentDmesg.txt:
 [ 31.067495] init: plymouth-upstart-bridge main process (480) killed by TERM signal
 [ 47.172089] end_request: I/O error, dev fd0, sector 0
 [ 47.192076] end_request: I/O error, dev fd0, sector 0
 [ 52.616410] colord-sane[1681]: segfault at 0 ip b7335ddf sp bfd05bc0 error 4 in libc-2.16.so[b7283000+1a6000]
DistroRelease: Ubuntu 13.04
GsettingsChanges:

MarkForUpload: True
Package: update-manager 1:0.174.3
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Tags: raring
Uname: Linux 3.5.0-18-generic i686
UpgradeStatus: Upgraded to raring on 2012-11-19 (6 days ago)
UserGroups:

[Para Siva (psivaa)]

apport information

[Para Siva (psivaa)]

apport information

[Para Siva (psivaa)]

apport information

[Para Siva (psivaa)]

Any other logs can be found in
https://jenkins.qa.ubuntu.com/view/Raring/view/Smoke%20Testing/job/raring-upgrade-quantal-desktop/27/ARCH=i386,LTS=non-lts,PROFILE=desktop,label=upgrade-test/

Thanks

[Brian Murray (brian-murray)]

It certainly looks like update-grub ran succe8sfully:

Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.7.0-3-generic
Found initrd image: /boot/initrd.img-3.7.0-3-generic
Found linux image: /boot/vmlinuz-3.5.0-18-generic
Found initrd image: /boot/initrd.img-3.5.0-18-generic
Found memtest86+ image: /boot/memtest86+.bin
done

The dmesg from the first reboot after upgrade and /boot/grub/menu.lst would be helpful here.

[Paul Larson (pwlars)]

Have you tried reproducing it by hand? I see this happening in the automated runs, but when I tried it just a moment ago on a local vm, I see the kernel getting upgraded just fine.

[Para Siva (psivaa)]

This is constantly reproducible in upgrades on quantal VMs created using ubuntu-vm-builder. Please see attached the dmesg after the first reboot.

[Para Siva (psivaa)]

/boot/grub/menu.list of the VM is also attached.

[Colin Watson (cjwatson)]

Why on earth is menu.lst involved at all? That's GRUB Legacy, and we haven't used GRUB Legacy by default for years.

[Colin Watson (cjwatson)]

Perhaps ubuntu-vm-builder is falling back to some kind of ancient stupid mode? The source I have for it only seems to have definitions for series up to natty.

[Para Siva (psivaa)]

Well for quantal base images i had to add --addpkg linux-image-generic during base image creation. This is based on the information given in bug 1037607.

Just to make it clear the following is the command used to create the base image

sudo ubuntu-vm-builder kvm quantal --kernel-flavour generic main restricted --rootsize 5G --addpkg openssh-server --addpkg linux-image-generic --arch i386

[Para Siva (psivaa)]

dist-upgrade.tar.gz from the machine where the above two files (dmesg_after_first_boot and menu.list) is attached

[Paul Larson (pwlars)]

I was able to reproduce this bug finally, and can confirm that the kernel is getting installed, but not set up properly in grub. It seems that VMs built with ubuntu-vm-builder do not include grub2. The auto-upgrade-testing scripts seem to account for this by forcing an install of grub-pc, but I'm not sure if that's before or after the upgrade, and doesn't seem to automatically handle the conversion to grub2. I was able to take the image that was failing and work around this by first booting the image with kvm, installing grub-pc and running upgrade-from-grub-legacy

It *is* a bit curious that all of this worked using the same process for precise->quantal and previous upgrade tests, but not for quantal->raring.

[Paul Larson (pwlars)]

After fixing the broken grub installs in these images, they all seem to be working properly. You could, perhaps, put a bug in for this on the way vm-builder seems to install grub1 instead of grub2, but I'm not sure how much traction it will get. If we continue to use this set of tests for upgrade testing, then the way they create new base images needs to be adapted to use some other, currently supported method.