[Bug 1517582] Re: flash-kernel causes postinsts to fail when it happens to be installed on an unsupported system

[dann frazier]

We do support arm64 UEFI systems for server and for those, there's no
use case for flash-kernel to do anything. It does commonly get installed
though. Though flash-kernel-installer knows not to make d-i install it
on arm*/efi systems, it does tend to get installed via other mechanisms.
curtin image-based installs, for example, do include flash-kernel. When
f-k is there, it breaks kernel upgrades because the f-k kernel hooks
bail out.

As Newell mentioned, the bypass-on-EFI code change in Debian only skip
unknown devices. If a system does appear that has a kernel/initrd in
encrypted MTD or similar, we just need to add a db entry for it like any
other f-k supported device and this bypass path would not be taken.

I guess an alternate solution would be to make tools like curtin, our
factory image creation process, etc be smart enough to detect an efi
system and set the FLASH_KERNEL_SKIP variable - but I don't see why
that's any better than fixing it in one place.

Unless there's any further objections, I'd like to go ahead and
merge/upload w/ Newell's patch from Debian.

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

Title:
  flash-kernel causes postinsts to fail when it happens to be installed
  on an unsupported system

Status in flash-kernel package in Ubuntu:
  Fix Released

Bug description:
  For xgene-2 soc on EFI system, flash-kernel is failing:

  Unsupported platform.
  run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1
  dpkg: error processing package initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for ureadahead (0.100.0-16) ...
  Processing triggers for ufw (0.34~rc-0ubuntu2) ...
  Errors were encountered while processing:
   initramfs-tools

  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu

  This error surfaced during the deployment of a Wily MAAS arm64 daily
  cloud image.  http://cloud-images.ubuntu.com/daily

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  I mounted the root-image that MAAS and overlayroot use as the
  OverlayFS.  I located the changlog for flash-kernel and found the
  package information below:

  flash-kernel (3.0~rc.4ubuntu55) wily

  3) What you expected to happen

  I expected that postinsts would not fail.

  4) What happened instead

  postinsts failed.

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