[Bug 1586894] Re: Xenial upgrade installs i386 kernel despite amd64 userland

Brian Murray brian at ubuntu.com
Mon Jul 25 21:09:07 UTC 2016


In VarLogDistUpgradeMainlog.txt we can see the following:

2016-05-29 11:36:01,240 INFO installing linux metapackage: linux-generic:i386
2016-05-29 11:36:01,241 DEBUG Installing 'linux-generic:i386' (linux metapackage may have been accidentally uninstalled)

The function "_get_linux_metapackage" from DistUpgradeQuirks.py doesn't
seem to do any architecture checking.

That being said you seem to have had the amd64 and i386 kernel packages
installed before the upgrade.  From the Foreign section of
VarLogDistupgradeMainlog.txt:

linux-image-4.0.5-040005-generic linux-image-4.4.10-040410-generic:i386

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

Title:
  Xenial upgrade installs i386 kernel despite amd64 userland

Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  I had a Trusty 14.04 LTS system and used update-manager -d to trigger
  the release upgrade to Xenial.  Everything went fine, but when I
  rebooted into the kernel 4.4.0-22-generic I was greeted with a
  stacktrace and an error about not being able to execute /sbin/init on
  the initrd.

  I booted into the old kernel and extracted and compared the initrd's
  and everything important was the same.  I then booted with
  boot_delay=250 and after a long wait was able to see "request_module:
  runaway loop modprobe binfmt-464c" messages indicating wrong binary
  format.  Then I looked at the kernel config and noticed that
  CONFIG_X86_64 was not defined on the upgrade kernel; afterwards, I saw
  that linux-image-generic:i386 and friends were installed.

  After replacing linux-image-generic:i386 and friends with the amd64
  variants, all was fine.

  Please ensure that if linux-image-generic is installed or replaced,
  its arch matches the arch of /sbin/init or systemd perhaps?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sun May 29 21:22:01 2016
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
         Users in the 'systemd-journal' group can see all messages. Pass -q to
         turn off this notice.
   No journal files were opened due to insufficient permissions.
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to xenial on 2016-05-30 (0 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeApttermlog: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt-term.log'
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1586894/+subscriptions



More information about the foundations-bugs mailing list