[Feature:DeploymentConfig] deploymentconfigs when run iteratively [Conformance] should only deploy the last deployment

[0xmichalis]

/tmp/openshift/build-rpms/rpm/BUILD/origin-3.11.0/_output/local/go/src/github.com/openshift/origin/test/extended/deployments/deployments.go:110
2018-07-18 10:44:16.757159708 +0000 UTC m=+108.185916470: detected deployer pod transition from terminated phase: "Failed" -> "Succeeded"
Expected
    <bool>: true
to be false
/tmp/openshift/build-rpms/rpm/BUILD/origin-3.11.0/_output/local/go/src/github.com/openshift/origin/test/extended/deployments/util.go:712

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/20347/pull-ci-origin-e2e-gcp/1112/

/kind test-flake
@openshift/sig-master

[mfojtik]

@sjenning seems like an another instance of kubelet saying that failed pod can go to succeeded ;-)

/cc @tnozicka

[tnozicka]

I thought @sjenning was adding this into API server validation last time we had this issue...

[openshift-merge-robot]

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-bot]

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-bot]

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