-
Notifications
You must be signed in to change notification settings - Fork 38.8k
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] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite} #26210
Comments
We are treating http error code 0 with no body as an error: May be we should relax this a bit? Since this was the first one and since we got 200 OK in the next 19 calls. |
https://console.cloud.google.com/storage/kubernetes-jenkins/logs/kubernetes-e2e-gke/7696/ Failed: [k8s.io] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite}
|
https://console.cloud.google.com/storage/kubernetes-jenkins/logs/kubernetes-e2e-gke/7706/ Failed: [k8s.io] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite}
|
Isn't this a dup of #21484 ? |
@dims yes, it's the same issue. |
Transferred assignee and priority from de-duped bug. |
@sttts interesting, i haven't been able to find 501 or 503 in kubernetes-e2e-gke logs that i pulled this morning |
Thanks @krousey i am just learning the ropes. |
https://console.cloud.google.com/storage/kubernetes-jenkins/logs/kubernetes-e2e-gke/7766/ Failed: [k8s.io] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite}
|
https://console.cloud.google.com/storage/kubernetes-jenkins/logs/kubernetes-e2e-gke/7779/ Failed: [k8s.io] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite}
|
https://console.cloud.google.com/storage/kubernetes-jenkins/logs/kubernetes-e2e-gke/7782/ Failed: [k8s.io] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite}
|
https://console.cloud.google.com/storage/kubernetes-jenkins/logs/kubernetes-e2e-gke/7785/ Failed: [k8s.io] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite}
|
https://console.cloud.google.com/storage/kubernetes-jenkins/logs/kubernetes-e2e-gke/7813/ Failed: [k8s.io] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite}
|
With the error logging merged, we now know that there is nothing logged in the proxy-service pod:
|
@krousey @gmarek in #21484 (comment) it was mentioned that Google-internally there is access to the gke apiserver logs. Could one of you try to get access to the relevant part in one of the upper gke flakes? Recently it looks like this flake happens on gke only. Here is one for example: https://console.cloud.google.com/storage/browser/kubernetes-jenkins/logs/kubernetes-e2e-gke/7813 |
@krousey https://console.cloud.google.com/storage/kubernetes-jenkins/logs/kubernetes-e2e-gke/7336/ is the last in the old issue, 8 days old. |
https://console.cloud.google.com/storage/kubernetes-jenkins/logs/kubernetes-e2e-gke/7877/ Failed: [k8s.io] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite}
|
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke/7676/
Failed: [k8s.io] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite}
The text was updated successfully, but these errors were encountered: