Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.)

[Kleber Sacilotto de Souza]

The ADT tests for arm64 kernels in Bionic are failing during the setup phase with the following errors:

Setting up grub-efi-arm64-signed (1.173.2~18.04.1+2.04-1ubuntu47.4) ...
Installing for arm64-efi platform.
grub-install: error: efibootmgr: not found.
dpkg: error processing package grub-efi-arm64-signed (--configure):
 installed grub-efi-arm64-signed package post-installation script subprocess returned error exit status 1
Setting up libx11-6:arm64 (2:1.6.4-3ubuntu0.5) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for libc-bin (2.27-3ubuntu1.6) ...
Errors were encountered while processing:
 grub-efi-arm64-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
blame:
badpkg: testbed setup commands failed with status 100
autopkgtest [15:12:03]: ERROR: erroneous package: testbed setup commands failed with status 100

ADT test log:
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/l/linux-hwe-5.4/20220930_151219_13ac3@/log.gz

[Kleber Sacilotto de Souza (kleber-souza)]

Could this be the same issue as reported in bug 1936857?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Francis Ginther (fginther)]

@juliank Hello, I see that you picked up https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1991676. I just want to mention so that you are aware, that this is blocking most, if not all, kernel ADT testing on bionic arm64.

[Julian Andres Klode (juliank)]

Well surely not more than the past year, this is not a new bug after all, the regression was introduced with the initial boothole update when we did the one grub split.

[Francis Ginther (fginther)]

@juliank, ah, I found another detail. This appears to only break when the package is updated in the ADT testbed. My assumption is if the latest package version is already in the base image, there is no package update and therefore no breakage. For example:

[1] older image, fails: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/d/dpdk/20221027_190645_aae03@/log.gz
[2] newer image, passes: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/d/dpdk/20221028_185258_2a00f@/log.gz

The second run occurred about a day later. I can't tell if this is using a new image, but when I inspected the artifacts from the run. I do see `grub-efi-arm64-bin 2.04-1ubuntu47.4`, which is the latest and the version that [1] tried to upgrade to.

So I guess we generally avoid this by refreshing the ADT base images.

[Andrei Gherzan (agherzan)]

I just bumped into this on a new linux-hwe-5.4 version:

Setting up grub-efi-arm64-signed (1.187.3~18.04.1+2.06-2ubuntu14.1) ...
Installing for arm64-efi platform.
grub-install: error: efibootmgr: not found.

ref.: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/l/lttng-modules/20230223_161020_a9d08@/log.gz

Do we have any progress on it?

[Brian Murray (brian-murray)]

This issue has been worked around in the autopkgtest environment with the following change:

https://code.launchpad.net/~ubuntu-release/autopkgtest/+git/development/+merge/437822