From aeedcbfb5ee4f4e00f17acabe18cc4ff036f5edc Mon Sep 17 00:00:00 2001 From: NickrenREN Date: Fri, 17 Mar 2017 09:47:22 +0800 Subject: [PATCH] small change to ControlleeExpectations --- pkg/controller/controller_utils.go | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/pkg/controller/controller_utils.go b/pkg/controller/controller_utils.go index 48d963b7951..11888a40e08 100644 --- a/pkg/controller/controller_utils.go +++ b/pkg/controller/controller_utils.go @@ -155,6 +155,7 @@ func (r *ControllerExpectations) DeleteExpectations(controllerKey string) { func (r *ControllerExpectations) SatisfiedExpectations(controllerKey string) bool { if exp, exists, err := r.GetExpectations(controllerKey); exists { if exp.Fulfilled() { + glog.V(4).Infof("Controller expectations fulfilled %#v", exp) return true } else if exp.isExpired() { glog.V(4).Infof("Controller expectations expired %#v", exp) @@ -284,7 +285,7 @@ type UIDSet struct { // UIDTrackingControllerExpectations tracks the UID of the pods it deletes. // This cache is needed over plain old expectations to safely handle graceful // deletion. The desired behavior is to treat an update that sets the -// DeletionTimestamp on an object as a delete. To do so consistenly, one needs +// DeletionTimestamp on an object as a delete. To do so consistently, one needs // to remember the expected deletes so they aren't double counted. // TODO: Track creates as well (#22599) type UIDTrackingControllerExpectations struct {