|Summary:||controller manager spam about PVCs|
|Product:||OpenShift Container Platform||Reporter:||Eric Paris <eparis>|
|Component:||Node||Assignee:||Avesh Agarwal <avagarwa>|
|Status:||CLOSED ERRATA||QA Contact:||weiwei jiang <wjiang>|
|Version:||3.6.0||CC:||aos-bugs, decarr, dma, jeder, jokerman, mawong, mmccomas, sjenning, xtian|
|Fixed In Version:||Doc Type:||Bug Fix|
This fix prevents unnecessary logging of a harmless error from a pvc related scheduler predicate.
|Last Closed:||2017-11-28 22:05:56 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Eric Paris 2017-07-26 21:44:22 UTC
SO. MUCH. SPAM. We run as V(2). Please either make this meaningful to an admin, remove it, or move it to a higher level. oc v3.6.170 predicates.go:234] Unable to look up PVC info for dupa1/database, assuming PVC matches predicate when counting limits: persistentvolumeclaim "database" not found
Comment 1 Derek Carr 2017-07-27 14:20:07 UTC
scheduler log spam.
Comment 2 Derek Carr 2017-08-19 03:05:11 UTC
Avesh, any chance we can get a PR opened for this by 8/21 so it can make 3.6.1?
Comment 3 Avesh Agarwal 2017-08-22 16:01:28 UTC
(In reply to Derek Carr from comment #2) > Avesh, any chance we can get a PR opened for this by 8/21 so it can make > 3.6.1? These errors are not returned as these are non-harmful errors. These errors are currently rate limited (not aggregated) in apimachinery/pkg/util/runtime/runtime.go. I think moving these to glog level 3 or beyond seems to be the only option to suppress these errors. Aggregation by returning these errors along with real errors seems hacky right now.
Comment 4 Jeremy Eder 2017-09-05 00:49:23 UTC
Aggregated across the 16 master nodes in the free and pro tiers, this log message is written over 1.2 million times in the last 24 hours (Sept 1). Here are the top-talkers: File and Line Lines Logged in 24 hours -------------------------------------------------------- predicates.go line 234 1282755 writers.go line 119 4035 status.go line 62 2805 factory.go line 641 2406 buildconfig_controller.go line 143 4587 proxier.go line 1320 727
Comment 5 Jeremy Eder 2017-09-05 00:49:40 UTC
*** Bug 1487603 has been marked as a duplicate of this bug. ***
Comment 6 Avesh Agarwal 2017-09-05 16:41:37 UTC
There is a PR to kube upstream for this by Matthew Wong@redhat: https://github.com/kubernetes/kubernetes/pull/48226.
Comment 13 DeShuai Ma 2017-09-30 09:49:03 UTC
Test on openshift v3.7.0-0.131.0, while the pod is running, pod's PVC is deleted or pods' PVC's PV is deleted. I don't seem the spam log, verify the bug.
Comment 16 errata-xmlrpc 2017-11-28 22:05:56 UTC
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