subiquity

install failed crashed with CalledProcessError

Bug #2049491 reported by corrado venturini on 2024-01-16

This bug report is a duplicate of: Bug #2049486: install failed crashed with CalledProcessError: apt-get update error. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	subiquity	New	Undecided	Unassigned

Bug Description

try install from iso dated 2024-01-16

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.490
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 Jan 16 07:47:37 2024
DesktopInstallerRev: 1278
ExecutablePath: /snap/ubuntu-desktop-installer/1278/bin/subiquity/subiquity/cmd/server.py
InterpreterPath: /snap/ubuntu-desktop-installer/1278/usr/bin/python3.10
LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240116)
MachineType: Gigabyte Technology Co., Ltd. H510M H
ProcAttrCurrent: snap.hostname-desktop-installer.subiquity-server (complain)
ProcCmdline: /snap/hostname-desktop-installer/1278/usr/bin/python3.10 -m subiquity.cmd.server --use-os-prober --storage-version=2 --postinst-hooks-dir=/snap/hostname-desktop-installer/1278/etc/subiquity/postinst.d
ProcEnviron:
LANG=C.UTF-8
LD_LIBRARY_PATH=<set>
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
SnapChannel:

SnapRevision: 1278
SnapUpdated: False
SnapVersion: 0+git.4edfab2b
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: 03/25/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F14
dmi.board.asset.tag: Default string
dmi.board.name: H510M H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF14:bd03/25/2022:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnH510MH:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH510MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: H510 MB
dmi.product.name: H510M H
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Tags:

Revision history for this message

corrado venturini (corradoventu) wrote on 2024-01-16:

CrashDB.txt Edit (162 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (104.4 KiB, text/plain; charset="utf-8")
CurtinCurthooksConfig.txt Edit (5.3 KiB, text/plain; charset="utf-8")
CurtinExtractConfig.txt Edit (5.3 KiB, text/plain; charset="utf-8")
CurtinInitialConfig.txt Edit (339 bytes, text/plain; charset="utf-8")
CurtinLog.txt Edit (147.3 KiB, text/plain; charset="utf-8")
CurtinPartitioningConfig.txt Edit (4.2 KiB, text/plain; charset="utf-8")
DesktopInstallerLog.txt Edit (98.8 KiB, text/plain; charset="utf-8")
InstallerServerLog.txt Edit (1.4 MiB, text/plain; charset="utf-8")
InstallerServerLogInfo.txt Edit (17.5 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (27.0 KiB, text/plain; charset="utf-8")
Lspci-vt.txt Edit (871 bytes, text/plain; charset="utf-8")
Lsusb.txt Edit (425 bytes, text/plain; charset="utf-8")
Lsusb-t.txt Edit (841 bytes, text/plain; charset="utf-8")
Lsusb-v.txt Edit (70.3 KiB, text/plain; charset="utf-8")
ProbeData.txt Edit (177.7 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (6.8 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (10.0 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Syslog.txt Edit (1.9 MiB, text/plain; charset="utf-8")
Traceback.txt Edit (2.7 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (353.4 KiB, text/plain; charset="utf-8")
acpidump.txt Edit (2.3 MiB, text/plain; charset="utf-8")

information type:

Private → Public

Revision history for this message

Ubuntu QA Website (ubuntuqa) wrote on 2024-01-16:

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/2049491

tags:

added: iso-testing

Revision history for this message

corrado venturini (corradoventu) wrote on 2024-01-16:

Installed system is working despite install problem but /var/log/installer is almost empty

corrado@corrado-n4-nn-0116:~$ ls /var/log/installer
casper-md5check.json media-info
corrado@corrado-n4-nn-0116:~$

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #2049486 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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