ARM server netboot installers broken

Bug #1084106 reported by Rob Herring
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
flash-kernel (Ubuntu)
Fix Released
High
Oliver Grawert
Quantal
Fix Released
Critical
Adam Conrad
Raring
Fix Released
High
Oliver Grawert

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'

Robie Basak (racb)
information type: Proprietary → Public
Changed in eilt:
status: New → Triaged
Oliver Grawert (ogra)
Changed in flash-kernel (Ubuntu Raring):
status: New → Fix Committed
assignee: nobody → Oliver Grawert (ogra)
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package flash-kernel - 3.0~rc.4ubuntu29

---------------
flash-kernel (3.0~rc.4ubuntu29) raring; urgency=low

  * determine the latest installer kernel version in the target rootfs instead
    of assuming the version is the same as the running kernel (LP: #1084106)
  * drop the "|| true" from the initramfs building code, if we fail here we
    actually dont want to attempt to flash that
 -- Oliver Grawert <email address hidden> Tue, 04 Dec 2012 17:24:49 +0100

Changed in flash-kernel (Ubuntu Raring):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in flash-kernel (Ubuntu Quantal):
status: New → Confirmed
Robie Basak (racb)
description: updated
Adam Conrad (adconrad)
no longer affects: debian-installer (Ubuntu)
no longer affects: debian-installer (Ubuntu Quantal)
no longer affects: debian-installer (Ubuntu Raring)
Revision history for this message
Colin Watson (cjwatson) wrote : Please test proposed package

Hello Rob, or anyone else affected,

Accepted flash-kernel into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/flash-kernel/3.0~rc.4ubuntu27.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in flash-kernel (Ubuntu Quantal):
status: Confirmed → Fix Committed
tags: added: verification-needed
Adam Conrad (adconrad)
Changed in flash-kernel (Ubuntu Quantal):
assignee: nobody → Adam Conrad (adconrad)
importance: Undecided → High
Revision history for this message
Robie Basak (racb) wrote : Re: highbank installer broken

Verified fixed on both highbank and armadaxp, using apt-setup/proposed=true on the kernel command line.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Robie Basak (racb) wrote :

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
Robie Basak (racb)
summary: - highbank installer broken
+ ARM server netboot installers broken
Revision history for this message
Robie Basak (racb) wrote :

This is what I am proposing, but am not sure if it is the best answer. I'd appreciate feedback.

Revision history for this message
Robie Basak (racb) wrote :
Revision history for this message
Adam Conrad (adconrad) wrote : Update Released

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

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

This bug was fixed in the package flash-kernel - 3.0~rc.4ubuntu27.1

---------------
flash-kernel (3.0~rc.4ubuntu27.1) quantal; urgency=low

  * Ask blkid for UUID, fixes finding filesystems with labels (LP: #1079185)
  * Determine the latest installed kernel version from the target instead
    of assuming the version is the same as the running kernel (LP: #1084106)
 -- Adam Conrad <email address hidden> Mon, 10 Dec 2012 09:31:39 -0700

Changed in flash-kernel (Ubuntu Quantal):
status: Fix Committed → Fix Released
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.