Description of problem: When we configure a wrong registry pod image in the migrationcontroller resource, the migration is stuck forever. Version-Release number of selected component (if applicable): MTC 1.4.0 How reproducible: Always Steps to Reproduce: 1. In source cluster. Create namespace $ oc new-project ocp-37313-registrybadimagetgt 2. In source cluster. Configure the migrationcontroller in order to use a wrong registry pod image $ oc patch migrationcontroller migration-controller -n openshift-migration --type merge -p '{"spec":{"migration_registry_image":"docker.io/registry-fake","migration_registry_repo":"registry","migration_registry_version":"2"}}' 3. Create a migration plan to migrate the namespace created in step 1 and run the migration Actual results: The migration is stuck forever saying "waiting for pods to be ready" on the UI. Expected results: The migration should fail if we cannot create the registry pods, or at least show an error/warning telling the user that the registry pods cannot be created because of an ImagePullBackOff error and the cluster where the pods cannot be created. Additional info:
The PR https://github.com/konveyor/mig-controller/pull/860 resolves this bug
verified. it will report error message like below Danger alert:This migration has following error conditions: Migration Registry Pod openshift-migration/registry-2a0bfbe0-06df-4f60-845a-aacc12c044b0-69dwv-7976f8ncr47 is in unhealthy state on cluster source-cluster, the Pod is in ImagePullBackOff state
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