© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
We ran into the same issue with Subiquity erroring out on an invalid "broadcast" key.
We're using a locally hosted 'user-data' on an HTTP server with the 'nocloud' datasource.
We figured out that the Subiquity snap could be updated to the one with the fix before it parses the file by inserting a cloud-init 'runcmd' into our 'user-data' that's processed by the installer live image 'cloud-init' run on boot.
We then had to disable the Subiquity installer refresh in the 'autoinstall' key or it would "upgrade" from the edge snap to the stable snap, and break again.
i.e.
#cloud-config
### SECTION01: Configures user-data values for the cloud-init that launches the LiveOS installer image.
...
runcmd:
- systemctl disable --now ssh
- systemctl mask ssh
- snap refresh subiquity --edge
...
### SECTION02: The autoinstall key turns into /autoinstall.yaml that is read by Subiquity on startup, the early-commands are run, and then /autoinstall.yaml is re-read.
autoinstall:
version: 1
refresh-
update: no
...
That fixed the issue for us. Once the 24.04 ISO is updated or the stable Subiquity snap version is updated we can update/remove that cloud-init 'runcmd' from our 'user-data' as it (hopefully) won't be needed.
Thankfully this avoided us needing to spin a custom install ISO with an updated Subiquity snap. We can just use the release ISO synced to the local mirror.