You can reproduce this by running `cloud-init schema --system` in the debug shell. As you will see there, it finds that the network-config.json is invalid (so the cloud-config.txt is valid!)
The server iso [1] uses subiquity version 24.04.1, which has cloud-init 23.4.4-0ubuntu0~22.04.1 built in.
The fix for the issue you're observering is in cloud-init 24.1.1 or higher [2], as that contains the fix for this issue [3].
Refreshing the installer via a directive in your autoinstall.yaml wouldn't help, because the schema is invalid, so it doesn't get there...
... however, one could run `snap refresh subiquity --channel=latest/edge` by hand at the shell prompt after the error occurs. From there, the install will continue to run.
You can reproduce this by running `cloud-init schema --system` in the debug shell. As you will see there, it finds that the network-config.json is invalid (so the cloud-config.txt is valid!)
The server iso [1] uses subiquity version 24.04.1, which has cloud-init 23.4.4- 0ubuntu0~ 22.04.1 built in.
The fix for the issue you're observering is in cloud-init 24.1.1 or higher [2], as that contains the fix for this issue [3].
Refreshing the installer via a directive in your autoinstall.yaml wouldn't help, because the schema is invalid, so it doesn't get there...
```
refresh-installer:
update: true
channel: latest/edge
```
... however, one could run `snap refresh subiquity --channel= latest/ edge` by hand at the shell prompt after the error occurs. From there, the install will continue to run.
[1] https:/ /releases. ubuntu. com/24. 04/ubuntu- 24.04-live- server- amd64.iso /github. com/canonical/ cloud-init/ blob/main/ ChangeLog# L21 /bugs.launchpad .net/ubuntu/ +source/ cloud-init/ +bug/2056460
[2] https:/
[3] https:/