autoinstall shows completed when late-commands starts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
subiquity |
New
|
Undecided
|
Unassigned |
Bug Description
When using autoinstall (nocloud) for Ubuntu Desktop 24.04 LTS to do a zero touch installs at my university, it shows as completed when it is about start doing the late commands steps. There is no indication that runs late commands. The green "restart now" is clickable but nothing happens. This confuses things for my fellow IT-tech coworkers that do the installing and they sometimes clicked the other "continue testing" instead. It is run from USB-stick at the moment (PXE is planned in the future)
Same behaviour was on 23.04 and 23.10 as well.
I use the following example in the user-data file:
late-commands:
- mkdir /target/
- mkdir /target/opt/scripts
- cp -r /cdrom/packages /target/opt
- cp -r /cdrom/scripts / target/opt
- curtin in-target -- bash /opt/scripts/
- curtin in-target -- bash /opt/scripts/
- curtin in-target -- bash /opt/scripts/
shutdown: reboot
I have a lot more scripts than above (10 of them) that runs and fixes things (checking which brand and model and so on) so it kinda sits there showing that is ready when it is not.
Hello and thank you for your bug report,
You are right, it should be possible for the client to determine if the installation is really finished, or if late commands are still running. We are trying to find the right design to fix this issue as part of bug 2065958 so I am going to link your bug report to it.
Thanks!
Olivier