Verified using AWS OCP 3.11 (MTC 1.5.1) -> AWS OCP 4.9 (MTC 1.6.0) openshift-migration-rhel7-operator@sha256:0d695a342a439e751fe7473b24a21eeca4cd5dc584253ad0f567762448cbda37 - name: MIG_CONTROLLER_REPO value: openshift-migration-controller-rhel8@sha256 - name: MIG_CONTROLLER_TAG value: d1bb94853b42abef96ec2c63600ebac41b0163d88fc25571f7b40c6c1d2f8c40 - name: MIG_UI_REPO value: openshift-migration-ui-rhel8@sha256 - name: MIG_UI_TAG value: 3e46187b2ff8c76c4022b418631d07eb40a347d15012d061c079e643a4188b6d Now, when we click on the link suggested by the message, we are redirected to the screen where we can upgrade the MTC operator. 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 (Moderate: Migration Toolkit for Containers (MTC) 1.6.0 security & bugfix update), 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/RHSA-2021:3694