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

Launchpad Bug Tracker 2123887 at bugs.launchpad.net
Tue Oct 7 10:08:28 UTC 2025


This bug was fixed in the package ubuntu-boot-test - 2.1~22.04

---------------
ubuntu-boot-test (2.1~22.04) jammy; urgency=medium

  * Enable debug output from tests by default
  * Port nullboot (Ubuntu on Azure CVM) automated test to Noble (LP: #2123887)
  * d/t/control: Run the nullboot test as part of autopkgtesting
  * Remove MAAS stream and openSUSE downloads from netboot test (LP: #2125338)
  * Disable tests other than nullboot for Jammy
  * Remove python-uefivars dependency (unused by nullboot test)

 -- Mate Kukri <mate.kukri at canonical.com>  Mon, 22 Sep 2025 10:06:18
+0100

** Changed in: ubuntu-boot-test (Ubuntu Jammy)
       Status: Fix Committed => Fix Released

-- 
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 Released
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




More information about the foundations-bugs mailing list