Description of problem:

Migration tool does not copy PVC that the cronjob uses so target cronjob does not work with the messages:
~~~
79s         Normal    SuccessfulCreate                 job/refresh-pq-1586368080                  Created pod: refresh-pq-1586368080-p2w8m
<unknown>   Warning   FailedScheduling                 pod/refresh-pq-1586368140-m45g6            persistentvolumeclaim "portal-downloads" not found
~~~

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. create a sample cronjob on source cluster
2. migrate 
3. execute the cronjob 

sample cronjob.
~~~
apiVersion: batch/v1beta1
kind: CronJob
metadata:
  name: hello
spec:
  schedule: "30 3 * * *"
  jobTemplate:
    spec:
      template:
        spec:
          containers:
          - name: hello
            image: busybox
            args:
            - /bin/sh
            - -c
            - date; echo Hello from a CronJob
          restartPolicy: OnFailure
          volumeMounts:
            - mountPath: /downlods
              name: downloads
          dnsPolicy: ClusterFirst
          restartPolicy: OnFailure
          schedulerName: default-scheduler
          securityContext: {}
          terminationGracePeriodSeconds: 30
          volumes:
          - name: downloads
            persistentVolumeClaim:
              claimName: portal-downloads
~~~
Actual results:
Cronjob always becomes suspended status.

Expected results:
it should work.

Additional info: