Red Hat Bugzilla – Bug 1473352
DNSSearchForming: Event Spam
Last modified: 2017-11-28 17:04:10 EST
+++ This bug was initially created as a clone of Bug #1471198 +++
I see lots of events like:
Pod Warning DNSSearchForming kubelet, ip-172-31-52-130.ec2.internal Found and omitted duplicated dns domain in host search line: 'cluster.local' during merging with cluster dns domains
1 pod is showing these events more than once per second.
Do we need these at all?
Should they be rate limited? (are they?)
Is this a misconfiguration of some sort?
--- Additional comment from Eric Paris on 2017-07-14 12:19:16 EDT ---
--- Additional comment from Derek Carr on 2017-07-17 10:37:52 EDT ---
--- Additional comment from Derek Carr on 2017-07-17 10:42:09 EDT ---
The rate limiting work we are carrying in Origin pending:
will make a major improvement to the rate of events in this case.
This event serves the cluster operator more than the cluster end-user.
Agree it should be removed.
--- Additional comment from Derek Carr on 2017-07-17 16:12:10 EDT ---
--- Additional comment from Derek Carr on 2017-07-19 15:28:09 EDT ---
Origin 3.6 PR:
--- Additional comment from Derek Carr on 2017-07-20 11:03:09 EDT ---
merged in 3.6.
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
No "DNSSearchForming" message in events
i'm still getting those spam dns messages.
$ 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.