Skip to content
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] Port forwarding [k8s.io] With a server that expects a client request should support a client that connects, sends no data, and disconnects [Conformance] {Kubernetes e2e suite} #26955

Closed
k8s-github-robot opened this issue Jun 7, 2016 · 14 comments
Assignees
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@k8s-github-robot
Copy link

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke/8647/

Failed: [k8s.io] Port forwarding [k8s.io] With a server that expects a client request should support a client that connects, sends no data, and disconnects [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/portforward.go:196
Jun  7 04:01:33.404: Pod did not stop running: timed out waiting for the condition
@k8s-github-robot k8s-github-robot added the kind/flake Categorizes issue or PR as related to a flaky test. label Jun 7, 2016
@fejta fejta assigned sttts and ncdc Jun 7, 2016
@ncdc
Copy link
Member

ncdc commented Jun 7, 2016

So far I haven't found anything in the logs. The pfpod container starts, the e2e test receives all the data from it. At that time, the container should exit and the pod should be stopped. For some reason, either the container doesn't stop, or the kubelet doesn't see it stop. It's hard to tell which because the logs don't have enough information to make that determination.

k8s-github-robot pushed a commit that referenced this issue Jun 10, 2016
Automatic merge from submit-queue

Flake 26955: portforwarding e2e: print logs when pod doesn't terminate

For more insights why flake #26955 happens.
@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke/11769/

Failed: [k8s.io] Port forwarding [k8s.io] With a server that expects a client request should support a client that connects, sends no data, and disconnects [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/portforward.go:220
Jul 23 05:27:02.335: Failed to read from kubectl port-forward stdout: EOF

@k8s-github-robot k8s-github-robot added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Jul 23, 2016
@sttts
Copy link
Contributor

sttts commented Aug 26, 2016

Might be the same issue as #27680

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @ncdc @sttts

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @ncdc @sttts

This flaky-test issue would love to have more attention.

1 similar comment
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @ncdc @sttts

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @ncdc @sttts

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

k8s-github-robot commented Oct 2, 2016

Builds:
kubernetes-e2e-gce-etcd3 4092
kubernetes-e2e-gci-gce 666

Failed: [k8s.io] Port forwarding [k8s.io] With a server that expects a client request should support a client that connects, sends no data, and disconnects [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/portforward.go:220
Oct  2 10:57:55.636: Pod did not stop running: timed out waiting for the condition
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/portforward.go:210

@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/31234/kubernetes-pull-build-test-gci-e2e-gce/2299/

Failed: [k8s.io] Port forwarding [k8s.io] With a server that expects a client request should support a client that connects, sends no data, and disconnects [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/portforward.go:220
Oct 13 17:46:06.431: Pod did not stop running: timed out waiting for the condition
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/portforward.go:210

Happened on a presubmit run in #31234.

@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke-staging-parallel/10333/

Failed: [k8s.io] Port forwarding [k8s.io] With a server that expects a client request should support a client that connects, sends no data, and disconnects [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/portforward.go:217
Oct 21 03:08:16.408: Error retrieving logs: Get https://gke-jenkins-e2e-default-pool-5fd95d0b-o1ti:10250/containerLogs/e2e-tests-port-forwarding-ryje9/pfpod/portforwardtester: ssh: unexpected packet in response to channel open: <nil>

@calebamiles
Copy link
Contributor

Closing this issue as the corresponding test has been removed from test/test_owners.csv

cc: @ethernetdan, @kubernetes/kubernetes-release-managers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

5 participants