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: TestRouterStatsPort #14962

Closed
smarterclayton opened this issue Jun 29, 2017 · 6 comments
Closed

flake: TestRouterStatsPort #14962

smarterclayton opened this issue Jun 29, 2017 · 6 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

@smarterclayton
Copy link
Contributor

https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/2818/testReport/junit/github/com_openshift_origin_test_integration%20%20%20/TestRouterStatsPort/

=== RUN   TestRouterStatsPort
I0629 11:57:46.687514    5727 router_http_server.go:422] Started, serving at 172.18.5.161:8080
I0629 11:57:46.687570    5727 router_http_server.go:422] Started, serving at 172.18.5.161:8888
I0629 11:57:46.687608    5727 router_http_server.go:422] Started, serving at 172.18.5.161:8889
I0629 11:57:46.688051    5727 router_http_server.go:454] Started, serving TLS at 172.18.5.161:8443
I0629 11:57:46.688602    5727 router_http_server.go:347] GET /
I0629 15:57:48.109938       1 template.go:246] Starting template router (v3.6.0-alpha.2+ff142c8-652)
I0629 15:57:48.139825       1 reflector.go:187] Starting reflector *api.Service (10m0s) from github.com/openshift/origin/pkg/router/template/service_lookup.go:31
I0629 15:57:48.140340       1 reflector.go:236] Listing and watching *api.Service from github.com/openshift/origin/pkg/router/template/service_lookup.go:31
I0629 15:57:48.153065       1 router.go:156] Creating a new template router, writing to /var/lib/haproxy/router
I0629 15:57:48.153172       1 router.go:350] Template router will coalesce reloads within 1 seconds of each other
I0629 15:57:48.153188       1 router.go:408] Writing default certificate to /var/lib/haproxy/router/certs
I0629 15:57:48.154633       1 router.go:214] Reading persisted state
I0629 15:57:48.154656       1 router.go:218] Committing state
I0629 15:57:48.154662       1 router.go:455] Writing the router state
I0629 15:57:48.155506       1 router.go:462] Writing the router config
I0629 15:57:48.156949       1 router.go:476] Reloading the router
I0629 15:57:48.307600       1 router.go:554] Router reloaded:
 - Checking http://localhost:80 ...
 - Health check ok : 0 retry attempt(s).
I0629 15:57:48.307976       1 router.go:240] Router is including routes in all namespaces
I0629 15:57:48.308021       1 reflector.go:187] Starting reflector *route.Route (10m0s) from github.com/openshift/origin/pkg/router/controller/factory/factory.go:88
I0629 15:57:48.308064       1 reflector.go:187] Starting reflector *api.Endpoints (10m0s) from github.com/openshift/origin/pkg/router/controller/factory/factory.go:95
I0629 15:57:48.308104       1 router_controller.go:70] Running router controller
I0629 15:57:48.308148       1 reaper.go:17] Launching reaper
I0629 15:57:48.308290       1 reflector.go:236] Listing and watching *route.Route from github.com/openshift/origin/pkg/router/controller/factory/factory.go:88
I0629 15:57:48.308390       1 reflector.go:236] Listing and watching *api.Endpoints from github.com/openshift/origin/pkg/router/controller/factory/factory.go:95
I0629 15:57:48.358622       1 router.go:435] Router state synchronized for the first time
I0629 15:57:48.358698       1 router.go:455] Writing the router state
I0629 15:57:48.360520       1 router.go:462] Writing the router config
I0629 15:57:48.362072       1 router.go:476] Reloading the router
I0629 15:57:48.386724       1 reaper.go:24] Signal received: child exited
I0629 15:57:48.386786       1 reaper.go:32] Reaped process with pid 31
I0629 11:57:48.590624    5727 router_http_server.go:294] Stopping listener at 172.18.5.161:8080
I0629 11:57:48.590655    5727 router_http_server.go:294] Stopping listener at 172.18.5.161:8888
I0629 11:57:48.590663    5727 router_http_server.go:294] Stopping listener at 172.18.5.161:8889
I0629 11:57:48.590671    5727 router_http_server.go:294] Stopping listener at 172.18.5.161:8443
--- FAIL: TestRouterStatsPort (1.90s)
	router_test.go:909: Unable to verify response: Get http://127.0.0.1:1936: dial tcp 0.0.0.0:1936: getsockopt: connection reset by peer
FAIL

By the time 909 runs, the router should be up. Which implies the router is not up, or not responding.

@smarterclayton smarterclayton added kind/test-flake Categorizes issue or PR as related to test flakes. component/networking labels Jun 29, 2017
@smarterclayton
Copy link
Contributor Author

@openshift/networking

@0xmichalis
Copy link
Contributor

=== RUN   TestRouterStatsPort
--- FAIL: TestRouterStatsPort (0.00s)
	router_test.go:884: Unable to start http server: listen tcp 172.18.0.75:8080: bind: address already in use

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/16139/test_pull_request_origin_end_to_end/2816/

@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 20, 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 22, 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