-
Notifications
You must be signed in to change notification settings - Fork 376
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error logs in agent: Unable to cancel request for *exec.roundTripper
#3497
Comments
Unable to cancel request for *exec.roundTripper
Unable to cancel request for *exec.roundTripper
cc @shettyg |
I did some research into this. This issue doesn't impact functionality and it was fixed in K8s v1.23: kubernetes/kubernetes#106014. The fix wasn't backported to earlier versions, so this issue will be resolved when we upgrade the client-go dependency in Antrea to v0.23 (we currently use v0.21.2). Given that there is an open feature request (#3540) which requires us to update to client-go v0.24, and given that updating the client-go version can be a bit of a pain, I suggest that we tackle both of these at the same time, when K8s v1.24 is GA at the end of the month. |
Thanks @antoninbas for the updates. Yes, you are right. We do use exec auth plugin for both kubelet and antrea-agent in GKE, so very likely to be the issue you described. |
Some notable changes since v0.21: * some apiserver library functions have a new signature and now take a context.Context instead of a stopCh * TopologyKeys was removed from ServiceSpec (this required a small cleanup in the third-party proxy code) * SelfLink field for K8s metadata (ListMeta / ObjectMeta) was deprecated * k8s.io/apimachinery/util/clock was deprecated and replaced with k8s.io/utils/clock * there was a small change in k8s.io/kubectl/pkg/proxy, which we use to implement "antctl proxy" Fixes antrea-io#3118 Fixes antrea-io#3497 Fixes antrea-io#3584 Signed-off-by: Antonin Bas <abas@vmware.com>
Some notable changes since v0.21: * some apiserver library functions have a new signature and now take a context.Context instead of a stopCh * TopologyKeys was removed from ServiceSpec (this required a small cleanup in the third-party proxy code) * SelfLink field for K8s metadata (ListMeta / ObjectMeta) was deprecated * k8s.io/apimachinery/util/clock was deprecated and replaced with k8s.io/utils/clock * there was a small change in k8s.io/kubectl/pkg/proxy, which we use to implement "antctl proxy" Fixes antrea-io#3118 Fixes antrea-io#3497 Fixes antrea-io#3584 Signed-off-by: Antonin Bas <abas@vmware.com>
Some notable changes since v0.21: * some apiserver library functions have a new signature and now take a context.Context instead of a stopCh * TopologyKeys was removed from ServiceSpec (this required a small cleanup in the third-party proxy code) * SelfLink field for K8s metadata (ListMeta / ObjectMeta) was deprecated * k8s.io/apimachinery/util/clock was deprecated and replaced with k8s.io/utils/clock * there was a small change in k8s.io/kubectl/pkg/proxy, which we use to implement "antctl proxy" Fixes antrea-io#3118 Fixes antrea-io#3497 Fixes antrea-io#3584 Signed-off-by: Antonin Bas <abas@vmware.com>
Some notable changes since v0.21: * some apiserver library functions have a new signature and now take a context.Context instead of a stopCh * TopologyKeys was removed from ServiceSpec (this required a small cleanup in the third-party proxy code) * SelfLink field for K8s metadata (ListMeta / ObjectMeta) was deprecated * k8s.io/apimachinery/util/clock was deprecated and replaced with k8s.io/utils/clock * there was a small change in k8s.io/kubectl/pkg/proxy, which we use to implement "antctl proxy" Fixes antrea-io#3118 Fixes antrea-io#3497 Fixes antrea-io#3584 Signed-off-by: Antonin Bas <abas@vmware.com>
Some notable changes since v0.21: * some apiserver library functions have a new signature and now take a context.Context instead of a stopCh * TopologyKeys was removed from ServiceSpec (this required a small cleanup in the third-party proxy code) * SelfLink field for K8s metadata (ListMeta / ObjectMeta) was deprecated * k8s.io/apimachinery/util/clock was deprecated and replaced with k8s.io/utils/clock * there was a small change in k8s.io/kubectl/pkg/proxy, which we use to implement "antctl proxy" * additional metrics were added to the apiserver, so we needed to regenerate the Prometheus metrics doc Fixes antrea-io#3118 Fixes antrea-io#3497 Fixes antrea-io#3584 Signed-off-by: Antonin Bas <abas@vmware.com>
* Upgrade K8s libraries to v0.24 Some notable changes since v0.21: * some apiserver library functions have a new signature and now take a context.Context instead of a stopCh * TopologyKeys was removed from ServiceSpec (this required a small cleanup in the third-party proxy code) * SelfLink field for K8s metadata (ListMeta / ObjectMeta) was deprecated * k8s.io/apimachinery/util/clock was deprecated and replaced with k8s.io/utils/clock * there was a small change in k8s.io/kubectl/pkg/proxy, which we use to implement "antctl proxy" * additional metrics were added to the apiserver, so we needed to regenerate the Prometheus metrics doc Fixes #3118 Fixes #3497 Fixes #3584 Signed-off-by: Antonin Bas <abas@vmware.com> * Fix logging after upgrading to K8s v1.24 klog flags are no longer added automatically to the command-line when running the InitLogs() function (from k8s.io/component-base/logs). The AddFlags() function must be called first, with the InitLogs() function being called after flags have been parsed. Note that K8s has deprecated klog flags as part of https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components. When these flags are used, a deprecation warning is displayed. We need to revisit how we do logging for Antrea components. Signed-off-by: Antonin Bas <abas@vmware.com>
Describe the bug
antrea-agent on windows (only observed in windows, but it should be platform independent) shows a lot of error logs saying
Unable to cancel request for *exec.roundTripper
. It's pretty annoying, though the functionality seems not impacted. The DEBUG logs are like the following.To Reproduce
Run the agent and check the log.
Expected
No error logs
Actual behavior
There are error logs.
Versions:
Please provide the following information:
kubectl version
). If your Kubernetes components have different versions, please provide the version for all of them. v1.22.4uname -r
). n/amodinfo openvswitch
for the Kubernetes Nodes. n/aThe text was updated successfully, but these errors were encountered: