Description of problem: When the registry pod is not available, the migration will report an error and the migration execution will be stopped. When this happens, the migration plan is not set on "Not Ready" status, and the user can continue launching more migration runs. Version-Release number of selected component (if applicable): MTC 1.4.0 How reproducible: Always Steps to Reproduce: 1. Create a new namespace in source cluster oc new-project test-bz 2. Create a migration plan for this namespace 3. In controller cluster, wait until the registry deployment is created oc get deployments -n openshift-migration 4. Once the registry deployment is created, scale it to 0 oc -n openshift-migration scale deployment NAME_OF_THE_REGISTRY_DEPLOYMENT --replicas=0 Actual results: A critical condition will be reported in the MigMigration resource, and an error will be prompted in the UI. The migration will be stopped. But the migplan resource is not moved to "not ready" status. Expected results: The migplan resource should be moved to "Not ready" status when there is a problem like this one. It prevents the user to launch infinite migration runs while the original execution is stopped. Additional info:
Testing on a 4.5 cluster, this is the state of the migplan after doing the above: status: conditions: - category: Required lastTransitionTime: "2020-12-07T23:26:23Z" message: The `persistentVolumes` list has been updated with discovered PVs. reason: Done status: "True" type: PvsDiscovered - category: Required lastTransitionTime: "2020-12-07T23:26:28Z" message: The storage resources have been created. reason: Done status: "True" type: StorageEnsured - category: Required lastTransitionTime: "2020-12-07T23:26:28Z" message: The migration plan is ready. status: "True" type: Ready - category: Advisory lastTransitionTime: "2020-12-07T23:43:26Z" message: The migrations plan is in suspended state; Limited validation enforced; PV discovery and resource reconciliation suspended. status: "True" type: Suspended This is reported in the UI as a migration "In Progress" with a displayed pipeline step of "prepare" with the message "Waiting for migration registries on source and target clusters to become healthy." I will test again & report my findings.
I found the issue - PR submitted pending review & merge https://github.com/konveyor/mig-ui/pull/1082
Verfied using 1.4.0 Because of a change in the design, the migration plan will not be in "Not ready" status any more. We have verified that migration is marked as failure in the UI, both in the migmigration and in the migplan resources.
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