install failed crashed with ReadTimeout

[Ken VanDine]

Installation with TPM enabled fails

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.482
CurtinAptConfig: /var/log/installer/subiquity-curtin-apt.conf
Date: Thu Sep 7 14:20:01 2023
ExecutablePath: /snap/ubuntu-desktop-installer/1229/bin/subiquity/subiquity/cmd/server.py
InterpreterPath: /snap/ubuntu-desktop-installer/1229/usr/bin/python3.10
LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230907)
MachineType: LENOVO 4810CT0100
ProcAttrCurrent: snap.hostname-desktop-installer.subiquity-server (complain)
ProcCmdline: /snap/hostname-desktop-installer/1229/usr/bin/python3.10 -m subiquity.cmd.server --use-os-prober --storage-version=2 --postinst-hooks-dir=/snap/hostname-desktop-installer/1229/etc/subiquity/postinst.d
ProcEnviron:
 LANG=C.UTF-8
 LD_LIBRARY_PATH=<set>
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=standard.live.squashfs --- quiet splash
Python3Details: /usr/bin/python3.11, Python 3.11.5, python3-minimal, 3.11.4-5
PythonDetails: N/A
SnapChannel:

SnapRevision: 1229
SnapUpdated: False
SnapVersion: 0+git.09349bf4
SourcePackage: subiquity
Title: install failed crashed with ReadTimeout
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/07/2017
dmi.bios.release: 0.8
dmi.bios.vendor: LENOVO
dmi.bios.version: R0RET08L (0.08 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4810CT0100
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 0.0
dmi.modalias: dmi:bvnLENOVO:bvrR0RET08L(0.08):bd09/07/2017:br0.8:efr0.0:svnLENOVO:pn4810CT0100:pvrThinkPad133rdGen:rvnLENOVO:rn4810CT0100:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_4810_BU_Think_FM_ThinkPad133rdGen:
dmi.product.family: ThinkPad 13 3rd Gen
dmi.product.name: 4810CT0100
dmi.product.sku: LENOVO_MT_4810_BU_Think_FM_ThinkPad 13 3rd Gen
dmi.product.version: ThinkPad 13 3rd Gen
dmi.sys.vendor: LENOVO

[Dan Bungert (dbungert)]

I don't think this is FDE related, I think this is a transient network thing. This is not a crash we've seen before, but I did see weird subiquity snap build failures this morning that are already resolved without change that look like they are network related.

Please repeat the install on the same setup and see if you get a different result. Thanks!

[Ken VanDine (ken-vandine)]

I made several more attempts, with and without networking and hit what appeared to be the same error condition. However, without FDE it worked (without networking).

[Dan Bungert (dbungert)]

We are hitting 60s read timeouts when attempting to perform action=INSTALL step=FINISH for core boot encrypted.

[Dan Bungert (dbungert)]

In my case, making the timeout longer allows the step to complete with apparent success, but fails on first boot and recovery key prompts.

[Michael Vogt (mvo)]

Thanks for reporting this. The issue here is that the "seal" operation in snapd can take a very long time. For historic reasons we lock the state during the operation and block other snapd operations (including /v2/changes). This obviously is a bug and we are working on a fix.

[Michael Vogt (mvo)]

Just for the record - there is a draft PR in https://github.com/snapcore/snapd/pull/13171 - the code in there will change after the latest discussions we had and the PR number may actual change (because we may to a prereq PR first with some groundwork) but we are actively working on this.

[Michael Vogt (mvo)]

@Dan if your first boot fails with the long timeout, could you please share your device details and (if possible) the log output of the failed boot?

[Dan Bungert (dbungert)]

> log output of the failed boot?

Rather boring, or maybe that is itself a clue:

```
/EndEntire
/EndEntire
<screen clear>
[timestamp] x86/cpu: SGX disabled by BIOS.
Please enter the recovery key for disk /dev/disk/by-partuuid/<uuid>: (press TAB for no echo)
```

> device details

Not sure what would be relevant here. TPM info from dmesg below, tarball of logs attached.
kernel: tpm_tis MSFT0101:00: 2.0 TPM (device-id 0x1A, rev-id 16)

[Dan Bungert (dbungert)]

Subiquity workaround committed in terms of a longer timeout.

[chandrahjr (chandrahjr)]

I can reproduce as mentioned above on a fresh installation
```
/EndEntire
/EndEntire
<screen clear>
[timestamp] x86/cpu: SGX disabled by BIOS.
Please enter the recovery key for disk /dev/disk/by-partuuid/<uuid>: (press TAB for no echo)
```

i5-9500
gigabyte gaming Z390
Intel PTT enabled, in TPM2.0 mode.

At the end of the installer, running command to show the key doesn't work, reportedly because it checks the installation usb boot environment instead of the freshly-installed environment.

[chandrahjr (chandrahjr)]

I see another bug posted regarding legacy bios modes -- this is not that -- I am repro'ing above with UEFI mode, with CSM disabled.

[Andrew Pelletier (betaubuntu)]

I was able to get it to work by
1. Boot USB Installer
2. Connect to Network and update installer
3. Proceed through installation by selecting no network for now.
4. Select TPM installation
5. Success

So it does seem to be network related.

Edit: Not sure if it was just luck. It worked as mentioned above on a VM but same steps did not provide success on my laptop.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sebastien Bacher (seb128)]

Closing that ubuntu-desktop-installer report since the component is deprecated. We aren't going to fix 23.10 installer bugs at this point and Noble uses ubuntu-desktop-provision, feel free to reopen/reassign to that component if that's still an issue with the noble beta image

[Rolf Lehfeld (mannig111)]

Keine Ahnung.
Steigt bei der Installation ohne Kommentar oder Hinweis aus.Weder
Weder die Version 22 noch die Version lässt sich installieren.
Mehr kann ich nicht sagen, weil das System keine Verständlichen Hinweise gibt.
Habe jetzt 10 Std versucht Ubuntu zu installieren.

MfG
Lehfeld

[Rolf Lehfeld (mannig111)]

Nach n-versuchen ergibt sich immer das gleiche Bild.
Er steigt immer ohne Kommentar an der gleich Stelle aus oder anders ausgedrückt:
Das System steht wie eine EINS.
Nichts rührt sich.

[Rolf Lehfeld (mannig111)]

Das Netzwerk funktioniert.
Ich komme in das Internet.