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

Services should serve multiport endpoints from pods #12184

Closed
0xmichalis opened this issue Dec 8, 2016 · 4 comments
Closed

Services should serve multiport endpoints from pods #12184

0xmichalis opened this issue Dec 8, 2016 · 4 comments
Assignees
Labels
area/tests 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/P2

Comments

@0xmichalis
Copy link
Contributor

/data/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/service.go:229
Dec  7 14:02:09.935: Timed out waiting for service multi-endpoint-test in namespace e2e-tests-services-pvgkc to expose endpoints map[pod1:[100]] (1m0s elapsed)
/data/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/service.go:1286

https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/9306/

@derekwaynecarr
Copy link
Member

see related upstream flake:
kubernetes/kubernetes#29831

this has existed since 1.4, and its frequency as reported upstream has not been enormous.

@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 9, 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 12, 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
area/tests 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/P2
Projects
None yet
Development

No branches or pull requests

5 participants