The bug is that nameservers needs to be indented *under* eth0.
However, cloud-init upstream does not parse or process nameservers[1] from Azure metadata, so I can't understand why you have this bug unless the cloud-init 19.1 on SLES has some downstream patches.
Thanks for the bug and the logs. Looking at the network-config that was generated:
>>> print(yaml.dump(nc, default_ flow_style= False, indent=4))
macaddress : 00:0d:3a:6d:ca:25
ethernets:
eth0:
dhcp4: true
match:
set-name: eth0
nameservers:
addresses: 168.63.129.16
search: xkf00b0rtzgejk
The bug is that nameservers needs to be indented *under* eth0.
However, cloud-init upstream does not parse or process nameservers[1] from Azure metadata, so I can't understand why you have this bug unless the cloud-init 19.1 on SLES has some downstream patches.
1. https:/ /git.launchpad. net/cloud- init/tree/ cloudinit/ sources/ DataSourceAzure .py#n1305