[Impact]
If flash-kernel is installed in a chroot environment it will crash when trying to execute its postinst script. This will prevent the new design
of ubuntu-image from building any images that have flash-kernel seeded.
[Test Plan]
* Create a chroot on armhf or arm64
* sudo chroot <path_to_chroot> apt install -y flash-kernel linux-modules-extra-raspi
* Observe that flash-kernel fails due to a non-existent boot partition
* Enable -proposed in the chroot
* Attempt to install flash_kernel and linux-modules-extra-raspi again
* Observe that the packages now successfully install
[Regression Potential]
* If there are any valid existing workflows that attempt to run flash-kernel in a chroot, they could be affected by this change.
* However, there is an environment variable in place, FK_FORCE, that will enable these workflows to succeed again
* Testing should be done in some other valid non-chroot use cases to ensure no false positives in the chroot detection.
[Original Description]
Hey, following up on: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1947601?comments=all
Its not possible install linux-modules-extra-raspi in chroot, because it activates flash-kernel which fails.
I also tried to bypass flash-kernel by moving /sbin/flash-kernel aside before installing, but then the issue of docker failing does not get fixed.
This means that a number of distros I maintain can't have docker running correctly.
Related: https://github.com/guysoft/CustomPiOS/issues/149
Output:
12:36:15 I: /boot/initrd.img is now a symlink to initrd.img-5.13.0-1011-raspi
12:36:16 Setting up linux-modules-extra-5.13.0-1011-raspi (5.13.0-1011.13) ...
12:36:20 Setting up linux-modules-5.13.0-1011-raspi (5.13.0-1011.13) ...
12:36:25 Setting up linux-modules-extra-raspi (5.13.0.1011.17) ...
12:36:25 Processing triggers for linux-image-5.13.0-1011-raspi (5.13.0-1011.13) ...
12:36:25 /etc/kernel/postinst.d/initramfs-tools:
12:36:25 update-initramfs: Generating /boot/initrd.img-5.13.0-1011-raspi
12:36:45 cryptsetup: ERROR: Couldn't find sysfs directory for 7:0
12:36:47 Label writable not found in /dev/disk/by-label
12:36:48 Warning: root device LABEL=writable does not exist
12:37:07 W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays.
12:37:07 W: mdadm: failed to auto-generate temporary mdadm.conf file.
12:38:59 flash-kernel: deferring update (trigger activated)
12:38:59 /etc/kernel/postinst.d/zz-flash-kernel:
12:38:59 flash-kernel: deferring update (trigger activated)
12:38:59 Processing triggers for flash-kernel (3.104ubuntu5) ...
12:39:00 Unsupported platform 'BCM2835'.
12:39:00 dpkg: error processing package flash-kernel (--configure):
12:39:00 installed flash-kernel package post-installation script subprocess returned error exit status 1
12:39:00 Errors were encountered while processing:
12:39:00 flash-kernel
12:39:01 needrestart is being skipped since dpkg has failed
12:39:09 E: Sub-process /usr/bin/dpkg returned an error code (1)
12:39:09 ++++ echo_red 'build failed, unmounting image...'
Things I tried:
Patching as describe here: https://forums.raspberrypi.com/viewtopic.php?t=258056
Then moving before install /sbin/flash-kernel to /sbin/flash-kernel.bak
Results in the following output:
13:14:27
13:14:27 Pending kernel upgrade!
13:14:27
13:14:27 Running kernel version:
13:14:27 5.10.81-v8+
13:14:27
13:14:27 Diagnostics:
13:14:27 The currently running kernel version is not the expected kernel version 5.13.0-1011-raspi.
13:14:27
13:14:27 Restarting the system to load the new kernel will not be handled automatically, so you should consider rebooting. [Return]
13:14:27
13:14:27 Failed to check for processor microcode upgrades.
13:14:27
13:14:27 No services need to be restarted.
13:14:27
13:14:27 No containers need to be restarted.
13:14:27
13:14:27 No user sessions are running outdated binaries.
flash-kernel should detect when it's called in a chroot environment.