Description of problem: Coredns infra pod should forward requests to servers list that retrieved from /etc/resolv.conf file. If /etc/resolv.conf file is changed, the change doesn't reflect coredns Corefile. Version-Release number of selected component (if applicable): How reproducible: Change /etc/resolv.conf servers list Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Antoni, could you or one of the baremetal folks take a look at this? As this has to do with templates (baremetal-coredns.yaml) in the MCO repo, but we don't actually own them...
Talked to Brad and he suggested I move this to KNI-Deployment.
PR for 4.5 (this BZ) was incorrectly titled w/o the correct "Bug ######:" prefix therefore the bot didn't attach the PR, but it's here https://github.com/openshift/machine-config-operator/pull/1501
Verified on 4.5.0-0.nightly-2020-03-18-115438 [core@master-0 ~]$ cat /var/run/NetworkManager/resolv.conf # Generated by NetworkManager nameserver fe80::5054:ff:fe4f:98a6%enp5s0 nameserver fd2e:6f44:5dd8:c956::1 [core@master-0 ~]$ cat /etc/coredns/Corefile | grep forward forward . fe80::5054:ff:fe4f:98a6%enp5s0 fd2e:6f44:5dd8:c956::1 # added 192.168.123.1 to resolv.conf and after few seconds corefile got updated [core@master-0 ~]$ cat /etc/coredns/Corefile | grep forward forward . fe80::5054:ff:fe4f:98a6%enp5s0 fd2e:6f44:5dd8:c956::1 forward . fe80::5054:ff:fe4f:98a6%enp5s0 fd2e:6f44:5dd8:c956::1 192.168.123.1
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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409