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

TestRouter flake #6635

Closed
0xmichalis opened this issue Jan 13, 2016 · 4 comments
Closed

TestRouter flake #6635

0xmichalis opened this issue Jan 13, 2016 · 4 comments
Assignees
Labels
kind/test-flake Categorizes issue or PR as related to test flakes. priority/P2

Comments

@0xmichalis
Copy link
Contributor

--- FAIL: TestRouter-4 (81.59s)
    router_test.go:359: TC reencrypt failed! Response body "<html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n" did not match expected "Hello Pod Secure!"
    router_test.go:359: TC reencrypt failed! Response body "<html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n" did not match expected "Hello Pod Secure!"
    router_test.go:359: TC reencrypt failed! Response body "<html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n" did not match expected "Hello Pod Secure!"
    router_test.go:359: TC reencrypt path failed! Response body "<html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n" did not match expected "Hello Pod Path Secure!"
    router_test.go:359: TC reencrypt path failed! Response body "<html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n" did not match expected "Hello Pod Path Secure!"
    router_test.go:359: TC reencrypt path failed! Response body "<html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n" did not match expected "Hello Pod Path Secure!"
Server message: accept tcp 172.18.7.38:8080: use of closed network connectionStopping listener at 172.18.7.38:8889
Stopping listener at 172.18.7.38:8443
Stopping listener at 172.18.7.38:8080
Stopping listener at 172.18.7.38:8888
Stopping listener at 172.18.7.38:8889
Stopping listener at 172.18.7.38:8443
FAIL

https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_origin/4615/console

@deads2k
Copy link
Contributor

deads2k commented Jan 13, 2016

Saw this again on #6637

@jwforres
Copy link
Member

@liggitt
Copy link
Contributor

liggitt commented Jan 13, 2016

Certs used in router tests expired today:

openssl x509 -in /tmp/cert.crt -text -noout
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number: 1 (0x1)
        Signature Algorithm: sha1WithRSAEncryption
        Issuer: C=US, ST=SC, L=Default City, O=Default Company Ltd, OU=Test CA, CN=www.exampleca.com/emailAddress=example@example.com
        Validity
            Not Before: Jan 12 14:19:41 2015 GMT
            Not After : Jan 12 14:19:41 2016 GMT

@liggitt
Copy link
Contributor

liggitt commented Jan 13, 2016

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

No branches or pull requests

6 participants