[Bug 2011925] Re: flash-kernel 3.106ubuntu13 causes a trigger cycle when installing arm64 kernels on VMs

[Dave Jones]

Thanks for the logs -- the latter is most interesting in that it
indicates the eventual cycle *isn't* the first cycle error that occurs.
One occurs earlier on flash-kernel's second execution, when the kernel
is reported as being in "triggers-pending" state (presumably because its
initrd hasn't been generated yet).

Because dpkg decides (for some reason I don't understand yet) that f-k
has triggered a cycle *there*, it places the kernel in half-configured
state (because the triggers it's awaiting have failed), and that
explains the later cycle that gets triggered.

So, the question becomes: why is dpkg deciding that f-k has triggered a
cycle that early when it doesn't in the Xilinx and Pi cases... Is there
something different about this kernel to others? In particular, with
regard to its initrd and corresponding initramfs-tools trigger?

In the meantime, I'll have a dig into the dpkg cycle detection and try
and figure out why that first cycle is detected when it doesn't in the
Xilinx and Pi cases.

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

Title:
  flash-kernel 3.106ubuntu13 causes a trigger cycle when installing
  arm64 kernels on VMs

Status in flash-kernel package in Ubuntu:
  New

Bug description:
  We're seeing the following error when trying to install kernel
  packages on cloud instances with the latest flash-kernel,
  3.106ubuntu13.

  sudo apt-get install --yes linux-generic
  ...
  : /boot/vmlinuz is now a symlink to vmlinuz-6.1.0-16-generic
  I: /boot/initrd.img is now a symlink to initrd.img-6.1.0-16-generic
  Setting up linux-headers-generic (6.1.0.16.16) ...
  Setting up linux-image-generic (6.1.0.16.16) ...
  Setting up linux-generic (6.1.0.16.16) ...
  Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for flash-kernel (3.106ubuntu13) ...
  flash-kernel: requested kernel 6.1.0-16-generic is in state triggers-pending.
  flash-kernel: deferring update (trigger activated)
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    flash-kernel -> linux-image-6.1.0-16-generic
   packages' pending triggers which are or may be unresolvable:
    linux-image-6.1.0-16-generic: linux-update-6.1.0-16-generic
    flash-kernel: flash-kernel
  dpkg: error processing package linux-image-6.1.0-16-generic (--configure):
   triggers looping, abandoned
  Processing triggers for flash-kernel (3.106ubuntu13) ...
  flash-kernel: requested kernel 6.1.0-16-generic is in state half-configured.
  flash-kernel: deferring update (trigger activated)
  Processing triggers for flash-kernel (3.106ubuntu13) ...
  flash-kernel: requested kernel 6.1.0-16-generic is in state half-configured.
  flash-kernel: deferring update (trigger activated)
  Processing triggers for flash-kernel (3.106ubuntu13) ...
  flash-kernel: requested kernel 6.1.0-16-generic is in state half-configured.
  flash-kernel: deferring update (trigger activated)
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    flash-kernel -> flash-kernel -> flash-kernel -> flash-kernel
   packages' pending triggers which are or may be unresolvable:
    flash-kernel: flash-kernel
  dpkg: error processing package flash-kernel (--configure):
   triggers looping, abandoned
  Errors were encountered while processing:
   linux-image-6.1.0-16-generic
   flash-kernel
  needrestart is being skipped since dpkg has failed
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  I was able to reproduce this on an aws image with serial 20230306, but
  not on one with serial 20230303 (which was using flash-kernel
  3.106ubuntu12. I also see this on the latest google cloud images.

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