[Bug 1928674] Re: grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

[Julian Andres Klode]

So xenial: I verified that maas-style netbooting that chainloads to
local grub still works.


On arm64 canonistack, both the version in -updates and the version in -proposed fail to boot.

After upgrade, the first boot gives us:

EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...

The second boot with updates gave us:

[2J[01;01H[=3h[2J[01;01H[2J[01;01H[=3h[2J[01;01H[2J[01;01H[=3h[2J[01;01H[0m[35m[40m[0m[37m[40merror: symbol `grub_file_filters' not found.
Entering rescue mode...
grub rescue> 

The second boot with proposed gave us:

[2J[01;01H[=3h[2J[01;01H[2J[01;01H[=3h[2J[01;01H[2J[01;01H[=3h[2J[01;01H[0m[35m[40m[0m[37m[40merror: relocation 0x113 is not implemented yet.
Entering rescue mode...
grub rescue> 

So there is some regression in terms of relocations due to the toolchain
change, but it did not boot before either, so I'm unsure if that's a
worthwhile regression to block the update.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1928674

Title:
  grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

Status in grub2 package in Ubuntu:
  In Progress
Status in grub2-signed package in Ubuntu:
  Invalid
Status in grub2-unsigned package in Ubuntu:
  Invalid
Status in grub2 source package in Trusty:
  Invalid
Status in grub2-signed source package in Trusty:
  New
Status in grub2-unsigned source package in Trusty:
  Triaged
Status in grub2 source package in Xenial:
  Invalid
Status in grub2-signed source package in Xenial:
  Fix Committed
Status in grub2-unsigned source package in Xenial:
  Fix Committed
Status in grub2 source package in Bionic:
  Invalid
Status in grub2-signed source package in Bionic:
  Fix Committed
Status in grub2-unsigned source package in Bionic:
  Fix Committed
Status in grub2 source package in Focal:
  Fix Committed
Status in grub2-signed source package in Focal:
  Fix Committed
Status in grub2-unsigned source package in Focal:
  Fix Committed
Status in grub2 source package in Groovy:
  Won't Fix
Status in grub2-signed source package in Groovy:
  Fix Committed
Status in grub2-unsigned source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

   * /etc/kernel/{postinst.d,postrm.d}/zz-update-grub missing on arm64
  with grub-efi-arm64 (a dependency of grub-efi-arm64-signed) installed

   * /etc/kernel/{postinst.d,postrm.d}/zz-update-grub missing on amd64
  with grub-efi-amd64 (an ORed dependency of grub-efi-amd64-signed)
  installed.

   * This results in newly installed kernels not getting added to
  grub.cfg and thus upon reboot one does not boot into the new kernel.

   * In later series these scripts moved to grub2-common, which is why
  they are absent in the backported grub-efi-* packages.  They should be
  restored to these packages in the backport.

  [Test Plan]
   * install grub packages from -updates
   * ensure that /etc/kernel/post{inst,rm}.d/zz-update-grub are absent; if necessary, remove them
   * Install new grubs
   * If testing on amd64 ensure that grub-efi-amd64 is installed, not grub-pc.
   * Install a new kernel that was not installed before
   * Observe that grub.cfg is regenerated and new kernel is present
   * Remove an old kernel
   * Observe that grub.cfg is regenerated and new kernel is removed from grub.cfg
   * From bionic, verify that a dist-upgrade to focal works without conflicts.

  [Where problems could occur]

   * These are conffiles. Although nobody should modify them, care
  should be taken when moving conffiles around.

  [Other Info]

   * First reported by klebers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1928674/+subscriptions