Description of problem:
When migrating a PVC that is not attached by any pod, the cutover process is stuck at Waiting for all Stage Pods to start


Version-Release number of selected component (if applicable):
MTC 1.6.0 
openshift-migration-operator-metadata-container-v1.6.0-20

Source:
AWS OCP 3.11 + MTC 1.5.1

Target:
AWS OCP 4.6 + MTC 1.6.0

How reproducible:
Always


Steps to Reproduce:
1. In source cluster create a PVC using default storageclass, and request 1Gi
$ oc new-project ocp-41815-notattachedanalyticwarn

$ cat <<EOF | oc create -f -
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  namespace: ocp-41815-notattachedanalyticwarn
  name: test-data
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi
EOF

2. 2. Create a job that will deploy a pod to use this volume
and create 3 files of 200M each

 cat <<EOF | oc create -f -
apiVersion:  batch/v1
kind: Job
metadata:
  labels:
    app: analytic-warn-test
  name: analytic-warn-test
  namespace: ocp-41815-notattachedanalyticwarn
spec:
  replicas:  1
  template:
    metadata:
      labels:
        app: analytic-warn-test
    spec:
      restartPolicy: OnFailure
      containers:
      - name: podtest
        imagePullPolicy: Always
        image: quay.io/openshifttest/alpine
        command: [ "/bin/sh", "-c", "--" ]
        args:
        - dd if=/dev/zero of=/data/test/file_1 bs=20M count=10;
          dd if=/dev/zero of=/data/test/file_2 bs=20M count=10;
          dd if=/dev/zero of=/data/test/file_3 bs=20M count=10;
          echo "Files created";
        restartPolicy: Never
        volumeMounts:
        - name: testvolume
          mountPath: /data/test
      volumes:
      - name: testvolume
        persistentVolumeClaim:
          claimName: test-data
EOF

3. Create a migration plan for this namespace with IDVM, IDIM
report a warning on UI:
Failed to compute PV resizing data for the following volumes. PV resizing will be disabled for these volumes and the migration may fail if the volumes are full or their requested and actual capacities differ in the source cluster. Please ensure that the volumes are attached to one or more running Pods for PV resizing to work correctly: [test-data]



4. Execute cutover


Actual results:
The process is stuck at StageBackup(Waiting for all Stage Pods to start.)


Expected results:
The process should finish successfully

Additional info:
Logs from controller pod:
{"level":"info","ts":1631180571.455342,"logger":"migration","msg":"Waiting for Stage Pods to be ready on source cluster","migMigration":"migration-d9264","phase":"StagePodsCreated"}
{"level":"info","ts":1631180574.4648843,"logger":"migration","msg":"[RUN] (Step 24/48) Waiting for all Stage Pods to start.","migMigration":"migration-d9264","phase":"StagePodsCreated"}
{"level":"info","ts":1631180574.4649167,"logger":"migration","msg":"Checking health of Stage Pods on source cluster.","migMigration":"migration-d9264","phase":"StagePodsCreated"}
{"level":"info","ts":1631180574.5018363,"logger":"migration","msg":"Waiting for Stage Pods to be ready on source cluster","migMigration":"migration-d9264","phase":"StagePodsCreated"}