nullboot 0.4.0 jammy SRU

[Julian Andres Klode]

[Impact]
nullboot 0.4.0 adds an additional feature necessary for enablement of the target platform: writing JSON files with the boot order during image building, so that the boot entries can be configured at first booth.

I also correctly handles the case where the BootOrder variable was deleted by populating it, instead of producing an error which IIRC was also seen as part of the validation, but also significantly improves testing.

[Test plan]
Gauthier Jolly will build images with the proposed package and boot them on Azure CVM.

[Where problems could occur]
The potential for regressions is low as the new code path uses the mock EFI variables implementation that the test suite uses, and is just a couple of ifs in the main code.

Any failure to write JSON files during image build can easily be worked around by disabling that bit in the image building script, first boot would be slower, so they are not exactly fatal.

If people relied on missing BootOrder producing an error, they see a change in behavior.

It is unlikely anyone is using that in jammy, as it is closely tied to Azure CVM, and we only enabled focal so far, so overall I think nobody should be broken even if there were an issue.

[code review tips]
MockEfiVariables moves from efivars_test.go to efivars.go, it makes the diff a bit unwieldly.

[Timo Aaltonen (tjaalton)]

Hello Julian, or anyone else affected,

Accepted nullboot into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nullboot/0.4.0-0ubuntu0.22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Gauthier Jolly (gjolly)]

The CPC team has been building (but not publishing) Jammy CVM images with nullboot 0.4.0 for a while.

here is an example:

ubuntu@jammy-cvm:~$ dpkg -l nullboot
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-======================-============-=================================
ii nullboot 0.4.0-0ubuntu0.22.04.1 amd64 UEFI boot entry manager
ubuntu@jammy-cvm:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy

then EFI vars are correctly set:

$ sudo efibootmgr
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001
Boot0000* MsTemp
Boot0001* Ubuntu with kernel 5.15.0-1019-azure

# cat /boot/efi/EFI/ubuntu/BOOTX64.CSV
shimx64.efi,Ubuntu with kernel 5.15.0-1019-azure,\kernel.efi-5.15.0-1019-azure ,Ubuntu entry for kernel 5.15.0-1019-azure

and I can reinstall the kernel and reboot (re-sealing works).

[Launchpad Janitor (janitor)]

This bug was fixed in the package nullboot - 0.4.0-0ubuntu0.22.04.1

---------------
nullboot (0.4.0-0ubuntu0.22.04.1) jammy; urgency=medium

  * nullboot 0.4.0 for jammy (LP: #1990504)
  * Feature:
    - Support for an -output-json option to dump efi boot variables to
      a JSON file
  * Bug fixes:
    - Handle missing BootOrder variable correctly

 -- Julian Andres Klode <email address hidden> Wed, 18 May 2022 16:09:13 +0200

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for nullboot has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.