Description of problem: directvolumemigration-rsync-transfer pod's image is using quay.io/konveyor/rsync-transfer:latest, which is upstream image. Version-Release number of selected component (if applicable): MTC 1.4.0 Images: registry.redhat.io/rhmtc/openshift-migration-rhel7-operator@sha256:61de8be7e30fb15b278aeececb0de8ac5ecaeb221a312ab1140e6c925ab0e217 registry.redhat.io/rhmtc/openshift-migration-controller-rhel8@sha256:b64b43a7f982ce1bd9a92de4f10f6468a54be059df0e0d192022b513f2505366 How reproducible: Always Steps to Reproduce: Checked that directvolumemigration-rsync-transfer pod is using upstream image quay.io/konveyor/rsync-transfer:latest. Actual results: $ oc get pod -n ocp-37664-stage-progressreporting directvolumemigration-rsync-transfer -o yaml | grep image: | sort -u f:image: {} image: quay.io/konveyor/rsync-transfer:latest Expected results: It should point to the downstream image Additional info:
directvolumemigration-stunnel-transfer pod as well. $ oc get pod directvolumemigration-stunnel-transfer -o yaml | grep image: f:image: {} image: quay.io/konveyor/rsync-transfer:latest image: quay.io/konveyor/rsync-transfer:latest
https://projects.engineering.redhat.com/browse/RCMAUTO-3946
verified. $ oc get pod -n ocp-24730-django -o yaml | grep image: f:image: {} f:image: {} image: registry.redhat.io/rhmtc/openshift-migration-rsync-transfer-rhel8@sha256:715d6869c6d23d572808d64c511b94c6af07a6bce08b4f62a78542b61f3af02a
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.4.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:5329