Image Pushes Don't Always Trigger New Deployments

[liam-middlebrook]

When a source2image build is set to automatically push an image to the image store that process happens as expected. The associated deployment configuration is set to automatically deploy when the imagestream object is updated. However this automatic new deployment is inconsistently working or not after a completed source2image build.

Version

openshift v1.5.1
kubernetes v1.5.2+43a9be4

Current Result

After completion builds will push their images to the repository. The deployment config sporadically updates to use the new image and then trigger a redeployment.

Expected Result

After completion builds will push their images to the repository. The deployment config will consistently update to use the newly pushed image and then trigger a redeployment.

[0xmichalis]

Maybe related to #16728

@mfojtik @tnozicka these issues need triaging

[tnozicka]

Hard to say without more detailed info provided (oc get dc,is,build -o yaml).

Origin 1.5.1 is also not supported release anymore and it got significant rewrite since that time. Could you try it with 3.7.1 to see if the issue got fixed?

[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

[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