Description of problem:
When we run a direct migration, the directvolumemigration-rsync pod cannot be created in the source cluster because it cannot mount the volumes.


Version-Release number of selected component (if applicable):
MTC 1.4.0
SOURCE CLUSTER: AWS 3.11
TARGET CLUSTER: AWS 4.6
REPLICATION REPOSITORY: AWS S3

How reproducible:
Always

Steps to Reproduce:
1. Run a migration with direct copy using gp2 storage class

Actual results:
The directvolumemigration pods will have problems mounting the volumes.

$ oc get pods
NAME                                         READY     STATUS              RESTARTS   AGE
cakephp-mysql-persistent-1-build             0/1       Completed           0          5m
cakephp-mysql-persistent-1-xxkp6             1/1       Running             0          4m
directvolumemigration-rsync-transfer-mysql   0/1       ContainerCreating   0          12s
directvolumemigration-stunnel-transfer       1/1       Running             0          18s
mysql-1-kq8xc                                1/1       Running             0          4m

We get this message in the events:

  Warning  FailedAttachVolume  1m    attachdetach-controller  Multi-Attach error for volume "pvc-33a8a017-3578-11eb-9bcf-0e5715382039" Volume is already used by pod(s) mysql-1-kq8xc


The reason is that the directvolumemigration-rsync-transfer-mysql pod and the mysql-1-kq8xc pod should be deployed in the same node, but actually they are deployed in different nodes, so the directvolumemigration pod cannot mount the volume.

$ oc get pods directvolumemigration-rsync-transfer-mysql -o yaml |grep -i nodeName
  nodeName: ip-172-18-8-191.ec2.internal
$ oc get pods mysql-1-kq8xc -o yaml |grep -i nodeName
  nodeName: ip-172-18-6-152.ec2.internal


Expected results:
The migration should be executed without problems.

Additional info: