Public bug reported: I'm using the following stanza in my cloud-init VM configurations:
manage_resolv_conf: true resolv_conf: nameservers: - 8.8.8.8 - 8.8.4.4 However, neither /etc/resolv.conf not 'systemd-resolv --status' reflects it. In both cases, DNS is delegated to the virtualisation host. The virtualisation host is: paag@pavilion:~/virt/images$ uname -a Linux pavilion 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux paag@pavilion:~/virt/images$ virsh --version 4.0.0 I'm creating the VMs directly with virsh. ** Affects: cloud-init Importance: Undecided Status: New ** Attachment added: "cloud-init.tar" https://bugs.launchpad.net/bugs/1843221/+attachment/5287413/+files/cloud-init.tar -- 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/1843221 Title: manage_resolv_conf not working in ubuntu18.04 cloud images Status in cloud-init: New Bug description: I'm using the following stanza in my cloud-init VM configurations: manage_resolv_conf: true resolv_conf: nameservers: - 8.8.8.8 - 8.8.4.4 However, neither /etc/resolv.conf not 'systemd-resolv --status' reflects it. In both cases, DNS is delegated to the virtualisation host. The virtualisation host is: paag@pavilion:~/virt/images$ uname -a Linux pavilion 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux paag@pavilion:~/virt/images$ virsh --version 4.0.0 I'm creating the VMs directly with virsh. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1843221/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp