= focal verification = ubuntu@ubuntu:~$ cat /proc/version Linux version 5.4.0-55-generic (buildd@lcy01-amd64-013) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #61-Ubuntu SMP Mon Nov 9 20:49:56 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] - $ ls /sys/firmware/efi/efivars | grep ^Boot - ls: reading directory '/sys/firmware/efi/efivars': Input/output error - Boot mode select-7683c190-9523-4402-81ff-a11e93dc389c - Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c - BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c - BootOptionSupport-8be4df61-93ca-11d2-aa0d-00e098032b8c + 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 + + 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. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899993 Title: EFI: Fails when BootCurrent entry does not exist Status in curtin package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Committed Status in curtin source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in curtin source package in Bionic: Invalid Status in linux source package in Bionic: Fix Committed Status in curtin source package in Focal: Invalid Status in linux source package in Focal: Fix Committed Status in curtin source package in Groovy: Invalid Status in linux source package in Groovy: Fix Committed Status in curtin source package in Hirsute: Invalid Status in linux source package in Hirsute: Fix Committed Bug description: [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: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1899993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
