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

Extended.[k8s.io] DNS should provide DNS for services [Conformance] #12264

Closed
bparees opened this issue Dec 14, 2016 · 5 comments
Closed

Extended.[k8s.io] DNS should provide DNS for services [Conformance] #12264

bparees opened this issue Dec 14, 2016 · 5 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/P1

Comments

@bparees
Copy link
Contributor

bparees commented Dec 14, 2016

/data/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/dns.go:400
Expected error:
    <*errors.errorString | 0xc8200f3600>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
not to have occurred
/data/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/dns.go:236

Seen in https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/9572/

@smarterclayton
Copy link
Contributor

I'd be surprised if this is not #11016

@bparees
Copy link
Contributor Author

bparees commented Mar 6, 2017

that may be but it's really annoying trying to track down appropriate flake issues when we don't actually have ones open that mention the specific test failure.

also to the extent to which #11016 can be mitigated by making test case changes, it should be, so the issue can be used for that also.

@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 13, 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/P1
Projects
None yet
Development

No branches or pull requests

5 participants