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] Daemon set [Serial] Should adopt or recreate existing pods when creating a RollingUpdate DaemonSet with matching or mismatching templateGeneration #14129

Closed
bparees opened this issue May 10, 2017 · 9 comments
Assignees
Labels
component/kubernetes 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 May 10, 2017

/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/daemon_set.go:401
Expected
    <int>: 0
to be >
    <int>: 0
/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/daemon_set.go:445

https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/1312/testReport/junit/(root)/Extended/_k8s_io__Daemon_set__Serial__Should_adopt_or_recreate_existing_pods_when_creating_a_RollingUpdate_DaemonSet_with_matching_or_mismatching_templateGeneration/

@bparees
Copy link
Contributor Author

bparees commented May 10, 2017

(and i have no idea why it failed when it expected "0" to be "0")

@bparees
Copy link
Contributor Author

bparees commented May 19, 2017

@derekwaynecarr
Copy link
Member

upstream flake:
kubernetes/kubernetes#42908

claimed fix:
kubernetes/kubernetes#42925

the referenced fix is in origin, so it must be upset for another reason.

@derekwaynecarr
Copy link
Member

@marun -- can you help track this down further?

@smarterclayton
Copy link
Contributor

I think this is also in part kubernetes/kubernetes#50586

@marun marun removed their assignment Nov 14, 2017
@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 25, 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 27, 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/kubernetes 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

7 participants