[Bug 1081721] Re: quantal to raring upgrade: do-release-upgrade fails to install the new kernel

Paul Larson paul.larson at canonical.com
Mon Jan 7 14:12:04 UTC 2013


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.

** Changed in: update-manager (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1081721

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

Status in “update-manager” package in Ubuntu:
  Invalid

Bug description:
  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:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1081721/+subscriptions




More information about the foundations-bugs mailing list