[k8s.io] Daemon set [Serial] [It] Should update pod when spec was updated and update strategy is RollingUpdate

[eparis]

https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin/506/consoleFull#-169259343956c60d7be4b02b88ae8c268b

from #13847

[stevekuznetsov]

This error doesn't make a lot of sense...

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

[bparees]

fresh logs:
https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended_conformance_install_update/1075/testReport/junit/(root)/Extended/_k8s_io__Daemon_set__Serial__Should_update_pod_when_spec_was_updated_and_update_strategy_is_RollingUpdate/

[derekwaynecarr]

@jboyd01 - can you look at this test and see if you can make sense of what is going on.

in particular, why #13977 (comment) is not helpful output.

[0xmichalis]

Recurred at least twice today

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

[0xmichalis]

https://ci.openshift.redhat.com/jenkins/view/All/job/merge_pull_request_origin/1340/

[0xmichalis]

We should move serial tests to run as post-submits. Then we can use post-submit results from GCS buckets to block merges with the submit queue.

[bparees]

https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended_conformance_install_update/4538/

[openshift-bot]

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

[stevekuznetsov]

/shrug
/close

[stevekuznetsov]

Ignoring problems until they go away is ultimately the best approach...