A test version of subiquity is available that incl. a fix for this bug. It can be installed at the first tUI screen of subiquity, by entering the shell and executing: snap refresh subiquity --channel=latest/edge/test --ignore-running
That allowed me to test the fix successfully, using several different cases: - 1) /boot, 2) root 3) swap - on z/VM - 1) swap, 2) root 3) /boot - on z/VM - 1) /boot, 2) root 3) swap - on LPAR - 1) swap, 2) root 3) /boot - on LPAR and regression testing the cases that still worked before (the 'workaround' cases): - 1) /boot, 2) swap 3) root - on LPAR - 1) swap, 2) /boot 3) root - on LPAR And they all worked fine for me, using custom partitioning and ext4 for the filesystems. I thing we can go ahead with the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2146873 Title: Custom partitioning on DASD ECKD (s390x) can lead to a failed installation To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2146873/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
