| 2020-08-14 22:15:49 |
dann frazier |
bug |
|
|
added bug |
| 2020-08-14 22:16:02 |
dann frazier |
nominated for series |
|
Ubuntu Groovy |
|
| 2020-08-14 22:16:02 |
dann frazier |
bug task added |
|
efivar (Ubuntu Groovy) |
|
| 2020-08-14 22:16:02 |
dann frazier |
nominated for series |
|
Ubuntu Focal |
|
| 2020-08-14 22:16:02 |
dann frazier |
bug task added |
|
efivar (Ubuntu Focal) |
|
| 2020-08-15 19:54:08 |
dann frazier |
bug watch added |
|
https://github.com/rhboot/efivar/issues/157 |
|
| 2020-08-15 19:54:08 |
dann frazier |
bug task added |
|
efivar |
|
| 2020-08-15 23:45:01 |
Bug Watch Updater |
efivar: status |
Unknown |
New |
|
| 2020-08-17 15:12:41 |
Andrew Cloke |
bug |
|
|
added subscriber Andrew Cloke |
| 2020-09-03 15:53:41 |
Dan Streetman |
bug |
|
|
added subscriber Dan Streetman |
| 2020-09-28 15:41:07 |
Jeff Lane |
tags |
|
blocks-hwcert-server |
|
| 2020-09-29 16:51:57 |
dann frazier |
efivar (Ubuntu Groovy): status |
New |
In Progress |
|
| 2020-09-29 16:52:16 |
dann frazier |
efivar (Ubuntu Groovy): assignee |
|
dann frazier (dannf) |
|
| 2020-10-05 09:51:56 |
Launchpad Janitor |
efivar (Ubuntu Groovy): status |
In Progress |
Fix Released |
|
| 2020-10-08 14:21:30 |
dann frazier |
efivar (Ubuntu Focal): assignee |
|
dann frazier (dannf) |
|
| 2020-10-08 14:21:34 |
dann frazier |
efivar (Ubuntu Focal): status |
New |
In Progress |
|
| 2020-10-09 21:28:42 |
dann frazier |
description |
After upgrading a system from bionic to focal, grub-install began to fail:
$ sudo /usr/sbin/grub-install
Installing for x86_64-efi platform.
/usr/sbin/grub-install: warning: Internal error.
/usr/sbin/grub-install: error: failed to register the EFI boot entry: Operation not permitted.
The issue seems to stem from libefiboot1. With upstream release 35:
# LD_PRELOAD=/home/ubuntu/efivar/src/libefiboot.so /bin/efibootmgr -q -c -d /dev/nvme0n1 -p 1 -w -L grub -l \\EFI\\grub\\grubx64.efi -v
#
But with 36:
# LD_PRELOAD=/home/ubuntu/efivar/src/libefiboot.so /bin/efibootmgr -q -c -d /dev/nvme0n1 -p 1 -w -L grub -l \\EFI\\grub\\grubx64.efi -vCould not prepare Boot variable: No such file or directory
git bisect of upstream efivars hit the following commit:
# first bad commit: [ff696a432bf92af1206e235a60ad28b58ff0ab92] Move nvme parsing to linux-nvme.c |
[Impact]
Grub fails to install on systems with nvme-subsys storage when installing focal, or upgrading from bionic to focal. As symptom of the latter is shown below:
┌───────────────────────┤ Configuring shim-signed ├────────────────────────┐
│ │
│ GRUB failed to install to the following devices: │
│ │
│ /dev/nvme0n1p1 │
│ │
│ Do you want to continue anyway? If you do, your computer may not start │
│ up properly. │
│ │
│ Writing GRUB to boot device failed - continue? │
│ │
│ <Yes> <No>
[Test Case]
On a system with an EFI System Partition residing on an nvme-subsys block device, run grub-install:
$ sudo /usr/sbin/grub-install
Installing for x86_64-efi platform.
/usr/sbin/grub-install: warning: Internal error.
/usr/sbin/grub-install: error: failed to register the EFI boot entry: Operation not permitted.
Also, regression test on a system with a non-nvme-subsys NVMe device.
[Regression Potential]
There's a risk that a parsing bug will introduce a regression to other systems - most like systems with NVMe block devices. |
|
| 2020-10-09 21:31:02 |
dann frazier |
description |
[Impact]
Grub fails to install on systems with nvme-subsys storage when installing focal, or upgrading from bionic to focal. As symptom of the latter is shown below:
┌───────────────────────┤ Configuring shim-signed ├────────────────────────┐
│ │
│ GRUB failed to install to the following devices: │
│ │
│ /dev/nvme0n1p1 │
│ │
│ Do you want to continue anyway? If you do, your computer may not start │
│ up properly. │
│ │
│ Writing GRUB to boot device failed - continue? │
│ │
│ <Yes> <No>
[Test Case]
On a system with an EFI System Partition residing on an nvme-subsys block device, run grub-install:
$ sudo /usr/sbin/grub-install
Installing for x86_64-efi platform.
/usr/sbin/grub-install: warning: Internal error.
/usr/sbin/grub-install: error: failed to register the EFI boot entry: Operation not permitted.
Also, regression test on a system with a non-nvme-subsys NVMe device.
[Regression Potential]
There's a risk that a parsing bug will introduce a regression to other systems - most like systems with NVMe block devices. |
[Impact]
Grub fails to install on systems with nvme-subsys storage when installing focal, or upgrading from bionic to focal. As symptom of the latter is shown below:
┌───────────────────────┤ Configuring shim-signed ├────────────────────────┐
│ │
│ GRUB failed to install to the following devices: │
│ │
│ /dev/nvme0n1p1 │
│ │
│ Do you want to continue anyway? If you do, your computer may not start │
│ up properly. │
│ │
│ Writing GRUB to boot device failed - continue? │
│ │
│ <Yes> <No>
[Test Case]
On a system with an EFI System Partition residing on an nvme-subsys block device, run grub-install:
$ sudo /usr/sbin/grub-install
Installing for x86_64-efi platform.
/usr/sbin/grub-install: warning: Internal error.
/usr/sbin/grub-install: error: failed to register the EFI boot entry: Operation not permitted.
Also, regression test on a system with a non-nvme-subsys NVMe device.
[Regression Potential]
There's a risk that a parsing bug will introduce a regression to other systems - most like systems with NVMe block devices.
This fix has been in groovy since just after beta (minus an innocuous debug statement that upstream requested during review), and the same patches apply cleanly to focal, which should help mitigate the risk by way of some real world exposure. |
|
| 2020-10-09 21:40:32 |
dann frazier |
description |
[Impact]
Grub fails to install on systems with nvme-subsys storage when installing focal, or upgrading from bionic to focal. As symptom of the latter is shown below:
┌───────────────────────┤ Configuring shim-signed ├────────────────────────┐
│ │
│ GRUB failed to install to the following devices: │
│ │
│ /dev/nvme0n1p1 │
│ │
│ Do you want to continue anyway? If you do, your computer may not start │
│ up properly. │
│ │
│ Writing GRUB to boot device failed - continue? │
│ │
│ <Yes> <No>
[Test Case]
On a system with an EFI System Partition residing on an nvme-subsys block device, run grub-install:
$ sudo /usr/sbin/grub-install
Installing for x86_64-efi platform.
/usr/sbin/grub-install: warning: Internal error.
/usr/sbin/grub-install: error: failed to register the EFI boot entry: Operation not permitted.
Also, regression test on a system with a non-nvme-subsys NVMe device.
[Regression Potential]
There's a risk that a parsing bug will introduce a regression to other systems - most like systems with NVMe block devices.
This fix has been in groovy since just after beta (minus an innocuous debug statement that upstream requested during review), and the same patches apply cleanly to focal, which should help mitigate the risk by way of some real world exposure. |
[Impact]
Grub fails to install on systems with nvme-subsys storage when installing focal, or upgrading from bionic to focal. As symptom of the latter is shown below:
┌───────────────────────┤ Configuring shim-signed ├────────────────────────┐
│ │
│ GRUB failed to install to the following devices: │
│ │
│ /dev/nvme0n1p1 │
│ │
│ Do you want to continue anyway? If you do, your computer may not start │
│ up properly. │
│ │
│ Writing GRUB to boot device failed - continue? │
│ │
│ <Yes> <No>
[Test Case]
On a system with an EFI System Partition residing on an nvme-subsys block device, run grub-install:
$ sudo /usr/sbin/grub-install
Installing for x86_64-efi platform.
/usr/sbin/grub-install: warning: Internal error.
/usr/sbin/grub-install: error: failed to register the EFI boot entry: Operation not permitted.
Also, regression test on a system with a non-nvme-subsys NVMe device.
[Regression Potential]
There's a risk that a parsing bug will introduce a regression to other systems - most at risk are systems with NVMe block devices.
This fix has been in groovy since just after beta (minus an innocuous debug statement that upstream requested during review), and the same patches apply cleanly to focal, which should help mitigate the risk by way of some real world exposure. |
|
| 2020-10-09 21:43:02 |
dann frazier |
description |
[Impact]
Grub fails to install on systems with nvme-subsys storage when installing focal, or upgrading from bionic to focal. As symptom of the latter is shown below:
┌───────────────────────┤ Configuring shim-signed ├────────────────────────┐
│ │
│ GRUB failed to install to the following devices: │
│ │
│ /dev/nvme0n1p1 │
│ │
│ Do you want to continue anyway? If you do, your computer may not start │
│ up properly. │
│ │
│ Writing GRUB to boot device failed - continue? │
│ │
│ <Yes> <No>
[Test Case]
On a system with an EFI System Partition residing on an nvme-subsys block device, run grub-install:
$ sudo /usr/sbin/grub-install
Installing for x86_64-efi platform.
/usr/sbin/grub-install: warning: Internal error.
/usr/sbin/grub-install: error: failed to register the EFI boot entry: Operation not permitted.
Also, regression test on a system with a non-nvme-subsys NVMe device.
[Regression Potential]
There's a risk that a parsing bug will introduce a regression to other systems - most at risk are systems with NVMe block devices.
This fix has been in groovy since just after beta (minus an innocuous debug statement that upstream requested during review), and the same patches apply cleanly to focal, which should help mitigate the risk by way of some real world exposure. |
[Impact]
Grub fails to install on systems with nvme-subsys storage when installing focal, or upgrading from bionic to focal. As symptom of the latter is shown below:
┌───────────────────────┤ Configuring shim-signed ├────────────────────────┐
│ │
│ GRUB failed to install to the following devices: │
│ │
│ /dev/nvme0n1p1 │
│ │
│ Do you want to continue anyway? If you do, your computer may not start │
│ up properly. │
│ │
│ Writing GRUB to boot device failed - continue? │
│ │
│ <Yes> <No>
[Test Case]
On a system with an EFI System Partition residing on an nvme-subsys block device, run grub-install:
$ sudo /usr/sbin/grub-install
Installing for x86_64-efi platform.
/usr/sbin/grub-install: warning: Internal error.
/usr/sbin/grub-install: error: failed to register the EFI boot entry: Operation not permitted.
Also, regression test on a system with a non-nvme-subsys NVMe device.
[Regression Potential]
There's a risk that a parsing bug will introduce a regression to other systems - most at risk are systems with NVMe block devices. Supposedly nvme-fabrics systems were not previously supported and, as a side-effect of this backport, will now be. However, it's possible - like was the case with bionic/nvme-subsys - that nvme-fabrics *used* to happen to work, and now will work differently or even break. Ideally we'd be able to test on such a system, but I don't know where to find that hardware.
This fix has been in groovy since just after beta (minus an innocuous debug statement that upstream requested during review), and the same patches apply cleanly to focal, which should help mitigate the risk by way of some real world exposure. |
|
| 2020-11-02 16:07:56 |
dann frazier |
description |
[Impact]
Grub fails to install on systems with nvme-subsys storage when installing focal, or upgrading from bionic to focal. As symptom of the latter is shown below:
┌───────────────────────┤ Configuring shim-signed ├────────────────────────┐
│ │
│ GRUB failed to install to the following devices: │
│ │
│ /dev/nvme0n1p1 │
│ │
│ Do you want to continue anyway? If you do, your computer may not start │
│ up properly. │
│ │
│ Writing GRUB to boot device failed - continue? │
│ │
│ <Yes> <No>
[Test Case]
On a system with an EFI System Partition residing on an nvme-subsys block device, run grub-install:
$ sudo /usr/sbin/grub-install
Installing for x86_64-efi platform.
/usr/sbin/grub-install: warning: Internal error.
/usr/sbin/grub-install: error: failed to register the EFI boot entry: Operation not permitted.
Also, regression test on a system with a non-nvme-subsys NVMe device.
[Regression Potential]
There's a risk that a parsing bug will introduce a regression to other systems - most at risk are systems with NVMe block devices. Supposedly nvme-fabrics systems were not previously supported and, as a side-effect of this backport, will now be. However, it's possible - like was the case with bionic/nvme-subsys - that nvme-fabrics *used* to happen to work, and now will work differently or even break. Ideally we'd be able to test on such a system, but I don't know where to find that hardware.
This fix has been in groovy since just after beta (minus an innocuous debug statement that upstream requested during review), and the same patches apply cleanly to focal, which should help mitigate the risk by way of some real world exposure. |
[Impact]
Grub fails to install on systems with nvme-subsys storage when installing focal, or upgrading from bionic to focal. As symptom of the latter is shown below:
┌───────────────────────┤ Configuring shim-signed ├────────────────────────┐
│ │
│ GRUB failed to install to the following devices: │
│ │
│ /dev/nvme0n1p1 │
│ │
│ Do you want to continue anyway? If you do, your computer may not start │
│ up properly. │
│ │
│ Writing GRUB to boot device failed - continue? │
│ │
│ <Yes> <No>
I've hit this on 2 systems so far - a high-end Nvidia server and an older ARM Server.
[Test Case]
On a system with an EFI System Partition residing on an nvme-subsys block device, run grub-install:
$ sudo /usr/sbin/grub-install
Installing for x86_64-efi platform.
/usr/sbin/grub-install: warning: Internal error.
/usr/sbin/grub-install: error: failed to register the EFI boot entry: Operation not permitted.
Also, regression test on a system with a non-nvme-subsys NVMe device.
[Regression Potential]
There's a risk that a parsing bug will introduce a regression to other systems - most at risk are systems with NVMe block devices. Supposedly nvme-fabrics systems were not previously supported and, as a side-effect of this backport, will now be. However, it's possible - like was the case with bionic/nvme-subsys - that nvme-fabrics *used* to happen to work, and now will work differently or even break. Ideally we'd be able to test on such a system, but I don't know where to find that hardware.
This fix has been in groovy since just after beta (minus an innocuous debug statement that upstream requested during review), and the same patches apply cleanly to focal, which should help mitigate the risk by way of some real world exposure. |
|
| 2020-11-03 21:46:48 |
Brian Murray |
efivar (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2020-11-03 21:46:50 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-11-03 21:46:52 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2020-11-03 21:46:56 |
Brian Murray |
tags |
blocks-hwcert-server |
blocks-hwcert-server verification-needed verification-needed-focal |
|
| 2020-11-03 23:16:55 |
dann frazier |
tags |
blocks-hwcert-server verification-needed verification-needed-focal |
blocks-hwcert-server verification-done verification-done-focal |
|
| 2020-11-12 11:18:04 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-11-12 11:28:08 |
Launchpad Janitor |
efivar (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2023-10-25 17:01:54 |
Bug Watch Updater |
efivar: status |
New |
Fix Released |
|
