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.
predicates.go:234] Unable to look up PVC info for dupa1/database, assuming PVC matches predicate when counting limits: persistentvolumeclaim "database" not found
scheduler log spam.
Avesh, any chance we can get a PR opened for this by 8/21 so it can make 3.6.1?
(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
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.
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
*** Bug 1487603 has been marked as a duplicate of this bug. ***
There is a PR to kube upstream for this by Matthew Wong@redhat: https://github.com/kubernetes/kubernetes/pull/48226.
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.
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.