[Bug 1084106] Re: highbank installer broken

Fri Dec 14 10:26:18 UTC 2012

The SRU for this is currently blocked by the verification of bug 1079185
and I'll describe the situation with that verification in that bug.

I feel it is appropriate to bump this bug to Critical for Quantal to
reflect the urgency of this SRU.

Justification: this bug is currently rendering all ARM server installers
completely unusable in Quantal, and this is a severe post-release
regression. Both "Renders the system temporarily or permanently
unusable" and "Severely affects applications beyond the package
responsible for the root cause" apply here.

The only workaround is to manually mess inside the installer during
installation, which is both unacceptable for such an essential default
case and renders MAAS unusable.

Therefore, although I will still seek to resolve the blocking
verification for bug 1079185, I propose that if this doesn't happen very
soon then we revert that fix in -proposed so that only this bug is
fixed, so that this can then meet SRU criteria for promotion to -updates
(since I can verify this bug is fixed easily) and get this bug resolved
in Quantal ASAP.

** Changed in: flash-kernel (Ubuntu Quantal)
   Importance: High => Critical

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

Title:
  ARM server netboot installers broken

Status in The Eilt project:
  Triaged
Status in “flash-kernel” package in Ubuntu:
  Fix Released
Status in “flash-kernel” source package in Quantal:
  Fix Committed
Status in “flash-kernel” source package in Raring:
  Fix Released

Bug description:
  [Impact]

  It is possible to install neither highbank nor armadaxp on Quantal.
  This is a regression in Quantal, since this worked at release.

  [Test Case]

  Run the installer using the instructions at
  https://wiki.ubuntu.com/ARM/Server/Install, except use 12.10 images
  instead of 12.04.

  If successful, the installation should succeed. If this bug still
  exists, then the installer will fail with the following in
  /var/log/syslog:

  Dec 10 16:46:03 in-target: Setting up u-boot-tools (2012.04.01-2) ...
  Dec 10 16:46:04 in-target: update-initramfs: Generating /boot/initrd.img-3.5.0-17-highbank
  Dec 10 16:46:04 in-target: grep: /boot/config-3.5.0-17-highbank
  Dec 10 16:46:04 in-target: : No such file or directory
  Dec 10 16:46:04 in-target: WARNING: missing /lib/modules/3.5.0-17-highbank
  Dec 10 16:46:04 in-target: Device driver support needs thus be built-in linux image!
  Dec 10 16:46:04 in-target: WARNING: Couldn't open directory /lib/modules/3.5.0-17-highbank: No such file or directory
  Dec 10 16:46:04 in-target: FATAL: Could not open /lib/modules/3.5.0-17-highbank/modules.dep.temp for writing: No such file or directory
  Dec 10 16:46:04 in-target: FATAL: Could not load /lib/modules/3.5.0-17-highbank/modules.dep: No such file or directory
  Dec 10 16:46:04 in-target: FATAL: Could not load /lib/modules/3.5.0-17-highbank/modules.dep: No such file or directory
  Dec 10 16:46:05 in-target: FATAL: Could not load /lib/modules/3.5.0-17-highbank/modules.dep: No such file or directory
  Dec 10 16:46:06 in-target: FATAL: Could not load /lib/modules/3.5.0-17-highbank/modules.dep: No such file or directory
  Dec 10 16:46:08 in-target: Can't find /boot/vmlinuz-3.5.0-19-highbank or /boot/initrd.img-3.5.0-19-highbank
  Dec 10 16:46:09 flash-kernel-installer: error: flash-kernel failed
  Dec 10 16:46:09 main-menu[329]: WARNING **: Configuring 'flash-kernel-installer' failed with error code 1
  Dec 10 16:46:09 main-menu[329]: WARNING **: Menu item 'flash-kernel-installer' failed.

  [Regression Potential]

  This change affects flash-kernel-installer only, so can only affect
  d-i. d-i is completely broken for both highbank and armadaxp, so I
  don't see how it could get worse for these machines. For other
  machines, a regression would manifest itself as an installer failure
  only. We have verified that the new linux-version call works as
  expected in Quantal using network-console, so think that this is
  unlikely.

  Original description:

  It appears the installer for highbank is broken because 3.5.0-17 kernel
  is running and 3.5.0-18 is the current kernel version which is installed:

  Nov 13 16:14:43 in-target: Unpacking u-boot-tools (from .../u-boot-tools_2012.04.01-2_armhf.deb) ...
  Nov 13 16:14:44 in-target: Processing triggers for man-db ...
  Nov 13 16:14:46 in-target: Setting up u-boot-tools (2012.04.01-2) ...
  Nov 13 16:14:48 in-target: update-initramfs: Generating /boot/initrd.img-3.5.0-17-highbank
  Nov 13 16:14:48 in-target: grep: /boot/config-3.5.0-17-highbank
  Nov 13 16:14:48 in-target: : No such file or directory
  Nov 13 16:14:48 in-target: WARNING: missing /lib/modules/3.5.0-17-highbank
  Nov 13 16:14:48 in-target: Device driver support needs thus be built-in linux image!
  Nov 13 16:14:48 in-target: WARNING: Couldn't open directory /lib/modules/3.5.0-17-highbank: No such file or directory
  Nov 13 16:14:48 in-target: FATAL: Could not open /lib/modules/3.5.0-17-highbank/modules.dep.temp for writing: No such file or directory
  Nov 13 16:14:48 in-target: FATAL: Could not load /lib/modules/3.5.0-17-highbank/modules.dep: No such file or directory
  Nov 13 16:14:48 in-target: FATAL: Could not load /lib/modules/3.5.0-17-highbank/modules.dep: No such file or directory
  Nov 13 16:14:49 in-target: FATAL: Could not load /lib/modules/3.5.0-17-highbank/modules.dep: No such file or directory
  Nov 13 16:14:51 in-target: FATAL: Could not load /lib/modules/3.5.0-17-highbank/modules.dep: No such file or directory
  Nov 13 16:14:53 in-target: Can't find /boot/vmlinuz-3.5.0-18-highbank or /boot/initrd.img-3.5.0-18-highbank
  Nov 13 16:14:53 flash-kernel-installer: error: flash-kernel failed
  Nov 13 16:14:53 main-menu[328]: WARNING **: Configuring 'flash-kernel-installer' failed with error code 1
  Nov 13 16:14:53 main-menu[328]: WARNING **: Menu item 'flash-kernel-installer' failed.
  Nov 13 16:14:53 main-menu[328]: INFO: Modifying debconf priority limit from 'critical' to 'high'

To manage notifications about this bug go to:
https://bugs.launchpad.net/eilt/+bug/1084106/+subscriptions