[Bug 1990504] Re: nullboot 0.4.0 jammy SRU

[Timo Aaltonen]

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.

** Changed in: nullboot (Ubuntu Jammy)
       Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1990504

Title:
  nullboot 0.4.0 jammy SRU

Status in nullboot package in Ubuntu:
  Invalid
Status in nullboot source package in Jammy:
  Fix Committed

Bug description:
  [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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nullboot/+bug/1990504/+subscriptions