Avoid duplicated/cancelled deployments when processing custom templates using external private registries

Solution Verified - Updated -

Issue

Processing custom templates with oc process "some-template" | oc apply -f - with customized imagestreams to store image information from external private registries and ImageChange triggers creates duplicated replicationControllers, with the first being cancelled with:

openshift.io/deployment.cancelled=true
openshift.io/deployment.phase=Failed
openshift.io/deployment.replicas=0
openshift.io/deployment.status-reason=newer deployment was found running

And second completed successfully with:

openshift.io/deployment.phase=Complete
openshift.io/deployment.replicas=
openshift.io/deployment.status-reason=image change

Environment

Openshift Container Plataform 3.7 and 3.9

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In