This unit is generating network config which I thought would be owned solely by cloud-init. Cloudinit should be generating a fallback network configuration, which sets up dhcp on the primary nic (eth0/enp0s2 etc). First you'll need to resolve the ordering cycle conflict with cloud- init.service and the scw-generate-net-config unit. Then, there is a bit of tension between cloud-init managing network config and scw-generate- net-config as that script blows away the cloud-init fallback network configuration. One alternative for cloud-init enabled images would be to only allow scw-generate-net-config to generate dhcp configs for devices != <primary_nic>. The other could be to disable cloud-init's network configuration altogether via http://cloudinit.readthedocs.io/en/latest/topics/network-config.html #disabling-network-configuration.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775086 Title: cloud-init fails to recognize scaleway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1775086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
