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.)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-kernel-tests |
New
|
Undecided
|
Unassigned | ||
grub2-signed (Ubuntu) |
Invalid
|
Undecided
|
Julian Andres Klode | ||
Bionic |
Triaged
|
High
|
Julian Andres Klode | ||
linux-hwe-5.4 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bionic |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
The ADT tests for arm64 kernels in Bionic are failing during the setup phase with the following errors:
Setting up grub-efi-
Installing for arm64-efi platform.
grub-install: error: efibootmgr: not found.
dpkg: error processing package grub-efi-
installed grub-efi-
Setting up libx11-6:arm64 (2:1.6.
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-
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:/
tags: | added: kernel-adt-failure |
description: | updated |
summary: |
- linux-hwe-5.4 ADT test failure with linux-hwe-5.4/5.4.0-128.144~18.04.1 + Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from + bionic-proposed fails to install/upgrade |
tags: | added: bionic regression-proposed |
no longer affects: | grub2-unsigned (Ubuntu) |
no longer affects: | grub2-unsigned (Ubuntu Bionic) |
tags: | added: foundations-todo |
Changed in grub2-signed (Ubuntu Bionic): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in grub2-signed (Ubuntu): | |
status: | New → Invalid |
Changed in grub2-signed (Ubuntu Bionic): | |
assignee: | nobody → Julian Andres Klode (juliank) |
Changed in grub2-signed (Ubuntu): | |
assignee: | nobody → Julian Andres Klode (juliank) |
Could this be the same issue as reported in bug 1936857?