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

Flake TestRouterDuplications #13708

Closed
soltysh opened this issue Apr 11, 2017 · 5 comments
Closed

Flake TestRouterDuplications #13708

soltysh opened this issue Apr 11, 2017 · 5 comments
Assignees
Labels
component/networking kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P1

Comments

@soltysh
Copy link
Member

soltysh commented Apr 11, 2017

Seen in https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_integration/989/consoleFull

--- FAIL: TestRouterDuplications (2.35s)
	router_test.go:837: Unable to validate both routes in a duplicate service scenario.  Resp 1: %!s(<nil>), Resp 2: Get http://0.0.0.0: read tcp 127.0.0.1:33922->127.0.0.1:80: read: connection reset by peer
@soltysh soltysh added component/networking kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1 labels Apr 11, 2017
@detiber
Copy link

detiber commented Jun 28, 2017

I'm seeing this failure as well as others on ppc64le and aarch64 tests with golang-1.8. I think the issue is caused by only testing the api server /healthz endpoint instead of /healthz/ready. I suspect that the issue is more prevalent in my environment because of peculiarities of the environments I'm running on.

I'm testing a fix for this currently.

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 22, 2018
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 24, 2018
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/networking kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P1
Projects
None yet
Development

No branches or pull requests

6 participants