block probing crashed with TimeoutError

[corrado venturini]

Kinetic canary iso dated Aug 16. Just booted I see this crash.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.22.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.473
Date: Tue Aug 16 13:29:39 2022
ExecutablePath: /snap/ubuntu-desktop-installer/573/bin/subiquity/subiquity/cmd/server.py
InterpreterPath: /snap/ubuntu-desktop-installer/573/usr/bin/python3.8
LiveMediaBuild: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220816)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcAttrCurrent: snap.hostname-desktop-installer.subiquity-server (complain)
ProcCmdline: /snap/hostname-desktop-installer/573/usr/bin/python3.8 -m subiquity.cmd.server --use-os-prober --storage-version=2 --autoinstall=
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs maybe-ubiquity --- quiet splash
Python3Details: /usr/bin/python3.10, Python 3.10.5, python3-minimal, 3.10.4-0ubuntu2
PythonDetails: N/A
SnapChannel:

SnapRevision: 573
SnapUpdated: False
SnapVersion: 0+git.51580522
SourcePackage: subiquity
Title: block probing crashed with TimeoutError
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2017
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: H110M-G/M.2
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[corrado venturini (corradoventu)]

attaching crash file

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/1986672

[Olivier Gayot (ogayot)]

Hello and thank you for your bug report!

probert is currently a bit lacking in terms of logging and it makes it challenging for us to understand what it is spending time on.

If you would like to help, I have prepared a script to retrieve some profiling information about probert execution. The script can be run in the ubuntu desktop installer environment and will generate a tarball with collected profiling information that you can share with us.

The script is available here in the two following locations:
* https://git.launchpad.net/~ogayot/+git/profile-probert-desktop-installer/tree/profile-probert-desktop-installer.py?h=main
* https://people.canonical.com/~ogayot/profile-probert-desktop-installer.py

The steps to run the script are as follow:

* Boot the lunar-live-server ISO (preferably the latest daily image)
* Once the graphical interface is up and running, ignore the installer's interface and open a terminal window (ctrl+alt+t is a keyboard shortcut for it)
* Download the script using the following command (this requires an Internet connection)
    * wget https://people.canonical.com/~ogayot/profile-probert-desktop-installer.py
* Run the profiler using the following command:
    * sudo python3 profile-probert-desktop-installer.py
* The execution can take a few seconds to a few minutes.
* Once finished a tarball will be generated in /tmp/profiling-probert.txz
* Sharing the tarball with us should help us figure out what's going on. We'd appreciate it!

Thanks!
Olivier

[corrado venturini (corradoventu)]

No longer occurred due to fix or new version. Marked as Invalid.