Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/3189
** Bug watch added: github.com/canonical/cloud-init/issues #3189 https://github.com/canonical/cloud-init/issues/3189 ** Changed in: cloud-init Status: Confirmed => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1774540 Title: bionic: DNS search domains lost from cloud-init to netplan Status in cloud-init: Expired Bug description: On a deployed node with a MAAS datasource, /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg contains: network: config: - id: enp1s0 mac_address: 52:54:00:9a:b4:64 mtu: 1500 name: enp1s0 subnets: - address: 10.48.7.48/21 dns_nameservers: - 10.48.0.5 gateway: 10.48.0.1 type: static type: physical - address: - 10.48.0.5 search: - bos01.canonistack.internal type: nameserver version: 1 But the generated /etc/netplan/50-cloud-init.yaml contains no search domains under nameservers for the interface: # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} network: version: 2 ethernets: enp1s0: addresses: - 10.48.7.48/21 gateway4: 10.48.0.1 match: macaddress: 52:54:00:9a:b4:64 mtu: 1500 nameservers: addresses: - 10.48.0.5 set-name: enp1s0 Related bugs: * bug 1750884: /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1774540/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
