From 6dd2ade762307246fe8335790f456bbf1e4e7ff6 Mon Sep 17 00:00:00 2001 From: Patrick Ohly Date: Tue, 20 Aug 2024 10:52:40 +0200 Subject: [PATCH] DRA scheduler: reduce log verbosity That a pod with no claims remains unschedulable on claim changes is a pretty normal case. It should only be logged when debugging. --- .../framework/plugins/dynamicresources/dynamicresources.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pkg/scheduler/framework/plugins/dynamicresources/dynamicresources.go b/pkg/scheduler/framework/plugins/dynamicresources/dynamicresources.go index 81589fbfa34..b5fad1b0f30 100644 --- a/pkg/scheduler/framework/plugins/dynamicresources/dynamicresources.go +++ b/pkg/scheduler/framework/plugins/dynamicresources/dynamicresources.go @@ -445,7 +445,7 @@ func (pl *dynamicResources) isSchedulableAfterClaimChange(logger klog.Logger, po // This is not an unexpected error: we know that // foreachPodResourceClaim only returns errors for "not // schedulable". - logger.V(4).Info("pod is not schedulable", "pod", klog.KObj(pod), "claim", klog.KObj(modifiedClaim), "reason", err.Error()) + logger.V(6).Info("pod is not schedulable after resource claim change", "pod", klog.KObj(pod), "claim", klog.KObj(modifiedClaim), "reason", err.Error()) return framework.QueueSkip, nil }