** Description changed:
[Impact]
- * With legacy-server iso in focal it is possible to network boot and
interactively setup networking configuration.
- * This feature lacks in the initrd used by subiquity, and thus is not
available on the live-server.
- * This feature is now implemented in groovy and has been tested to work on
multiple architectures, including s390x specific hardware (zdev code path)
- * Backport this feature to focal for 20.04.1
+ * With legacy-server iso in focal it is possible to network boot and
interactively setup networking configuration.
+ * This feature lacks in the initrd used by subiquity, and thus is not
available on the live-server.
+ * This feature is now implemented in groovy and has been tested to work on
multiple architectures, including s390x specific hardware (zdev code path)
+ * Backport this feature to focal for 20.04.1
- [Test Case]
+ [Test Case - interractive boot]
- * Build live-server iso with proposed pocket enabled
+ * Build live-server iso with proposed pocket enabled
- * Download just the kernel & initrd artefacts
+ * Download just the kernel & initrd artefacts
- * Boot kerenl & initrd and specify ignore_uuid kernel cmdline
+ * Boot kerenl & initrd and specify ignore_uuid kernel cmdline
parameter, but nothing about ip= or url= and _without_ any subiquity iso
attached.
- * Wait for boot to offer to perform network boot, configure networking,
+ * Wait for boot to offer to perform network boot, configure networking,
and accept default url, await to be booted to subiquity welcome screen
+
+ [Test case - improved UX]
+
+ * During live server boot, there is no plymouth running, and thus some
+ messages displayed during boot are ugly warnings, which are harmless and
+ actually should not be there or improved:
+
+ - Newline added between progress '.....' and the check result message
+ - Warning "Connection to playmouth" is dropped, as server normally boots
without plymouth, thus this warning should not be printed.
+ - Failure to mount /cow -> the code to expose /cow in the root never
worked, and always printed error, stop doing that.
+
+ * Ideally, booting kernel+initrd with "quiet" should result in crisp
+ experience without a single warning message printed, until one is
+ informed that local installation media was not found and remote network
+ boot is offered.
+
+ * Test case is to check that fsck progress dots look nice, there is no
+ inline mixed '....' with text, and that there is no "Connection to
+ plymouth" error message, or an error message about /cow.
+
[Regression Potential]
- * Previously when booting kernel/initrd without iso attached to the
+ * Previously when booting kernel/initrd without iso attached to the
machine, the boot would fail and drop to emergency shell. Now
interactive network setup is offered, and if that fails, then drop to
emergency shell. So whilst there is added interactivity, eventually
dropping to emergency shell is still there.
[Other Info]
-
- * There are many other bug reports requesting this feature, all of which
will be closed once this update lands on the daily isos.
+
+ * There are many other bug reports requesting this feature, all of
+ which will be closed once this update lands on the daily isos.
** Summary changed:
- Backport casper from groovy to support interactive network boot on focal
+ Backport casper changes from groovy to support interactive network boot on
focal, and improved interractive boot UX on server
** Also affects: casper (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: casper (Ubuntu)
Status: New => Fix Released
** Changed in: casper (Ubuntu Focal)
Status: New => In Progress
** Changed in: casper (Ubuntu Focal)
Importance: Undecided => High
** Changed in: casper (Ubuntu Focal)
Milestone: None => ubuntu-20.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884933
Title:
Backport casper changes from groovy to support interactive network
boot on focal, and improved interractive boot UX on server
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1884933/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
