Bug 1473352
Summary: | DNSSearchForming: Event Spam | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Eric Paris <eparis> |
Component: | Node | Assignee: | Seth Jennings <sjenning> |
Status: | CLOSED ERRATA | QA Contact: | DeShuai Ma <dma> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.6.0 | CC: | aos-bugs, decarr, dma, eparis, jokerman, jwendell, mmccomas, sjenning, wmeng, xtian |
Target Milestone: | --- | ||
Target Release: | 3.7.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: |
undefined
|
Story Points: | --- |
Clone Of: | 1471198 | Environment: | |
Last Closed: | 2017-11-28 22:04:10 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: | |||
Bug Depends On: | 1471198 | ||
Bug Blocks: |
Description
Eric Paris
2017-07-20 15:10:35 UTC
Eric, what is this clone tracking? This BZ is to track the fix on origin/master==3.7 all code has merged. Verified on openshift v3.7.0-0.127.0 kubernetes v1.7.0+80709908fd etcd 3.2.1 No "DNSSearchForming" message in events i'm still getting those spam dns messages. openshift v3.7.0-0.143.4 kubernetes v1.7.0+80709908fd $ oc get events LASTSEEN FIRSTSEEN COUNT NAME KIND SUBOBJECT TYPE REASON SOURCE MESSAGE 48m 48m 6 broker-amq-1-deploy Pod Warning DNSSearchForming kubelet, xxx Search Line limits were exceeded, some dns names have been omitted, the applied search line is: amq.svc.cluster.local svc.cluster.local cluster.local xyz zyx yxz John, the bug pertained only to warnings for duplicate dns entries. If the search list is truncated, you will still see an error, and that is by design. The number of domains is limited to 6 and the total length of the search string is limited to 255. 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/RHSA-2017:3188 |