[Bug 2123887] Re: [SRU] Backport nullboot automated testing to Noble and Jammy

[Timo Aaltonen]

Hello Mate, or anyone else affected,

Accepted ubuntu-boot-test into jammy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/ubuntu-
boot-test/2.1~22.04 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.

** Tags removed: verification-done
** 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 ubuntu-boot-test in Ubuntu.
https://bugs.launchpad.net/bugs/2123887

Title:
  [SRU] Backport nullboot automated testing to Noble and Jammy

Status in ubuntu-boot-test package in Ubuntu:
  Invalid
Status in ubuntu-boot-test source package in Jammy:
  Fix Committed
Status in ubuntu-boot-test source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * There has been serious issues caused by untested nullboot SRUs
     breaking production deployments of Azure CVMs.

   * This change adds an automated test of the nullboot package to
     ubuntu-boot-test package, gating the migration of nullboot out
     of -proposed against a successful nullboot update on a simulated
     CVM.

  [ Test Plan ]

   * If the existing and newly added autopkgtests in ubuntu-boot-test
     package pass, with the correct output in the test log, this
     change works as intended.

   * ubuntu-boot-test is not intended to be installed or used on end user
     machines, thus there isn't any value in traditional manual local tests.

  [ Where problems could occur ]

   * The ubuntu-boot-test package was never seeded, nor is it intended to be
     used by end users.

   * The worse case scenario is regression of existing tests, but these are not
     being changed in Noble. In case of Jammy, ubuntu-boot-test isn't even part
     of the archive at present.

  [ Other Info ]

   * Despite being a universe package, ubuntu-boot-test is maintained by the
     Canonical Foundations team.

   * Azure CVMs are not supported by Ubuntu on non-LTS releases, thus there is no
     value in uploading this change first to devel as no images exist that are
     required to enable this test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-boot-test/+bug/2123887/+subscriptions