Public bug reported:
[ 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.
** Affects: ubuntu-boot-test (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: ubuntu-boot-test (Ubuntu Jammy)
Importance: Undecided
Assignee: Mate Kukri (mkukri)
Status: New
** Affects: ubuntu-boot-test (Ubuntu Noble)
Importance: Undecided
Assignee: Mate Kukri (mkukri)
Status: New
** Tags: foundations-todo
** Description changed:
[ Impact ]
- * There has been serious issues caused by untested nullboot SRUs
- breaking production deployments of Azure CVMs.
+ * 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.
-
+ * 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.
+ * 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.
+ * 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 packages was never seeded, nor is it intended to be
- used by end users.
+ * 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.
+ * 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.
+ * Despite being a universe package, ubuntu-boot-test is maintained by the
+ Canonical Foundations team.
** Description changed:
[ 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.
** Also affects: ubuntu-boot-test (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: ubuntu-boot-test (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: ubuntu-boot-test (Ubuntu)
Status: New => Invalid
** Changed in: ubuntu-boot-test (Ubuntu Jammy)
Assignee: (unassigned) => Mate Kukri (mkukri)
** Changed in: ubuntu-boot-test (Ubuntu Noble)
Assignee: (unassigned) => Mate Kukri (mkukri)
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2123887
Title:
[SRU] Backport nullboot automated testing to Noble and Jammy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-boot-test/+bug/2123887/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
