subiquity

block probing crashed with TimeoutError

Bug #2003278 reported by Sebastian Horatio Stillion on 2023-01-19

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	subiquity	New	Undecided	Unassigned

Bug Description

This bug affects snap ubuntu-desktop-installer as of revision 761. It is related to bug #2003276 which is a critical bug that causes installation failure on select systems. My theory is that the proper functioning of block probing has something to do with the proper functioning of the installation. The program calls for a block probe of the computer, but somehow there is no response. Because of this bug and bug #2003276, users can use the daily-legacy image for installation until a fix is committed.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.24.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.477
CurtinAptConfig: /var/log/installer/subiquity-curtin-apt.conf
Date: Wed Jan 18 23:38:51 2023
ExecutablePath: /snap/ubuntu-desktop-installer/738/bin/subiquity/subiquity/cmd/server.py
InterpreterPath: /snap/ubuntu-desktop-installer/738/usr/bin/python3.8
LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230118)
MachineType: LENOVO 20TRS00S00
ProcAttrCurrent: snap.hostname-desktop-installer.subiquity-server (complain)
ProcCmdline: /snap/hostname-desktop-installer/738/usr/bin/python3.8 -m subiquity.cmd.server --use-os-prober --storage-version=2 --postinst-hooks-dir=/snap/hostname-desktop-installer/738/etc/subiquity/postinst.d --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.9, python3-minimal, 3.10.6-1ubuntu1
PythonDetails: N/A
SnapChannel:

SnapRevision: 738
SnapUpdated: False
SnapVersion: 0+git.cc5f6d81
SourcePackage: subiquity
Title: block probing crashed with TimeoutError
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/07/2022
dmi.bios.release: 1.31
dmi.bios.vendor: LENOVO
dmi.bios.version: N30ET48W (1.31 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TRS00S00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.16
dmi.modalias: dmi:bvnLENOVO:bvrN30ET48W(1.31):bd10/07/2022:br1.31:efr1.16:svnLENOVO:pn20TRS00S00:pvrThinkPadP15vGen1:rvnLENOVO:rn20TRS00S00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TR_BU_Think_FM_ThinkPadP15vGen1:
dmi.product.family: ThinkPad P15v Gen 1
dmi.product.name: 20TRS00S00
dmi.product.sku: LENOVO_MT_20TR_BU_Think_FM_ThinkPad P15v Gen 1
dmi.product.version: ThinkPad P15v Gen 1
dmi.sys.vendor: LENOVO

See original description

Tags:

Revision history for this message

Sebastian Horatio Stillion (sstillion) wrote on 2023-01-19:

CrashDB.txt Edit (162 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (95.1 KiB, text/plain; charset="utf-8")
CurtinLog.txt Edit (69.0 KiB, text/plain; charset="utf-8")
InstallerServerLog.txt Edit (25.5 KiB, text/plain; charset="utf-8")
InstallerServerLogInfo.txt Edit (5.0 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (74.4 KiB, text/plain; charset="utf-8")
Lspci-vt.txt Edit (1.8 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (639 bytes, text/plain; charset="utf-8")
Lsusb-t.txt Edit (959 bytes, text/plain; charset="utf-8")
Lsusb-v.txt Edit (71.5 KiB, text/plain; charset="utf-8")
ProbeData.txt Edit (46.0 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (12.0 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (11.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Traceback.txt Edit (395 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (344.0 KiB, text/plain; charset="utf-8")
acpidump.txt Edit (1.4 MiB, text/plain; charset="utf-8")

information type:

Private → Public

Sebastian Horatio Stillion (sstillion) on 2023-02-01

description:

updated

Revision history for this message

Olivier Gayot (ogayot) wrote on 2023-04-04 (last edit on 2023-04-04):

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!