restarting the install doesn't update the UI

Bug #2060749 reported by Chris Peterson
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
subiquity
Invalid
Undecided
Unassigned
ubuntu-desktop-provision
Fix Committed
Undecided
Unassigned

Bug Description

If the desktop installer crashes, the "Something went wrong" screen will show up and there is a green button on the bottom right that will allow you to restart the install. After clicking the restart button it will start a spinning animation in the button but otherwise no other updates to the UI are made. I know the install in the background worked because the failure happens again and the whoopsie dialog prompts again to report a problem. However, after the second failure the restart button continues spinning and has no updates to inform the user that the retry has failed.

The particular cause of the crash is so far unimportant. To reproduce this issue, I provided an autoinstall configuration with a late command that would cause the installation to fail:

late-commands:
  - $((1/0))

but I was first made aware of this issue when encountering a real bug.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
BootstrapLog: Error: [Errno 40] Too many levels of symbolic links: '/var/log/installer/ubuntu_bootstrap.log'
CasperMD5CheckResult: pass
CasperVersion: 1.495build1
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud,/dev/vda)
CurtinAptConfig: /var/log/installer/curtin-install/subiquity-curtin-apt.conf
Date: Tue Apr 9 22:41:55 2024
ExecutablePath: /snap/ubuntu-desktop-bootstrap/111/bin/subiquity/subiquity/cmd/server.py
InterpreterPath: /snap/ubuntu-desktop-bootstrap/111/usr/bin/python3.10
LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240409)
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:

Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcAttrCurrent: snap.hostname-desktop-bootstrap.subiquity-server (complain)
ProcCmdline: /snap/hostname-desktop-bootstrap/111/usr/bin/python3.10 -m subiquity.cmd.server --use-os-prober --storage-version=2 --postinst-hooks-dir=/snap/hostname-desktop-bootstrap/111/etc/subiquity/postinst.d
ProcEnviron:
 LANG=C.UTF-8
 LD_LIBRARY_PATH=<set>
 PATH=(custom, no user)
ProcKernelCmdLine: autoinstall initrd=initrd
Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 3.12.2-0ubuntu2
PythonDetails: N/A
SnapUpdated: False
SourcePackage: subiquity
Title: curthooks crashed with CurtinInstallError
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/06/2015
dmi.bios.release: 0.0
dmi.bios.vendor: EFI Development Kit II / OVMF
dmi.bios.version: 0.0.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-jammy
dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-jammy:cvnQEMU:ct1:cvrpc-i440fx-jammy:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-jammy
dmi.sys.vendor: QEMU

Revision history for this message
Chris Peterson (cpete) wrote :
information type: Private → Public
Revision history for this message
Chris Peterson (cpete) wrote :
Changed in ubuntu-desktop-provision:
status: New → Confirmed
Revision history for this message
Chris Peterson (cpete) wrote :

Marking as confirmed because this was brought to my attention by someone else and I was able to confirm it.

Revision history for this message
Dennis Loose (dloose) wrote :

Thanks for the report, I can confirm this as well. Note that the button is supposed to restart the machine, not only the installation (the text on the error screen should be clear about this). I'll look into why this doesn't work as intended.

Revision history for this message
Dennis Loose (dloose) wrote :

Turns out we're relying on subiquity to restart the machine on the generic error page. That's probably not a great idea, so I'd propose showing a 'close' button instead. If the user decides to restart the machine they can do so using the menu in the live session.

Revision history for this message
Dennis Loose (dloose) wrote :
Changed in ubuntu-desktop-provision:
status: Confirmed → Fix Committed
Olivier Gayot (ogayot)
Changed in subiquity:
status: New → Invalid
Revision history for this message
Erkin Alp Güney (erkinalp9035) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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