Description of problem: When we click on edit migplan it should show correct information related to the target namespace. Version-Release number of selected component (if applicable): SOURCE CLUSTER: AWS 4.6 (MTC 1.6.0) TARGET CLUSTER: AWS 4.9 (MTC 1.6.0) (CONTROLLER + UI) How reproducible: Always Steps to Reproduce: 1. Create a migplan from UI. Change the target namespace. 2. Click on edit migplan and go to the namespace page. Actual results: Migplan is showing wrong target namespace Expected results: Migplan should show correct target namespace Additional info: In backend we can see the correct target namespace. oc get migplan -n openshift-migration state-migration -o yaml spec: destMigClusterRef: name: source-cluster namespace: openshift-migration migStorageRef: name: automatic namespace: openshift-migration namespaces: - cakephp:cakephp-new
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