[k8s.io] StatefulSet [k8s.io][StatefulSetBasic] should implement legacy replacement when the update strategy is OnDelete

[mfojtik]

Seen here: https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/16324/test_pull_request_origin_extended_conformance_gce/7803/#-k8sio-statefulset-k8sio-basic-statefulset-functionality-statefulsetbasic-should-implement-legacy-replacement-when-the-update-strategy-is-ondelete

go run hack/e2e.go -v -test --test_args='--ginkgo.focus=\s\[k8s\.io\]\sStatefulSet\s\[k8s\.io\]\sBasic\sStatefulSet\sfunctionality\s\[StatefulSetBasic\]\sshould\simplement\slegacy\sreplacement\swhen\sthe\supdate\sstrategy\sis\sOnDelete$'
/tmp/openshift/build-rpm-release/tito/rpmbuild-originGCRc4S/BUILD/origin-3.7.0/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/statefulset.go:661
Pod e2e-tests-statefulset-t0n2k/ss2-0 has revision ss2-3796260542 not equal to current revision ss2-163079317
Expected
    <string>: ss2-3796260542
to equal
    <string>: ss2-163079317
/tmp/openshift/build-rpm-release/tito/rpmbuild-originGCRc4S/BUILD/origin-3.7.0/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/statefulset.go:659
			

[tnozicka]

is it possible that the pod just hasn't been deleted yet?
https://github.com/tnozicka/origin/blob/75bcc760f259d1c2a1e1ef7efdbeff9174fe6345/vendor/k8s.io/kubernetes/test/e2e/framework/statefulset_utils.go#L190

[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

[tnozicka]

likely already fixed with a rebase since last report is 90 days old