the issue Richard describes also applies to GCP and Azure instances.
The netplan configuration is not re-generated if the mac address changes
and is hardcoded with a `match: { mac: address}`. So if a image is
created the newly spawned instances do not have network enabled on their
main interface.
the only work around i've found is
```
# disabling default cloudInit network and enable dhcp based on known interfaces
echo "network: {config: disabled}" >
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
echo 'network:
version: 2
renderer: networkd
ethernets:
ens5:
dhcp4: true
dhcp6: true
optional: true
ens4:
dhcp4: true
dhcp6: true
optional: true
' > /etc/netplan/50-cloud-init.yaml
```
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846535
Title:
cloud-init 19.2.36 fails with python exception "Not all expected
physical devices present ..." during bionic image deployment from
MAAS
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1846535/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
