canonical
No DNS unless cloud-init=disabled if also netboot=nfs
Because cloud-init puts the interface in /etc/network/interfaces.d, the interplay between systemd-resolved and network-manager is blocked (network manager doesn't load the dns address into systemd-resolved.)
While the cloud-init interface has IPs and the routing table has routes -- no dns. no detail added for systemd-resolved.
And, Network Manager won't allow the interface to be started. Just a little broken network icon at the top.
Really bad when you do a casper install and the user is presented with a 'no network access' live cd.
Ver=plucky.
@hcoin A couple of things:
Because cloud-init puts the interface in /etc/network/interfaces.d, the interplay between systemd-resolved and network-manager is blocked (network manager doesn't load the dns address into systemd-resolved.)
You mentioned Plucky? I wouldn't expect cloud-init to be be touching /etc/network/interfaces.d, because it should be using netplan.
While the cloud-init interface has IPs and the routing table has routes -- no dns. no detail added for systemd-resolved.
I don't know what to do with this information. Please provide full logs from a test system.
And, Network Manager won't allow the interface to be started. Just a little broken network icon at the top.
Really bad when you do a casper install and the user is presented with a 'no network access' live cd.
Ver=plucky.
It sounds like you are using autoinstall. Please report accordingly.
You'll see it right quick if you merely put this in your bootup line. No net.
cloud-init=disabled netboot=nfs