Skip to content

Flake: test/end-to-end/core.sh:88 #14403

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

Closed
tnozicka opened this issue May 30, 2017 · 7 comments
Closed

Flake: test/end-to-end/core.sh:88 #14403

tnozicka opened this issue May 30, 2017 · 7 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

@tnozicka
Copy link
Contributor

https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/1830/

Stacktrace

=== BEGIN TEST CASE ===
test/end-to-end/core.sh:88: executing 'oc rollout status dc/ipfailover' expecting success
FAILURE after 41.322s: test/end-to-end/core.sh:88: executing 'oc rollout status dc/ipfailover' expecting success: the command returned the wrong error code
Standard output from the command:
Waiting for rollout to finish: 0 out of 1 new replicas have been updated...

Standard error from the command:
error: replication controller "ipfailover-1" has failed progressing
=== END TEST CASE ===
@tnozicka tnozicka added kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1 labels May 30, 2017
@mfojtik
Copy link
Contributor

mfojtik commented May 30, 2017

@knobunc @smarterclayton i swear I saw this flake before but can't find the issue.

@knobunc
Copy link
Contributor

knobunc commented Jun 9, 2017

I'm not really sure why this is a networking issue...

@smarterclayton
Copy link
Contributor

Is this the "pod doesn't get network connectivity so it can't run"?

@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 15, 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 18, 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

8 participants