Bug 1754127 - kubernetes.default.svc fails to resolve after updating from RHEL7.6 to RHEL 7.7
Summary: kubernetes.default.svc fails to resolve after updating from RHEL7.6 to RHEL 7.7
Keywords:
Status: CLOSED DUPLICATE of bug 1743572
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.11.0
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
: 3.11.z
Assignee: Dan Mace
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-20 22:45 UTC by Taneem Ibrahim
Modified: 2022-08-04 22:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-24 19:02:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Taneem Ibrahim 2019-09-20 22:45:08 UTC
Description of problem:

Customer is having issues with DNS after patching to RHEL 7.7. We have the tuned update applied [https://bugzilla.redhat.com/show_bug.cgi?id=1739563].

why does host kubernetes.default.svc resolve successfully for a node in RHEL 7.6 but not in RHEL 7.7?

In RHEL 7.6:

host kubernetes.default.svc
kubernetes.default.svc.cluster.local has address XX.XX.XX.XX

In RHEL 7.7:

host kubernetes.default.svc
Host kubernetes.default.svc not found: 3(NXDOMAIN)

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

RHEL 7.7
OpenShift 3.11.59

How reproducible:

Always (in customer environment)

Steps to Reproduce:

1. Upgrade to RHEL 7.7 with OCP v3.11.59 
2. Run host kubernetes.default.svc
3. Fails to resolve

Actual results:

Host kubernetes.default.svc not found: 3(NXDOMAIN)

Expected results:

kubernetes.default.svc.cluster.local has address XX.XX.XX.XX

Additional info:

Comment 5 Taneem Ibrahim 2019-09-24 19:02:42 UTC
Found the root cause :

https://bugzilla.redhat.com/show_bug.cgi?id=1743572

*** This bug has been marked as a duplicate of bug 1743572 ***


Note You need to log in before you can comment on or make changes to this bug.