BTW: using lxd provider for juju won't reproduce this issue as it goes down a slightly different path. lxd provider uses cloud-init's NoCloud datasource so it pools user-data/meta-data earlier in cloud-init which will not exhibit this race condition.
BTW: using lxd provider for juju won't reproduce this issue as it goes down a slightly different path. lxd provider uses cloud-init's NoCloud datasource so it pools user-data/meta-data earlier in cloud-init which will not exhibit this race condition.