Hi Olivier,
fortunately I have the session still open.
These are the first two cmds:
root@ubuntu-server:/# snap run subiquity.python -c 'from probert import lvm;
print(lvm.probe_vgs_report())'
[]
root@ubuntu-server:/# lvm fullreport --reportformat json
{
"report": [
]
,
"log": [
]
}
root@ubuntu-server:/#
and for the 'udevadm info --export-db' output, please see the attachment
(since it's quite long).
And yes it is reproducible, it first happened when I tried an
autoinstall, but initially thought that something is broken with
autoinstall itself, I then did an interactive install, first with
updating the installer, where this happened, and then again without
updating (trying to narrow this down), but it happened again. So pretty
sure that this happens all the time, when trying to install to
SCSI/FCP/multipath now. Btw. earlier (way earlier) stonking images
worked.
** Attachment added: "udevadm_info_export-db.txt"
https://bugs.launchpad.net/subiquity/+bug/2165993/+attachment/5996874/+files/udevadm_info_export-db.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2165993
Title:
Ubuntu 26.10/stonking installation (image from Aug 31st) crashes on
s390x (due to probert)
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2165993/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
