block probing crashed with TimeoutError

Bug #1964039 reported by Chris Guiver
356
This bug affects 20 people
Affects Status Importance Assigned to Milestone
subiquity
New
Undecided
Unassigned

Bug Description

Ubuntu Jammy canary ISO LIVE test on
- dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

Sorry I have limited details to provide.

Problem detected message appeared; so I opened terminal & explored /var/crash and have submitted the `ubuntu-bug` report from there.

If I can provide more details; I'll happily re-run test whilst I have this daily, or test using newer dailies.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.465+canary3.3
CrashDB:
 {
        "impl": "launchpad",
        "project": "subiquity",
        "bug_pattern_url": "http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml"
     }
Date: Mon Mar 7 23:58:29 2022
ExecutablePath: /snap/ubuntu-desktop-installer/313/bin/subiquity/subiquity/cmd/server.py
InterpreterPath: /snap/ubuntu-desktop-installer/313/usr/bin/python3.8
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220306)
MachineType: Dell Inc. OptiPlex 755
ProcAttrCurrent: snap.hostname-desktop-installer.subiquity-server (complain)
ProcCmdline: /snap/hostname-desktop-installer/313/usr/bin/python3.8 -m subiquity.cmd.server --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.2, python3-minimal, 3.10.1-0ubuntu1
PythonDetails: N/A
SnapChannel:

SnapRevision: 313
SnapUpdated: False
SnapVersion: 0+git.b49fe8d
SourcePackage: subiquity
Title: block probing crashed with TimeoutError
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/02/2007
dmi.bios.release: 0.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0DR845
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd10/02/2007:br0.0:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0DR845:rvr:cvnDellInc.:ct3:cvr:sku:
dmi.product.name: OptiPlex 755
dmi.sys.vendor: Dell Inc.

Revision history for this message
Chris Guiver (guiverc) wrote :
Revision history for this message
Chris Guiver (guiverc) wrote :

FYI: I now note this is marked against `subiquity`... I didn't start the installer, my testing was LIVE only on this old box.

Revision history for this message
Chris Guiver (guiverc) wrote :

Another box & the same issue appeared on REPORT BUG (I used the onscreen option on 2nd box, and as this bug report was offered - I've selected it).

- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

Another live of same ISO, just different hardware

description: updated
Revision history for this message
Chris Guiver (guiverc) wrote :

Another live test (daily 20220319) and same issue
- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

information type: Private → Public Security
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

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

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

tags: added: iso-testing
Revision history for this message
corrado venturini (corradoventu) wrote :

same with subiquity 511

Revision history for this message
Olivier Gayot (ogayot) wrote (last edit ):

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

Etienne URBAH (eurbah)
tags: added: mantic
Revision history for this message
Etienne URBAH (eurbah) wrote :
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.