Crash when running autoinstall with data generated from a previous install

Bug #1985098 reported by Olivier Gayot
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
subiquity
New
Undecided
Unassigned

Bug Description

Steps to reproduce:

1. Perform a subiquity installation with kvm-test.py (no autoinstall) and use the default value everywhere (next, next, next, next, done...)

$ scripts/kvm-test.py -m 2G --install --overwrite --iso jammy-live-server-amd64.iso

2. Once the installation has finished, copy over the /var/log/installer/autoinstall-user-data file to the host.

3. Perform a second subiquity installation using the autoinstall file previously generated:

$ scripts/kvm-test.py -m 2G --install --overwrite --iso jammy-live-server-amd64.iso --autoinstall-file autoinstall-user-data

The install crashes during the curtin partitioning stage.

I'm attaching the logs of the first and second installation. The autoinstall-user-data file can be found in the first archive under var/log/install/autoinstall-user-data

Revision history for this message
Olivier Gayot (ogayot) wrote :
Revision history for this message
Olivier Gayot (ogayot) wrote :
description: updated
Revision history for this message
Olivier Gayot (ogayot) wrote :

Reproduced today again using a kinetic ISO.

The invocations of `curtin install` in both runs look almost identical. Only the machine_id generated (and the resume_data directory) change ; which is expected.

The following differences are observed in curtin.log before everything starts failing:

https://pastebin.ubuntu.com/p/cHgvR3V6CK/

 * in red is where the autoinstall data was produced.
 * in green is where the autoinstall data was consumed - and the install failed.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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