I can confirm with Chad's steps that Subiquity will fail to see the autoinstall.
Some telltale symptoms of this are:
1. the Subiquity TUI is showing the first screen instead of carrying out the autoinstall steps
2. the following log statement in /var/log/installer/subiquity-server-debug.log
`load_autoinstall_config only_early True file None`
3. the specific error for this issue, also in subiquity-server-debug.log
`Failed loading pickled blob from /var/lib/cloud/instance/obj.pkl`
To apply the fix, for now please run
sudo snap refresh --beta subiquity
After the refresh is complete, the Subiquity TUI should change to show the progress of the autoinstall. Log statements for that will look like:
```
Loaded cloud config from /run/cloud-init/combined-cloud-config.json
autoinstall found in cloud-config
load_autoinstall_config only_early True file /autoinstall.yaml
```
I suggest not holding cloud-init SRU, as the fix for this issue will be released on or around October-12th.
I can confirm with Chad's steps that Subiquity will fail to see the autoinstall. installer/ subiquity- server- debug.log ll_config only_early True file None` server- debug.log cloud/instance/ obj.pkl`
Some telltale symptoms of this are:
1. the Subiquity TUI is showing the first screen instead of carrying out the autoinstall steps
2. the following log statement in /var/log/
`load_autoinsta
3. the specific error for this issue, also in subiquity-
`Failed loading pickled blob from /var/lib/
To apply the fix, for now please run
sudo snap refresh --beta subiquity
After the refresh is complete, the Subiquity TUI should change to show the progress of the autoinstall. Log statements for that will look like: init/combined- cloud-config. json l_config only_early True file /autoinstall.yaml
```
Loaded cloud config from /run/cloud-
autoinstall found in cloud-config
load_autoinstal
```
I suggest not holding cloud-init SRU, as the fix for this issue will be released on or around October-12th.