You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
d66f8f9 added that "plugins have to implement a QueueingHint for Pod/Update
event if the rejection from them could be resolved by updating unscheduled
Pods itself".
This applies to DRA because the name of a generated ResourceClaim must be
recorded in the pod status before the pod can be scheduled.
// Adding or updating a ResourceSlice might make a pod schedulable because new resources became available.
@@ -450,7 +452,10 @@ func (pl *dynamicResources) isSchedulableAfterClaimChange(logger klog.Logger, po
450
452
// This is not an unexpected error: we know that
451
453
// foreachPodResourceClaim only returns errors for "not
452
454
// schedulable".
453
-
logger.V(6).Info("pod is not schedulable after resource claim change", "pod", klog.KObj(pod), "claim", klog.KObj(modifiedClaim), "reason", err.Error())
455
+
ifloggerV:=logger.V(6); loggerV.Enabled() {
456
+
owner:=metav1.GetControllerOf(modifiedClaim)
457
+
loggerV.Info("pod is not schedulable after resource claim change", "pod", klog.KObj(pod), "claim", klog.KObj(modifiedClaim), "claimOwner", owner, "reason", err.Error())
458
+
}
454
459
returnframework.QueueSkip, nil
455
460
}
456
461
@@ -496,6 +501,33 @@ func (pl *dynamicResources) isSchedulableAfterClaimChange(logger klog.Logger, po
496
501
returnframework.Queue, nil
497
502
}
498
503
504
+
// isSchedulableAfterPodChange is invoked for update pod events reported by
505
+
// an informer. It checks whether that change adds the ResourceClaim(s) that the
0 commit comments