Bug 1459630
Summary: | OpenShift Dedicated outgoing pod DNS requests failing | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Eric Jones <erjones> |
Component: | Networking | Assignee: | Ben Bennett <bbennett> |
Status: | CLOSED NOTABUG | QA Contact: | Meng Bo <bmeng> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.4.1 | CC: | aos-bugs, erjones |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-06-09 18:12:02 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
Eric Jones
2017-06-07 15:51:48 UTC
Is it failing from the node, or from pods? Can I get /etc/resolv.conf and /etc/nsswitch.conf, and the output from: dig retail-locator-prod.cx4w7ilrr6c0.us-east-1.rds.amazonaws.com Ok. This was caused by the cron job we put in to clear the ARP cache every minute. That was causing simple curl commands from a node to a remote pod to take > 40s after the cache was flushed. That's weird and is still merits investigation, and that will happen on https://bugzilla.redhat.com/show_bug.cgi?id=1451854 where we are looking at the other ARP issues. However, given that this was due to the cronjob, and that has now been removed, I'm closing this. |