+++ This bug was initially created as a clone of Bug #1777869 +++

Description of problem:
In the volumes screen (step 3) the name of the storage class has a wrong value.

Version-Release number of selected component (if applicable):
UI image:
Release 1.0.1 stored in rh-osbs
  image: image-registry.openshift-image-registry.svc:5000/rhcam-1-0/openshift-migration-ui-rhel8@sha256:5e04d383b3796982aaf366c7bb6742661bc4b4964a326ee8db20c533f1831342

TARGET CLUSTER:
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.2.0     True        False         26h     Cluster version is 4.2.0

SOURCE CLUSTER:
$ oc version
Client Version: version.Info{Major:"4", Minor:"1+", GitVersion:"v4.1.4", GitCommit:"c9e4f28ff", GitTreeState:"clean", BuildDate:"2019-06-26T23:04:27Z", GoVersion:"go1.12.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.0+d4cacc0", GitCommit:"d4cacc0", GitTreeState:"clean", BuildDate:"2019-11-26T00:42:21Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}

How reproducible:
Always

Steps to Reproduce:
Use a source cluster with glusterfs, and a target cluster with ceph.

1. Create a migration plan to migrate a volume that uses "glusterfs-storage" storage class
2. In step 3, verify the storage class name shown

Actual results:
The storage class shown in step 3 is a ceph storage class, instead of the "glusterfs-storage" storage class actually used in the source cluster.

Expected results:
Step 3 should show the current storage class used in the source cluster, and not the destination storage class in the target.

Additional info: