Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1839121

Summary:	Containers are not using the new DNS Servers as configured
Product:	OpenShift Container Platform	Reporter:	Gabriel Stein <gferrazs>
Component:	Networking	Assignee:	Miheer Salunke <misalunk>
Networking sub component:	DNS	QA Contact:	Hongan Li <hongli>
Status:	CLOSED WONTFIX	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	aos-bugs, bbennett
Version:	3.11.0
Target Milestone:	---
Target Release:	3.11.z
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-07 20:53:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gabriel Stein 2020-05-22 14:16:18 UTC

Description of problem:

After changing the DNS configuration from the OpenShift Container Platform Cluster, the resolv.conf are missing in some containers like SDN, OVS, Prometheus Node Exporter, and the reverse DNS is pointing to the old DNS Server.

The only way to fix that now was to restart the docker daemon and then the containers would be using the right configuration.

Version-Release number of selected component (if applicable):

3.11.146

How reproducible:

Steps to Reproduce:
1. Change the DNS Server configuration on dnsmasq upstream script
2. Check the DNS reverse resolution, e.g. with nslookup, from a route ip
3. It will be wrong, with the old dns server
4. Restart docker daemon and the resolution will work

Actual results:

- After changing a DNS Server configuration on the cluster, just restarting docker daemon it will delete the old dns server configuration on the cluster

Expected results:

- Change the DNS Server configuration ip from a.b.c.d to e.f.g.h. and all dns resolution working, on the fly


Additional info:

- Followed all DNS Troubleshooting steps, nothing showed a possible error on the configuration
- Read and executed the steps from the solution on 'how to change the DNS Server Configuration on the OpenShift Container Platform', does not fix the issue

Comment 1 Andrew McDermott 2020-05-22 16:06:41 UTC

I’m adding UpcomingSprint, because I was occupied by fixing bugs with
higher priority/severity, developing new features with higher
priority, or developing new features to improve stability at a macro
level. I will revisit this bug next sprint.

Comment 2 Andrew McDermott 2020-06-17 09:28:33 UTC

I’m adding UpcomingSprint, because I was occupied by fixing bugs with
higher priority/severity, developing new features with higher
priority, or developing new features to improve stability at a macro
level. I will revisit this bug next sprint.

Comment 3 Andrew McDermott 2020-07-09 12:01:33 UTC

I’m adding UpcomingSprint, because I was occupied by fixing bugs with
higher priority/severity, developing new features with higher
priority, or developing new features to improve stability at a macro
level. I will revisit this bug next sprint.

Comment 4 Andrew McDermott 2020-07-30 09:56:27 UTC

I’m adding UpcomingSprint, because I was occupied by fixing bugs with
higher priority/severity, developing new features with higher
priority, or developing new features to improve stability at a macro
level. I will revisit this bug next sprint.

Comment 5 Andrew McDermott 2020-09-10 11:42:20 UTC

I’m adding UpcomingSprint, because I was occupied by fixing bugs with
higher priority/severity, developing new features with higher
priority, or developing new features to improve stability at a macro
level. I will revisit this bug next sprint.

Comment 6 Andrew McDermott 2020-09-10 11:42:31 UTC

I’m adding UpcomingSprint, because I was occupied by fixing bugs with
higher priority/severity, developing new features with higher
priority, or developing new features to improve stability at a macro
level. I will revisit this bug next sprint.

Comment 7 Andrew McDermott 2020-09-10 11:42:38 UTC

I’m adding UpcomingSprint, because I was occupied by fixing bugs with
higher priority/severity, developing new features with higher
priority, or developing new features to improve stability at a macro
level. I will revisit this bug next sprint.

Comment 8 Andrew McDermott 2020-10-02 16:06:04 UTC

Bumping the priority and Tagging with UpcomingSprint while investigation is either ongoing or
pending. Will be considered for earlier release versions when
diagnosed and resolved.

Comment 9 Stephen Cuppett 2020-10-07 20:53:31 UTC

Thank you for continuing to use Red Hat OpenShift.  As part of a wider bug review, this bug has been evaluated and we have determined that at this time we do not plan to progress it.  As such, we will be closing this bug.  If you have need for continued assistance on this issue, please reopen the bug with additional context on why it needs to be reconsidered.