Description of problem: When we try to create an intra-cluter migration plan using the UI, after selecting the namespace the UI reports a failure and does not allow us to continue creating the migration plan. Version-Release number of selected component (if applicable): MTC 1.6.0 How reproducible: Always Steps to Reproduce: 1. In the source cluster deploy an application with a pvc oc new-project bz-intracluster-test oc new-app django-psql-persistent 2. Use the UI to create a migration plan from the source cluster to the source cluster (intra-cluster). 3. Select the "bz-intracluster-test" namespace and click "OK", do NOT map it. Actual results: After selecting the namespace the UI will show this error ''' Source PVCs [bz-intracluster-test/postgresql] are mapped to destination PVCs which result in conflicts. Please ensure that each source PVC is mapped to a distinct destination PVC and try again. ''' Expected results: We should be able to create an intra-cluster migration plan in MTC 1.6.0 Additional info:
verified with MTC 1.6.0 Image: registry.redhat.io/rhmtc/openshift-migration-ui-rhel8@sha256:9ef84beaa12e7374f45411573e369d2f1a57b680d2e63cf08b97e2bb09ecba68
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