Sounds good. Since we have a resolution, I'm going to go ahead and close
this bug as "won't fix", but feel free to continue the conversation if
you have any more concerns.
** Changed in: cloud-init
Status: Incomplete => Won't Fix
--
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/2003048
Title:
[Azure] User's customized dns search domains is over-written as re-
config network on every boot
Status in cloud-init:
Won't Fix
Bug description:
Description of problem:
This issue only exists on Azure cloud-init.
With the 22.1 version, we add dns search domains via nmcli con modify 'System
eth0' +ipv4.dns-search domain.tld, after reboot, the config is over-written by
cloud-init(the changes to /etc/sysconfig/network-scripts/ifcfg-eth0 get
deleted, they used to be persistent), as Azure apply networking config on every
BOOT[1] since cloud-init-22.1
[1] https://github.com/canonical/cloud-init/pull/1023
But some users prefer to persist the customized network config(e.g. DNS)
after reboot, so could you please help to check how to enhance this patch[1] to
meet customer's requirement[2]?
[2] User's requirements:
We add additional search domains to certain servers, mostly because they
communicate with legacy urls in our company without using fqdn.
Additional info:
Below[3] is a workaround to persist user's customized DNS. But as all the
customized network configs will be over-written after reboot, so maybe we need
to consider how to avoid it.
[3] Adding the customized DNS to /etc/dhcp/dhclient.conf,
e.g.
Modify /etc/dhcp/dhclient.conf
timeout 300;
append domain-search "searchdomain1.com";
append domain-search "searchdomain2.com";
append domain-name-servers 1.1.1.1;
Reboot the VM and then check the dns information, the modifications are not
overwritten.
# cat /etc/resolv.conf
# Generated by NetworkManager
search searchdomain1.com searchdomain2.com
nameserver 1.1.1.1
Test Veision: 22.1
How reproducible:
Modify dns search domains, reboot
Steps to Reproduce:
1. nmcli con modify 'System eth0' +ipv4.dns-search example.com
2. systemctl reboot
Actual results:
$ grep example.com /etc/resolv.conf
[No result]
Expected results:
$ grep example.com /etc/resolv.conf
search example.com
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2003048/+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
