subiquity

install failed crashed with CalledProcessError (apt mirror out of sync)

Bug #2038987 reported by Jane Atkinson on 2023-10-11

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	subiquity	Triaged	Medium	Unassigned

Bug Description

Had entered "Who are you" information during Install (entire disk) when this happened.

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: Wed Oct 11 03:38:46 2023
DesktopInstallerRev: 1257
ExecutablePath: /snap/ubuntu-desktop-installer/1257/bin/subiquity/subiquity/cmd/server.py
InterpreterPath: /snap/ubuntu-desktop-installer/1257/usr/bin/python3.10
LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
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/1257/usr/bin/python3.10 -m subiquity.cmd.server --use-os-prober --storage-version=2 --postinst-hooks-dir=/snap/hostname-desktop-installer/1257/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: 1257
SnapUpdated: False
SnapVersion: 0+git.bca6e31c
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: 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-q35-6.2
dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-6.2
dmi.sys.vendor: QEMU

Tags:

Revision history for this message

Jane Atkinson (irihapeti) wrote on 2023-10-11:

CrashDB.txt Edit (162 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (80.0 KiB, text/plain; charset="utf-8")
DesktopInstallerLog.txt Edit (31.1 KiB, text/plain; charset="utf-8")
InstallerServerLog.txt Edit (148.7 KiB, text/plain; charset="utf-8")
InstallerServerLogInfo.txt Edit (7.9 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (77.5 KiB, text/plain; charset="utf-8")
Lspci-vt.txt Edit (1.0 KiB, text/plain; charset="utf-8")
Lsusb-v.txt Edit (7.9 KiB, text/plain; charset="utf-8")
ProbeData.txt Edit (47.4 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (3.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (5.2 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Syslog.txt Edit (315.1 KiB, text/plain; charset="utf-8")
Traceback.txt Edit (2.5 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (158.8 KiB, text/plain; charset="utf-8")
acpidump.txt Edit (54.6 KiB, text/plain; charset="utf-8")

information type:

Private → Public

Revision history for this message

Jane Atkinson (irihapeti) wrote on 2023-10-11:

I've made this public. It happened in a VM and there's nothing I can see that needs to be private.

Revision history for this message

Ubuntu QA Website (ubuntuqa) wrote on 2023-10-11:

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

tags:

added: iso-testing

Dan Bungert (dbungert) on 2023-10-11

Changed in subiquity:
status:	New → Triaged
importance:	Undecided → Medium
summary:	- install failed crashed with CalledProcessError + install failed crashed with CalledProcessError (apt mirror out of sync)

Revision history for this message

sudodus (nio-wiklund) wrote on 2023-10-11 (last edit on 2023-10-11):

@irihapeti,

Installation (from a cloned USB SSD into the internal SSD drive) works for me in a real computer, a Dell Latitude E7240 with a 4th gen Intel i5 CPU (with integrated graphics) and 8GiB RAM, in UEFI mode, onto GPT.

Can you see (or guess) why it fails in your virtual machine? Could there be too little memory or drive space or some other limiting factor? I guess community flavours work for you in the same virtual machine. Or should we conclude that it is a 'real bug', that this installer does not manage QEMU?

Revision history for this message

Jane Atkinson (irihapeti) wrote on 2023-10-11:

This has only recently started happening with the Subiquity installer. I had assumed that a bug had been introduced with the most recent updates (last day or so). I could try increasing memory and seeing if that makes any difference.

Revision history for this message

Dan Bungert (dbungert) wrote on 2023-10-11:

Oct 11 16:38:46 ubuntu subiquity_log.2060[6328]: E: Failed to fetch http://nz.archive.ubuntu.com/ubuntu/dists/mantic/universe/binary-amd64/Packages.xz File has unexpected size (14956792 != 14955876). Mirror sync in progress? [IP: 163.7.134.112 80]
Oct 11 16:38:46 ubuntu subiquity_log.2060[6328]: Hashes of expected file:
Oct 11 16:38:46 ubuntu subiquity_log.2060[6328]: - Filesize:14955876 [weak]
Oct 11 16:38:46 ubuntu subiquity_log.2060[6328]: - SHA256:fe30520f079000bf6ef0c80180395fc3d1df1d43afce86fe8262ee4f35b7294c
Oct 11 16:38:46 ubuntu subiquity_log.2060[6328]: - SHA1:235a5fccb331373fa2819058194b0973f3bf0865 [weak]
Oct 11 16:38:46 ubuntu subiquity_log.2060[6328]: - MD5Sum:41cf3ef6b649b2043101cc4d6f08bbf6 [weak]
Oct 11 16:38:46 ubuntu subiquity_log.2060[6328]: Release file created at: Wed, 11 Oct 2023 00:30:47 +0000
Oct 11 16:38:46 ubuntu subiquity_log.2060[6328]: E: Failed to fetch http://nz.archive.ubuntu.com/ubuntu/dists/mantic/universe/dep11/Components-amd64.yml.xz
Oct 11 16:38:46 ubuntu subiquity_log.2060[6328]: E: Failed to fetch http://nz.archive.ubuntu.com/ubuntu/dists/mantic/universe/cnf/Commands-amd64.xz
Oct 11 16:38:46 ubuntu subiquity_log.2060[6328]: E: Failed to fetch http://nz.archive.ubuntu.com/ubuntu/dists/mantic/multiverse/dep11/Components-amd64.yml.xz
Oct 11 16:38:46 ubuntu subiquity_log.2060[6328]: E: Some index files failed to download. They have been ignored, or old ones used instead.

Apt update has failed. We have mirror controls to proceed with an offline install but this was not finalized in time for 23.10. If you try again later I expect you'll get better results.

Revision history for this message

Jane Atkinson (irihapeti) wrote on 2023-10-11:

I just tried another attempt at installing Budgie with more RAM. It made no difference. I didn't get time to finish entering password before the slideshow started, and then the thing crashed.

(I seem to be crashing a lot of things this testing cycle!)

Revision history for this message

sudodus (nio-wiklund) wrote on 2023-10-11:

#10

Could bug #2033423 and this bug be caused by the same problematic code in the installer and/or in QEMU?

Revision history for this message

Jane Atkinson (irihapeti) wrote on 2023-10-11:

#11

@sudodus That would make sense. It occurs at about the same place in the install process. If there's no online connection, the installer gives up right there; if there is an online connection, it crashes/quits if apt isn't working properly.

Revision history for this message

Jane Atkinson (irihapeti) wrote on 2023-10-11:

#12

I've tried a couple of bare-metal installs to an external SSD drive. I had no problems entering the "who are you" details and completing the install.

It seems to me that this is at least partly a qemu/kvm issue. It's possible that the online install just happened to get the apt repos at the right time :) , so I'll reserve judgment on that issue, but offline definitely would seem to be qemu/kvm.

Which is a pity, as I have no spare amd64 devices, and don't like using my main box in case I "try" to install to the wrong disk/partition. :(

Revision history for this message

Dimitri John Ledkov (xnox) wrote on 2023-10-12:

#13

I believe this is common on release date and it "fixes" it self by freezing release pocket and thus slowly it's timestamps becoming in the past for anybody in early or late timezones, and local timezone clocks, instead of UTC.

To the point where we potentially should employ the snapd strategy - snapd uses timestamps from valid assertion signatures to advance clock to the most recent signature timestamp, because we trust snapd assertions authority.

Similarly, if ubuntu archive release file has time signed in the future, we clearly should be advancing the local system clock forward.

Revision history for this message

sudodus (nio-wiklund) wrote on 2023-10-16 (last edit on 2023-10-16):

#14

Now (with the iso file dated 20231016.1) I am affected too (at least I get the same error output).

The Ubuntu mantic-desktop-amd64.iso failed, but after that the Lubuntu mantic-desktop-amd64.iso succeeded, so I have confirmed that the computer is working correctly (nothing ugly has turned off booting from the internal drive of my Dell Latitude E7240).

Revision history for this message

sudodus (nio-wiklund) wrote on 2023-10-16:

#15

Dell Latitude E7240 in UEFI mode (not secure boot), booted from cloned iso file. There was a previous Lubuntu system.

New since this morning:Early when started the installer there is a window "Update to version 0+git.1c719695", I did that and restarted the installer.

Several errors popups are shown. I sent reports ...

Anyway, the installation finished and the installed system booted and reached the desktop environment correctly :-)

Revision history for this message

Jane Atkinson (irihapeti) wrote on 2023-10-16:

#16

I just tried again with Ubuntu 20231016.1 on a no-network bare-metal install; plugged the ethernet cable in long enough to update the installer, then removed it again (no WiFi on this box). The installer still quit on "configuring apt".

So, it seems that it's not quite up to the job of doing offline installs.

Apropos of comment #12 above, I've discovered I can disable the SATA controller in UEFI; thus I can't accidentally try to install to the system disk. :)