Created attachment 1730143 [details]
Screenshot

Description of problem:
The UI cannot detect the right storage classes in the target cluster.


Version-Release number of selected component (if applicable):
MTC 1.3.2
TARGET CLUSTER: OCP 4.6 AWS
SOURCE CLUSTER: OCP 3.11 AWS


How reproducible:
Always

Steps to Reproduce:
1. Deploy an application with one PVC in the source cluster

oc new-project bztest
oc new-app django-psql-persistent

2. Use the UI to create a migration plan for this application


Actual results:
In the screen where the target storage class should be selected, we click on the "Targe storage class" item to select the right one and the only option shown is "None".

Expected results:
All storages classes in the target cluster should be displayed when we try to choose the target storage class.


Additional info:

In target cluster we have these SCs

$ oc get sc
NAME            PROVISIONER             RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
gp2 (default)   kubernetes.io/aws-ebs   Delete          WaitForFirstConsumer   true                   68m
gp2-csi         ebs.csi.aws.com         Delete          WaitForFirstConsumer   true                   68m

In source cluster we have these SCs

$ oc get sc
NAME            PROVISIONER             AGE
gp2 (default)   kubernetes.io/aws-ebs   3h


The migcluster has the right storageclasses in it:

spec:
  isHostCluster: true
  storageClasses:
  - accessModes:
    - ReadWriteOnce
    default: true
    name: gp2
    provisioner: kubernetes.io/aws-ebs
  - accessModes:
    - ReadWriteOnce
    name: gp2-csi
    provisioner: ebs.csi.aws.com