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] Kubectl client [k8s.io] Guestbook application should create and stop a working application [Conformance] #33617

Closed
bprashanth opened this issue Sep 27, 2016 · 13 comments
Assignees
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.

Comments

@bprashanth
Copy link
Contributor

It hits the apiserver proxy on GKE, which fails with:

'http://10.244.0.6:80/guestbook.php?cmd=get&key=messages&value='") has prevented the request from succeeding (get services frontend), response: 
Sep 27 15:36:19.157: INFO: Failed to get response from guestbook. err: an error on the server ("Error: 'No SSH tunnels currently open. Were the targets able to accept an ssh-key for user \"gke-4b1917fb2f43ed3cbed7\"?'\nTrying to reach: 'http://10.244.0.6:80/guestbook.php?cmd=get&key=messages&value='") has prevented the request from succeeding (get services frontend), response: 
Sep 27 15:36:24.162: INFO: Failed to get response from guestbook. err: an error on the server ("Error: 'No SSH tunnels currently open. Were the targets able to accept an ssh-key for user \"gke-4b1917fb2f43ed3cbed7\"?'\nTrying to reach: 'http://10.244.0.6:80/guestbook.php?cmd=get&key=messages&value='") has prevented the request from succeeding (get services frontend), response: 
Sep 27 15:36:29.166: INFO: Failed to get response from guestbook. err: an error on the server ("Error: 'No SSH tunnels currently open. Were the targets able to accept an ssh-key for user \"gke-4b1917fb2f43ed3cbed7\"?'\nTrying to reach: 'http://10.244.0.6:80/guestbook.php?cmd=get&key=messages&value='") has prevented the request from succeeding (get services frontend), response: 
Sep 27 15:36:34.173: INFO: Failed to get response from guestbook. err: an error on the server ("Error: 'No SSH tunnels currently open. Were the targets able to accept an ssh-key for user \"gke-4b1917fb2f43ed3cbed7\"?'\nTrying to reach: 'http://10.244.1.6:80/guestbook.php?cmd=get&key=messages&value='") has prevented the request from succeeding (get services frontend), response: 
Sep 27 15:36:39.179: INFO: Failed to get response from guestbook. err: an error on the server ("Error: 'No SSH tunnels currently open. Were the targets able to accept an ssh-key for user \"gke-4b1917fb2f43ed3cbed7\"?'\nTrying to reach: 'http://10.244.1.6:80/guestbook.php?cmd=get&key=messages&value='") has prevented the request from succeeding (get services frontend), response: 
Sep 27 15:36:44.184: INFO: Failed to get response from guestbook. err: an error on the server ("Error: 'No SSH tunnels currently open. Were the targets able to accept an ssh-key for user \"gke-4b1917fb2f43ed3cbed7\"?'\nTrying to reach: 'http://10.244.1.6:80/guestbook.php?cmd=get&key=messages&value='") has prevented the request from succeeding (get services frontend), response: 

We could just not hit the apiserver proxy but create a service of type=lb instead. That is actually more representative of real world app usage, but the proxy issue seems specific to gke and ssh-tunnels.

@bprashanth bprashanth added kind/flake Categorizes issue or PR as related to a flaky test. team/gke labels Sep 27, 2016
@bprashanth
Copy link
Contributor Author

@kubernetes/sig-testing fyi recent spike in failures on pr builders from this

@gmarek gmarek added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Sep 28, 2016
@gmarek
Copy link
Contributor

gmarek commented Sep 28, 2016

@roberthbailey can you reassign?

@sttts
Copy link
Contributor

sttts commented Sep 28, 2016

Saw this now on three different PRs independently with the gke smoke test, all this morning. Feels like a P0.

@gmarek gmarek added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Sep 28, 2016
@gmarek
Copy link
Contributor

gmarek commented Sep 28, 2016

@sttts I thought I was the only one;) If it happens multiple times a day it's certainly a P0.

@roberthbailey
Copy link
Contributor

@cjcullen would be a good person to dig into this.

@k8s-github-robot
Copy link

[FLAKE-PING] @cjcullen

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

1 similar comment
@k8s-github-robot
Copy link

[FLAKE-PING] @cjcullen

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

@k8s-github-robot
Copy link

[FLAKE-PING] @cjcullen

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

@gmarek
Copy link
Contributor

gmarek commented Oct 5, 2016

Ping @cjcullen

@cjcullen
Copy link
Member

cjcullen commented Oct 5, 2016

I'm not sure how to debug this. I don't see any e2e failures of this test in testgrid in the last 2 weeks. Has it only happened in the PR builder?

@spxtr
Copy link
Contributor

spxtr commented Oct 5, 2016

Dupe of kubernetes/test-infra#725

@spxtr spxtr closed this as completed Oct 5, 2016
@cjcullen
Copy link
Member

cjcullen commented Oct 5, 2016

Thanks Joe!

@bprashanth
Copy link
Contributor Author

I usually look at one of the linked in prs, ctrl+f this bug number (33617) and go up to the last failure eg #31136 (comment)

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/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Development

No branches or pull requests

7 participants