@ThomasBechtold. I've tested bionic, focal and jammy with the following procedure:
cat > user-data <<EOF #cloud-config ssh_import_id: [chad.smith] EOF
for series in bionic focal jammy; do lxc init ubuntu-daily/$series lp-1988401-$series lxc config set lp-1988401-$series cloud-init.user-data="$(cat user-data)" lxc config template delete lp-1988401-$series cloud-init-meta.tpl lxc config template delete lp-1988401-$series cloud-init-network.tpl lxc config template delete lp-1988401-$series cloud-init-user.tpl lxc config template delete lp-1988401-$series cloud-init-vendor.tpl lxc start lp-1988401-$series sleep 5 lxc exec lp-1988401-$series -- cloud-init status --wait --long lxc exec lp-1988401-$series -- cloud-init query userdata lxc exec lp-1988401-$series -- cloud-init grep Traceback /var/log/cloud-init.log done
All tests come up with LXD datasource properly, no Tracebacks and proper userdata being passed through to the instance.
@ThomasBechtold.
I've tested bionic, focal and jammy with the following procedure:
cat > user-data <<EOF
#cloud-config
ssh_import_id: [chad.smith]
EOF
for series in bionic focal jammy; do daily/$ series lp-1988401-$series user-data= "$(cat user-data)" network. tpl vendor. tpl cloud-init. log
lxc init ubuntu-
lxc config set lp-1988401-$series cloud-init.
lxc config template delete lp-1988401-$series cloud-init-meta.tpl
lxc config template delete lp-1988401-$series cloud-init-
lxc config template delete lp-1988401-$series cloud-init-user.tpl
lxc config template delete lp-1988401-$series cloud-init-
lxc start lp-1988401-$series
sleep 5
lxc exec lp-1988401-$series -- cloud-init status --wait --long
lxc exec lp-1988401-$series -- cloud-init query userdata
lxc exec lp-1988401-$series -- cloud-init grep Traceback /var/log/
done
All tests come up with LXD datasource properly, no Tracebacks and proper userdata being passed through to the instance.