Hi Paride,
We are hitting this on RHEL as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892447
Title:
Why ignore new name server if 3 name servers exists
To manage notifications about this
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892447
Title:
Hi,
I agree: the "stale" resolv.conf may disrupt the nameserver
configuration, and do it in a way that depends on the number of
nameservers listed there.
Adding the /etc/resolv.conf nameservers to the *tail* of the nameserver
list (trimmed to 3 entries) may be the most sensible thing to do.
--
I set back to 'New', Pengpeng's comment does make sense.
cloudinit/net/sysconfig.py's render_network_state calls _render_dns.
_render_dns then will load the existing file if it is present.
So the end result is that if we have a "stale" version of
/etc/resolv.conf on the system, then the dns
[Expired for cloud-init (Ubuntu) because there has been no activity for
60 days.]
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
emm...I see the new name servers are appended to the current name
servers list. https://github.com/canonical/cloud-
init/blob/master/cloudinit/distros/parsers/resolv_conf.py#L79
So the new name servers are always in the tail, if there are already 3
current name servers exist, then any new name
Hi Pengpeng,
I think it boils down to arbitrary choice: we either need to discard the
head or the tail of the list, and the current implementation discards
the tail. I think the most common way to order nameservers is by
decreasing priority, so the current implementation is the least
surprising
