[Bug 1884933] Re: Backport casper changes from groovy to support interactive network boot on focal, and improved interractive boot UX on server

[Frank Heimes]

I tested this now using your kernel and initrd, Michael, on a z/VM
guest.

The interactive boot UX seems to work fine, the installer boot
completed, and I could login to the initial subiquity UI.

So far so good - regarding this ticket.

I proceeded with the installation, and first of all selected NOT to
update the installer to the latest level, and ran into the following two
things:

In the zdev setup screen I noticed that some standard devices are now
marked as failed:

======================================================================
  Zdev setup                                                [ Help ]
======================================================================
  ID                          ONLINE  NAMES
                                           
  generic-ccw                                  
  0.0.0009                                    >
  0.0.000c                    failed          >
  0.0.000d                    failed          >
  0.0.000e                    failed          >            

 dasd-eckd                                       
  0.0.0190                                    >  
  0.0.0191                                    >  
  0.0.019d                                    >  
  0.0.019e                                    >  
  0.0.0200                                    >  
  0.0.0300                                    >  
  0.0.0400                                    >  
  0.0.0592                                    >  

I enabled only DASD 0200 - and notice that there are no FCP/multipath
devices in the system.

But later on the installer failed due to a curtin issue with the
multipath detection.


Please see details in the attached log and find a tgz with crash and log in the following tgz.

(probably worth to open a separate ticket - but I will also retry with
updating subiquity to latest level)


** Attachment added: "test.txt"
   https://bugs.launchpad.net/ubuntu-z-systems/+bug/1884933/+attachment/5390419/+files/test.txt

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to casper in 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

Status in Ubuntu on IBM z Systems:
  New
Status in casper package in Ubuntu:
  Fix Released
Status in casper source package in Focal:
  Fix Committed

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

  [Test Case - interractive boot]

   * Build live-server iso with proposed pocket enabled

   * Download just the kernel & initrd artefacts

   * 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, 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
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1884933/+subscriptions