Description of problem: When there are only 2 MigClusters configured in CAM (host, and source) for instance, when in a migration plan we select one as "source" and the other one as "target", if we made a mistake and want to swap them we cant. Version-Release number of selected component (if applicable): CAM 1.2.5 How reproducible: Always Steps to Reproduce: 1. Install CAM and add a source cluster, so that you have "host" MigCluster and "source-cluster" as MigCluster too. Only 2 MigClusters. 2. Create a migration plan 3. Select "host" as source cluster 4. Select "source-cluster" as target cluster. 5. Try to fix the selection by swapping them. Actual results: Since "host" cluster is already selected as source, it cannot be selected as target. And vice versa for the source-cluster. So the situation is blocked an cannot be fixed. Expected results: We should be able to swap the clusters in case we make this mistake. Additional info: We can find a reference to this issue here in github https://github.com/konveyor/mig-ui/issues/765
I confirm the issue, this is actually a known behavior when there are 2 clusters in total (source + target). The work around is to cancel the creation of the migration plan and reselect the correct source and target cluster. A refactor of the plan wizard along with the implementation of the non-admin feature has pushed back the priority for a better solution. I'll provide an update as soon as available.
PR submitted https://github.com/konveyor/mig-ui/pull/1018. Tested & working on latest master. Pending merge.
Verified using MTC 1.3 openshift-migration-ui-rhel8@sha256:f306de1051cd2029944b2aa9511626b1dce365317fd04168478f14a43ad95e44 Moved to VERIFIED status.
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.3.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:4148