[Bug 1626848] Re: flash-kernel postrm.d script fails on kernel removal

[Loïc Minier]

The presence of a flash-kernel deb on a system is meant to imply that
kernel installations/removal/upgrades should update the bootloader
state. When using image building tools, flash-kernel's behavior needs to
be entirely disabled, much like daemons shouldn't be started in such a
chroot. To disable flash-kernel's behavior, set FLASH_KERNEL_SKIP=1 in
the environment.

Another approach used commonly by image building tools is to dpkg-divert
binaries (e.g. start-stop-daemon) to avoid services from being started;
a similar approach could be taken to disable flash-kernel.

-- 
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/1626848

Title:
  flash-kernel postrm.d script fails on kernel removal

Status in flash-kernel package in Ubuntu:
  New

Bug description:
  Context: livecd-rootfs build for ARM64 ubuntu images using the linux-
  generic kernel

  What changed: linux-image-generic-extra-* came into being and now
  linux-image-generic-* depends on it.  When removed the zz-flash-kernel
  hook for the kernel runs twice (postinst.d and postrm.d)

  What happened:
   - Creating a container image (LXD, ...) livecd-rootfs starts with a server image with a kernel and removes the kernel.
   - The kernel postinst.d hook for flash-kernel (zz-flash-kernel) runs twice now (first for postinst and then for postrm).  On the second call there is no kernel installed and flash-kernel does not handle being called with no kernel present; the kernel removal operation fails at this point.

  Looking for a solution where zz-flash-kernel/flash-kernel is tolerant
  of this behavior such that kernel removal is possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1626848/+subscriptions