install failed crashed with CalledProcessError

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

Bug Description

I was interrupted between typing password and repeating the password (for login). Maybe it is a duplicate of a recent bug report.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
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-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.487
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: Fri Nov 17 18:33:14 2023
DesktopInstallerRev: 1272
ExecutablePath: /snap/ubuntu-desktop-installer/1272/bin/subiquity/subiquity/cmd/server.py
InterpreterPath: /snap/ubuntu-desktop-installer/1272/usr/bin/python3.10
LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231117)
MachineType: TOSHIBA SATELLITE PRO C850-19W
ProcAttrCurrent: snap.hostname-desktop-installer.subiquity-server (complain)
ProcCmdline: /snap/hostname-desktop-installer/1272/usr/bin/python3.10 -m subiquity.cmd.server --use-os-prober --storage-version=2 --postinst-hooks-dir=/snap/hostname-desktop-installer/1272/etc/subiquity/postinst.d
ProcEnviron:
 LANG=C.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:

SnapRevision: 1272
SnapUpdated: False
SnapVersion: 0+git.417b2d8a
SourcePackage: subiquity
Title: install failed crashed with CalledProcessError
UdiLog: Error: [Errno 40] Too many levels of symbolic links: '/var/log/installer/ubuntu_desktop_installer.log'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2012
dmi.bios.release: 6.10
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: PLCSF8
dmi.board.vendor: Intel
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 6.0
dmi.modalias: dmi:bvnInsydeCorp.:bvr6.10:bd09/24/2012:br6.10:efr6.0:svnTOSHIBA:pnSATELLITEPROC850-19W:pvrPSCBXE-00C00VN5:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSCBXE:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE PRO C850-19W
dmi.product.sku: PSCBXE
dmi.product.version: PSCBXE-00C00VN5
dmi.sys.vendor: TOSHIBA

Revision history for this message
sudodus (nio-wiklund) wrote :
information type: Private → Public
Revision history for this message
sudodus (nio-wiklund) wrote :

Tried to install with encryption, maybe the same bug as reported previously,

https://bugs.launchpad.net/subiquity/+bug/2043585

but I am not sure about the symptoms, so I report as a separate bug.

I tried again (so twice with today's daily build) and the same thing happened.

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:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2043837

tags: added: iso-testing
Revision history for this message
Olivier Gayot (ogayot) wrote :

Thank you for your bug report. Indeed this is the same root cause as in the other bugs when installing noble with encryption enabled.

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.