Bug 1696394
Summary: | [3.10] Pod /etc/resolv.conf populated with incorrect nameserver possibly with an IP read from the wrong interface | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Ravi Sankar <rpenta> |
Component: | Networking | Assignee: | Dan Mace <dmace> |
Networking sub component: | router | QA Contact: | Hongan Li <hongli> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | high | CC: | aos-bugs, byron.collins, dapark, dcaldwel, dmace, dmoessne, fgrosjea, hongli, jinjli, jokerman, mfojtik, mmccomas, openshift-bugs-escalate, rbost, rekhan |
Version: | 3.10.0 | ||
Target Milestone: | --- | ||
Target Release: | 3.10.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: Undesired dns IP is selected by openshift service in case of multiple NICs.
Consequence: DNS requests failed to work from pod.
Fix: Create sane defaults for DNS IP and it follows the similar pattern used by kubelet to fetch routable node IP.
Result: DNS requests from pod works as expected.
|
Story Points: | --- |
Clone Of: | 1680059 | Environment: | |
Last Closed: | 2019-06-27 16:41:12 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1680059 | ||
Bug Blocks: |
Comment 1
Ravi Sankar
2019-04-04 19:15:31 UTC
@daniel https://coreos.slack.com/archives/CB95J6R4N/p1557166721063800 QE is already testing the changes and the bug will be automatically moved to QA once the bug is attached to advisory. verified with atomic-openshift-3.10.149-1.git.0.05de590.el7 and issue has been fixed. 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-2019:1607 *** Bug 1705166 has been marked as a duplicate of this bug. *** |