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.

Sign up for GitHub

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

Jump to bottom

services basic functionality should allow connections to another pod flake #11561

Closed
bparees opened this issue Oct 25, 2016 · 3 comments
Closed

services basic functionality should allow connections to another pod flake #11561

bparees opened this issue Oct 25, 2016 · 3 comments
Assignees
@knobunc
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/P2

Comments

@bparees
Copy link
Contributor

bparees commented Oct 25, 2016 

[Fail] [networking] services basic functionality [It] should allow connections to another pod on the same node via a service IP 
/data/src/github.com/openshift/origin/test/extended/networking/services.go:15

https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_networking/634/consoleFull
@bparees bparees added priority/P2 component/networking kind/test-flake Categorizes issue or PR as related to test flakes. labels Oct 25, 2016
@bparees bparees mentioned this issue Oct 25, 2016
Merged
@sjenning sjenning mentioned this issue Dec 9, 2016
Merged
@sttts sttts reopened this May 18, 2017
@sttts sttts mentioned this issue May 18, 2017
Merged
@jsafrane jsafrane mentioned this issue Jul 14, 2017
Merged
@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 11, 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 15, 2018
@bparees
Copy link
Contributor Author

bparees commented Mar 15, 2018

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@knobunc knobunc

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/P2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@sttts @smarterclayton @openshift-bot @bparees @knobunc @openshift-ci-robot