install failed crashed with ClientError

Bug #2064293 reported by Benjamin Drung
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
subiquity
New
Undecided
Unassigned

Bug Description

I tried to install Ubuntu 23.10 with TPM FDE in a virtual machine with virt-manager (using /usr/share/OVMF/OVMF_VARS_4M.ms.fd and an added TPM v2.0 device added).

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurtinAptConfig: /var/log/installer/subiquity-curtin-apt.conf
Date: Tue Apr 30 14:23:13 2024
DesktopInstallerRev: 1286
ExecutablePath: /snap/ubuntu-desktop-installer/1286/bin/subiquity/subiquity/cmd/server.py
InterpreterPath: /snap/ubuntu-desktop-installer/1286/usr/bin/python3.10
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
     |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcAttrCurrent: snap.hostname-desktop-installer.subiquity-server (complain)
ProcCmdline: /snap/hostname-desktop-installer/1286/usr/bin/python3.10 -m subiquity.cmd.server --use-os-prober --storage-version=2 --postinst-hooks-dir=/snap/hostname-desktop-installer/1286/etc/subiquity/postinst.d
ProcEnviron:
 LANG=de_DE.UTF-8
 LD_LIBRARY_PATH=<set>
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
SnapChannel: latest/stable
SnapRevision: 1286
SnapUpdated: False
SnapVersion: 0+git.0057491b
SourcePackage: subiquity
Title: install failed crashed with ClientError
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/11/2024
dmi.bios.release: 0.0
dmi.bios.vendor: Ubuntu distribution of EDK II
dmi.bios.version: 2024.02-2
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-8.2
dmi.modalias: dmi:bvnUbuntudistributionofEDKII:bvr2024.02-2:bd03/11/2024:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.2:cvnQEMU:ct1:cvrpc-q35-8.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-8.2
dmi.sys.vendor: QEMU

Revision history for this message
Benjamin Drung (bdrung) wrote :
information type: Private → Public
Revision history for this message
Dan Bungert (dbungert) wrote :

Hi Ben, thanks for the report.

Snapd has reported the following about the machine:

Finish setup of run system for "enhanced-secureboot-desktop" (cannot seal the encryption keys: cannot add EFI secure boot policy profile: cannot compute secure boot policy profile: the current boot was preceeded by a boot attempt to an EFI application that returned to the boot manager, without a reboot in between)

I'm not entirely sure what you do about that - is a reboot really enough? - but that's what's going on and why it failed.

Changed in subiquity:
status: New → Incomplete
Revision history for this message
Benjamin Drung (bdrung) wrote :

I entered the EFI firmware settings. Let me test the installation from a direct boot into the installer.

Revision history for this message
Benjamin Drung (bdrung) wrote :

An installation attempt is blocked by:
> not encrypting devie storage as checking TPM gave: the TPM is in DA lockout mode

Revision history for this message
Benjamin Drung (bdrung) wrote :

A fresh setup worked.

Coming back to this bug: Instead of crashing, subiquity could display that failure message do the user. Bonus points for suggesting how to fix it or point to an URL that helps debugging or where common failures are documented.

Dan Bungert (dbungert)
Changed in subiquity:
status: Incomplete → New
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.