Description of problem: The downstream operator.yml file's image pull spec uses a `v1.2` tag. That means if a new z-stream is released and the operator pod is restarted/rescheduled/redeployed etc., it will deploy the latest z-stream. This could potentially result in an unintended upgrade. It has been proposed that using an additional-tags file would allow us to tag our images downstream to be z-stream aware. That would allow us to include a z-stream in the pull spec tag so it always deploys the same fully qualified version, but we have yet to confirm the additional-tags file will work.
This should be addressed in 1.3.0 by using the tag 1.3.0 instead of 1.2 in the operator.yml for the operator.
Verified using MTC 1.3 openshift-migration-rhel7-operator@sha256:71156aa47b56dd673268f7f073c76c9595e6d856b4f94f61b28e599bffe12899 The image used in the operator.yml file points to the 1.3.0 version. $ oc exec migration-operator-75bdc8b65-4xtd4 cat /operator.yml |grep image | grep operator image: registry.redhat.io/rhmtc/openshift-migration-rhel7-operator:v1.3.0 Moved to VERIFIED status.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Migration Toolkit for Containers (MTC) Tool image release advisory 1.3.0), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4148