So if /etc/resolv.conf was pointing at stub-resolv.conf everything would
have worked.
However, at closer inspection, netplan test suite has also been miss
detecting the backends used by NetworkManager and whether or not
resolved was enabled. For resolved, it was only considering nss module
and was
current base cloud-image does not have resolvconf, but has ifupdown.
The following happens:
1) cloud-init starts
2) picks ifupdown renderer
3) renders eni
4) which uses auto dhcp
5) which calls dhclient
6) because there is no resolvconf installed, default make_resolve_conf function
is used which
2 matches
Mail list logo
