Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1570400 - [3.7] DNS to local node vs. static egress IP
[3.7] DNS to local node vs. static egress IP
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking (Show other bugs)
3.7.1
x86_64 Linux
medium Severity medium
: ---
: 3.7.z
Assigned To: Dan Winship
Meng Bo
:
Depends On: 1557924
Blocks:
  Show dependency treegraph
 
Reported: 2018-04-22 11:01 EDT by Dan Winship
Modified: 2018-05-17 23:55 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: When using per-namespace static egress IPs, all external traffic is routed through the egress IP. "External" means all traffic which isn't directed to another pod, and so includes traffic from the pod to the pod's node. Consequence: When pods are told to use the node's IP address for DNS, and the pod is using a static egress IP, then DNS traffic will be routed to the egress node first, and then back to the original node, which might be configured to not accept DNS requests from other hosts, causing the pod to be unable to resolve DNS. Fix: pod-to-node DNS requests now bypass the egress IP and go directly to the node Result: DNS works
Story Points: ---
Clone Of: 1570398
Environment:
Last Closed: 2018-05-17 23:54:45 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Github ose/pull/1220 None None None 2018-04-22 11:03 EDT
Red Hat Product Errata RHBA-2018:1576 None None None 2018-05-17 23:55 EDT

  None (edit)
Comment 1 Dan Winship 2018-04-22 11:03:34 EDT
https://github.com/openshift/ose/pull/1220
Comment 3 Meng Bo 2018-05-11 03:14:44 EDT
Tested on 3.7.46, with same step in https://bugzilla.redhat.com/show_bug.cgi?id=1570398#c5

The issue had been fixed.
Comment 6 errata-xmlrpc 2018-05-17 23:54:45 EDT
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-2018:1576

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