subiquity

Noble install fails: crash with CalledProcessError while installing grub

Bug #2055634 reported by corrado venturini on 2024-03-01

This bug report is a duplicate of: Bug #2055294: /usr/lib/grub/grub-multi-install fails on noble-daily. Edit Remove

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	subiquity	Confirmed	Undecided	Unassigned

Bug Description

Trying install from ISO dated 2024-03-01

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.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.494
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurtinAptConfig: /var/log/installer/curtin-install/subiquity-curtin-apt.conf
Date: Fri Mar 1 10:42:13 2024
ExecutablePath: /snap/ubuntu-desktop-bootstrap/6/bin/subiquity/subiquity/cmd/server.py
InterpreterPath: /snap/ubuntu-desktop-bootstrap/6/usr/bin/python3.10
LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240301)
MachineType: Gigabyte Technology Co., Ltd. H510M H
ProcAttrCurrent: snap.hostname-desktop-bootstrap.subiquity-server (complain)
ProcCmdline: /snap/hostname-desktop-bootstrap/6/usr/bin/python3.10 -m subiquity.cmd.server --use-os-prober --storage-version=2 --postinst-hooks-dir=/snap/hostname-desktop-bootstrap/6/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.12, Python 3.12.2, python3-minimal, 3.12.1-0ubuntu1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
SnapChannel:

SnapRevision: 6
SnapUpdated: False
SnapVersion: 0+git.15cde5fb
SourcePackage: subiquity
Title: install failed crashed with CalledProcessError
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-03-01:

CrashDB.txt Edit (162 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (102.9 KiB, text/plain; charset="utf-8")
CurtinCurthooksConfig.txt Edit (5.3 KiB, text/plain; charset="utf-8")
CurtinErrors.gz Edit (31.7 KiB, application/x-gzip)
CurtinExtractConfig.txt Edit (5.3 KiB, text/plain; charset="utf-8")
CurtinInitialConfig.txt Edit (339 bytes, text/plain; charset="utf-8")
CurtinLog.txt Edit (218.3 KiB, text/plain; charset="utf-8")
CurtinPartitioningConfig.txt Edit (4.2 KiB, text/plain; charset="utf-8")
InstallerJournal.txt Edit (2.6 MiB, text/plain; charset="utf-8")
InstallerServerLog.txt Edit (942.7 KiB, text/plain; charset="utf-8")
InstallerServerLogInfo.txt Edit (14.8 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (27.1 KiB, text/plain; charset="utf-8")
Lspci-vt.txt Edit (871 bytes, text/plain; charset="utf-8")
Lsusb.txt Edit (411 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 (175.5 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")
Traceback.txt Edit (1.4 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (369.7 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

Paride Legovini (paride) wrote on 2024-03-01 (last edit on 2024-03-01):

I can confirm this bug, I'll add that in my testing this appears to only happen when installing in UEFI mode (both non-secureboot and secureboot). I didn't encounter the crash booting in BIOS mode.

This is my subiquity-traceback.txt:

https://paste.ubuntu.com/p/TxZ7T8SWDf/

subiquity-server-debug.log:

https://paste.ubuntu.com/p/zDzR3GppKd/

and curtin-install.log

https://paste.ubuntu.com/p/C8fh5yVCTN/

Changed in subiquity:
status:	New → Confirmed
summary:	- install failed crashed with CalledProcessError + Noble install fails: crash with CalledProcessError while installing grub