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

net/http: TLS handshake timeout deployment flake #14109

Closed
jim-minter opened this issue May 9, 2017 · 1 comment
Closed

net/http: TLS handshake timeout deployment flake #14109

jim-minter opened this issue May 9, 2017 · 1 comment
Assignees
Labels
component/apps kind/test-flake Categorizes issue or PR as related to test flakes. priority/P2

Comments

@jim-minter
Copy link
Contributor

https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/1250/consoleFull#-169259343956c60d7be4b02b88ae8c268b

[Fail] deploymentconfigs with revision history limits [Conformance] [It] should never persist more old deployments than acceptable after being observed by the controller

In this case, the deployer pod failed to speak to the master API:

May  9 07:44:55.904: INFO: --- pod history-limit-8-deploy logs
2017-05-09T11:40:04.577121000Z error: couldn't get deployment history-limit-8: Get https://172.30.0.1:443/api/v1/namespaces/extended-test-cli-deployment-3zn4t-5kkzz/replicationcontrollers/history-limit-8: net/http: TLS handshake timeout---

Although this looks a bit like #11114 I'm opening a new issue because I didn't see any obvious specific evidence of etcd/credentials issues here.

@tnozicka
Copy link
Contributor

So this was either infra failing or API server going down in exactly that moment, but I am inclined to blame infra. In both cases the hasn't been an occurrence of this for a long time and I see no action to be taken for fixing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/apps kind/test-flake Categorizes issue or PR as related to test flakes. priority/P2
Projects
None yet
Development

No branches or pull requests

4 participants