-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
[k8s.io] MetricsGrabber should grab all metrics from a Kubelet. {Kubernetes e2e suite} #37543
Comments
@vishh @dchen1107 - it seems that we can't establish proxy connection to the GCI Node. |
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-etcd3/2309/ Failed: [k8s.io] MetricsGrabber should grab all metrics from a Kubelet. {Kubernetes e2e suite}
|
It seems that api-server proxy wasn't able to connect to this Node, but there are no logs, so it's impossible to know what happened. |
Looking at recent failures it seems that it's still related to Master-Node connectivity, but not necessarily #36143. Adding retry might help (or not - hard to tell), but it'd shadow real problem, which is not working node proxy (IIUC). @kubernetes/sig-api-machinery-misc |
@cmluciano @gmarek should this flake block the 1.6 release? |
@gmarek Should this have a label for the apimachinery SIG as well |
This is clearly just flaking. Making as non-release-blocker. |
(@gmarek is on vacation) |
This looks to be talking directly to kubelets? If so it doesn't go through any api machinery code. |
Changing to @kubernetes/sig-node-bugs |
It only flaked once in the past two weeks, and that was because kubelet panicked. The root cause was already fixed by #42927. Closing the issue. |
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce-etcd3/661/
Failed: [k8s.io] MetricsGrabber should grab all metrics from a Kubelet. {Kubernetes e2e suite}
Previous issues for this test: #27295 #35385 #36126 #37452
The text was updated successfully, but these errors were encountered: