= groovy verification =
ubuntu@ubuntu:~$ cat /proc/version
Linux version 5.8.0-30-generic (buildd@lgw01-amd64-009) (gcc (Ubuntu
10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #32-Ubuntu
SMP Mon Nov 9 21:03:15 UTC 2020
ubuntu@ubuntu:~$ ls /sys/firmware/efi/efivars | grep FOO
FOO!BAR-8ed72b3f-ad26-4d5c-aa36-38689635cac3
** Description changed:
[Impact]
MAAS installs fail on systems that have EFI Variables that include a "/" in
the name.
Split out of bug 1894217.
[Test Case]
Using an OVMF-based VM, create a boot variable with a "/" character. For
example:
- setvar FOO/BAR -guid 8ed72b3f-ad26-4d5c-aa36-38689635cac3 -rt -nv =foo
+ Shell> setvar FOO/BAR -guid 8ed72b3f-ad26-4d5c-aa36-38689635cac3 -rt -nv
+ =foo
Then, in Linux:
$ ls /sys/firmware/efi/efivars/
ls: reading directory '/sys/firmware/efi/efivars/': Input/output error
BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c
ConIn-8be4df61-93ca-11d2-aa0d-00e098032b8c
ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8c
ErrOut-8be4df61-93ca-11d2-aa0d-00e098032b8c
MTC-eb704011-1402-11d3-8e77-00a0c969723b
The Input/output error is the key symptom. See below to see how that
percolates up to MAAS install failures.
[Regression Risk]
There's a very tiny chance that someone has written code that depends on an
the -EIO error for some reason. It's hard to guess why such a script would do
that.
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Fix Committed
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899993
Title:
EFI: Fails when BootCurrent entry does not exist
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1899993/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
