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
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-z-systems/+bug/1884933/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
