[Bug 1926748] Re: regression in xenial updates - grub2 cannot handle new arm64 relocations

[Joshua Powers]

# Bionic Verification

## Test Steps

Booted AWS arm64 baremetal and VM systems
Ran the following script: https://paste.ubuntu.com/p/B5XPR8StXy/
Ensure system successfully reboots

## Results

t4g.medium: https://paste.ubuntu.com/p/QH8Xrr4Sck/
c6g.metal: https://paste.ubuntu.com/p/4q688QqC4v/

Both systems successfully updated grub from proposed and rebooted.

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

Title:
  regression in xenial updates - grub2 cannot handle new arm64
  relocations

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Invalid
Status in grub2-unsigned package in Ubuntu:
  Invalid
Status in grub2 source package in Trusty:
  New
Status in grub2-signed source package in Trusty:
  New
Status in grub2-unsigned source package in Trusty:
  New
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Committed
Status in grub2-unsigned source package in Xenial:
  Fix Committed
Status in grub2-signed source package in Bionic:
  Fix Committed
Status in grub2-unsigned source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * regression in xenial updates - grub2 cannot handle new relocations

   * grub-efi-arm64-bin gained new recommends on -signed package which
  is attempted to be installed

   * it pulls in one grub which was built with a newer toolchain and has
  more relocations

   * non-secureboot grub-install in xenial fails to install it when
  creating core.efi, because it does not know how to handle new
  relocations.

   * We need to cherrypick patches from 2.02 (which are in bionic+) to
  xenial & trusty.

  [Test Plan]

   * install new grub2-common grub-common

   * install grub-efi-arm64-signed from xenial-updates

   * package installation should be successful

   * this is executed as part of autopkgtest upgrades when testing any
  package on xenial in our autopkgtest cloud

  [Where problems could occur]

   * we are rebuilding grub2 which will have to go into security pocket
  eventually. Thus it's best to rebuild grub2 in security pocket.

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