+++ This bug was initially created as a clone of Bug #2039852 +++ Description of problem: Migrationcontroller pod going in "CrashLoopBackOff" state when migplan is pointing to an invalid destMigClusterRef/srcMigClusterRef. Version-Release number of selected component (if applicable): MTC 1.6.3 SOURCE CLUSTER: AWS 4.6 MTC 1.6.3 TARGET CLUSTER: AWS 4.9 MTC 1.6.3 How reproducible: Always Steps to Reproduce: 1. Create a migplan which pointing to a invalid destMigClusterRef/srcMigClusterRef For eg. oc get migplan test3 -n openshift-migration -o yaml srcMigClusterRef: name: foo namespace: openshift-migration Actual results: Migrationcontroller pod going in "CrashLoopBackOff" Expected results: Migplan should display critical warning in conditions and status should be not Ready Additional info: $ oc get pods -n openshift-migration NAME READY STATUS RESTARTS AGE migration-controller-c444f7d67-2zxdj 1/2 CrashLoopBackOff 10 80m
Fixed in master here: https://github.com/konveyor/mig-controller/pull/1251 Cloned bug to verify in 1.7.
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) 1.7.0 release advisory), 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-2022:1043