Description of problem: When the resolv-prepender runs, it is duplicating the prepended address. For example, when starting from a resolv.conf that looks like:
# Generated by NetworkManager
# Generated by KNI resolv prepender NM dispatcher script
# nameserver 192.168.111.1
It looks like what is happening is that the local nameserver is being prepended before each existing nameserver line instead of just the first. I think this is because of https://github.com/openshift/machine-config-operator/commit/09fab1e853418bfd8624db0a617411603e7b6876
Version-Release number of MCO (Machine Config Operator) (if applicable): NA
Platform (AWS, VSphere, Metal, etc.): On-prem
Are you certain that the root cause of the issue being reported is the MCO (Machine Config Operator)?
(Y/N/Not sure): Yes, it's the prepender script that lives in MCO.
How reproducible: Always.
Did you catch this issue by running a Jenkins job? If yes, please list:
1. Jenkins job:
Steps to Reproduce:
1. Deploy cluster
2. Modify DNS settings to have multiple servers. I used kubernetes-nmstate to add a DNS server.
Actual results: Duplicate local nameserver entries.
Expected results: Only one local nameserver entry.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.