Deployment can gets stuck after recreating

[mfojtik]

After running this little script the output will be following:

--> running test #1 ...
deploymentconfig "test" deleted
deploymentconfig "test" created
--> status of #1 is Pending ...
--> status of #1 is Running ...
--> running test #2 ...
deploymentconfig "test" deleted
pod "test-1-deploy" deleted
pod "test-1-s7vq4" deleted
deploymentconfig "test" created
--> status of #2 is Running ...
--> running test #3 ...
deploymentconfig "test" deleted
pod "test-1-deploy" deleted
deploymentconfig "test" created
--> status of #3 is Failed ...

What I think happen is that the "test-1-deploy" pod is in Terminating status (or it is being terminated by GC), however it is not fast enough and that means the next DC will fail to create deployer pod (because it already exists) and it never retries.

Before we giving up on creating a new deployer pod for new DC, we should perhaps check the ownerRef and verify that the test-1-deploy which already exists is meant to be for the current DC. We should reconcile and recreate that Pod for the new DC?

[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

[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

[tnozicka]

/lifecycle frozen
/remove-lifecycle rotten