[Bug 1160360] [NEW] flash-kernel failed in an armhf lxc container on ARM: /usr/sbin/flash-kernel: 214: /usr/sbin/flash-kernel: mkimage: not found

Launchpad Bug Tracker 1160360 at bugs.launchpad.net
Thu Mar 28 13:53:29 UTC 2013


You have been subscribed to a public bug by Jean-Baptiste Lallement (jibel):

Raring armv7l
lxc: 0.9.0~rc1-0ubuntu1
flash-kernel: 3.0~rc.4ubuntu29
initramfs-tools: 0.103ubuntu0.7


When the kernel is upgraded inside an armhf LXC container running on armv7l, the upgrade fails with:
===
Setting up initramfs-tools (0.103ubuntu0.7) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.8.0-14-generic
flash-kernel: installing version 3.8.0-14-generic
Generating kernel u-boot image... /usr/sbin/flash-kernel: 214: /usr/sbin/flash-kernel: mkimage: not found
run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 127
dpkg: error processing initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
===

TEST CASE:
1. Install an armhf container on an arm host
2. Upgrade initramfs-tools

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: lxc 0.9.0~rc1-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
Uname: Linux 3.8.0-13-generic x86_64
ApportVersion: 2.9.2-0ubuntu4
Architecture: amd64
Date: Tue Mar 26 14:09:34 2013
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lxc
UpgradeStatus: Upgraded to raring on 2012-01-31 (419 days ago)

** Affects: flash-kernel (Ubuntu)
     Importance: High
         Status: Triaged


** Tags: amd64 apparmor apport-bug qa-daily-testing raring
-- 
flash-kernel failed in an armhf lxc container on ARM: /usr/sbin/flash-kernel: 214: /usr/sbin/flash-kernel: mkimage: not found
https://bugs.launchpad.net/bugs/1160360
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list