Merge pull request #44115 from derekwaynecarr/reduce-logging-severity

Automatic merge from submit-queue (batch tested with PRs 47083, 44115, 46881, 47082, 46577) Scheduler should not log an error when there is no fit **What this PR does / why we need it**: The scheduler should not log an error when it is unable to find a fit for a pod as it's an expected situation when resources are unavailable on the cluster that satisfy the pods requirements.

Merge pull request #44115 from derekwaynecarr/reduce-logging-severity
3fae07c5 · Kubernetes Submit Queue · GitHub · 66041a94 · 25564b40 · 3fae07c5
Commit 3fae07c5 authored Jun 06, 2017 by Kubernetes Submit Queue Committed by GitHub Jun 06, 2017
Hide whitespace changes
Inline Side-by-side

Showing with 5 additions and 1 deletion

factory.go plugin/pkg/scheduler/factory/factory.go +5 -1

No files found.
--- a/plugin/pkg/scheduler/factory/factory.go
+++ b/plugin/pkg/scheduler/factory/factory.go
@@ -653,7 +653,11 @@ func (factory *ConfigFactory) MakeDefaultErrorFunc(backoff *util.PodBackoff, pod
 		if err == core.ErrNoNodesAvailable {
 			glog.V(4).Infof("Unable to schedule %v %v: no nodes are registered to the cluster; waiting", pod.Namespace, pod.Name)
 		} else {
-			glog.Errorf("Error scheduling %v %v: %v; retrying", pod.Namespace, pod.Name, err)
+			if _, ok := err.(*core.FitError); ok {
+				glog.V(4).Infof("Unable to schedule %v %v: no fit: %v; waiting", pod.Namespace, pod.Name, err)
+			} else {
+				glog.Errorf("Error scheduling %v %v: %v; retrying", pod.Namespace, pod.Name, err)
+			}
 		}
 		backoff.Gc()
 		// Retry asynchronously.