Bug 1825909
| Summary: | Nameserver limits were exceeded, some nameservers have been omitted | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Yossi Boaron <yboaron> | |
| Component: | Installer | Assignee: | Yossi Boaron <yboaron> | |
| Installer sub component: | OpenShift on Bare Metal IPI | QA Contact: | Nataf Sharabi <nsharabi> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | low | |||
| Priority: | medium | CC: | aos-bugs, dsanzmor, jmalde, kfryklun, llowinge, m.andre, mchoma, ppitonak, pprinett, scuppett | |
| Version: | 4.4 | Keywords: | Triaged | |
| Target Milestone: | --- | |||
| Target Release: | 4.5.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause: In baremetal platform, in order to support nodes DNS resolve we point node's /etc/resolv.conf to local instance of infra coredns by prepending the node's control plane IP address to node's /etc/resolv.conf.
Consequence: When the hosts already had 3 nameservers in their /etc/resolv.conf file, pods generate alerts about "nameserver limits were exceeded"
Fix: Only leave the first 3 nameservers in the generated /etc/resolv.conf
Result: Pods no longer complain about "nameserver limits were exceeded"
|
Story Points: | --- | |
| Clone Of: | 1791008 | |||
| : | 1829752 (view as bug list) | Environment: | ||
| Last Closed: | 2020-07-13 17:29:07 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: | 1791008 | |||
| Bug Blocks: | 1829752 | |||
|
Comment 1
Stephen Benjamin
2020-04-21 11:58:06 UTC
The OCP on OSP team hit this bug, since baremetal-ipi use the same design for handling DNS (including setting nameserver list in /etc/resolv.conf) - I decided to clone this bug. I think we should set target release for this bug to 4.5; if we'll decide to backport it, we should open/clone new bugs with the relevant target release. Got it, thanks! [kni@provisionhost-0-0 ~]$ oc version Client Version: 4.5.0-0.nightly-2020-05-06-003431 Server Version: 4.5.0-0.nightly-2020-05-06-003431 Kubernetes Version: v1.18.0-rc.1 All of the following came with zero results: oc get events --all-namespaces | grep omitted oc get events --all-namespaces | grep "Nameserver limits were exceeded" Verified. 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-2020:2409 |