request to /storage/v2/guided crashed with ValueError

[geole0]

with daily during installation three consecutive crash after choosing the disk.

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-0ubuntu7
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.493
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
Date: Tue Feb 20 18:36:02 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 (20240219)
MachineType: TOSHIBA SATELLITE S70t-A
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.11, Python 3.11.8, python3-minimal, 3.11.4-5ubuntu1
PythonDetails: N/A
SnapChannel:

SnapRevision: 6
SnapUpdated: False
SnapVersion: 0+git.15cde5fb
SourcePackage: subiquity
Title: request to /storage/v2/guided crashed with ValueError
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2014
dmi.bios.release: 1.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.30
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
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: 1.30
dmi.modalias: dmi:bvnInsydeCorp.:bvr1.30:bd04/18/2014:br1.30:efr1.30:svnTOSHIBA:pnSATELLITES70t-A:pvrPSKN6E-01C00KFR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKN6E:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE S70t-A
dmi.product.sku: PSKN6E
dmi.product.version: PSKN6E-01C00KFR
dmi.sys.vendor: TOSHIBA

[Divipranesh (divipranesh)]

same bug affecting me cant find the solution

[Benjamin Bellamy (benjaminbellamy)]

Same here.
This bug has been here for YEARS.

[Robb (grefyne)]

same here

[arnoldthebat (tony-ditchfield)]

Note that this appears to be relate to the initial drive being LUKS encrypted when selecting the drive to install.

Using a differing drive (even if LUKs encrypted), or formatting the initial drive prior to install, allows the installer to succeed.

[geole0 (geole0)]

Good morning

Thanks for the explanation. Indeed, there was an old installation. I didn't know that the disk had to be blank to install on the entire disk.

THANKS

[geole0 (geole0)]

ood morning

Thanks for the explanation. Indeed, there was an old ENCRYPTED installation. I didn't know that the disk had to be blank to install on the entire disk.

THANKS

[geole0 (geole0)]

Good morning

Thanks for the explanation. Indeed, there was an old ENCRYPTED installation. I didn't know that the disk had to be blank to install on the entire disk.

THANKS