Hi,

I tried but failed to reproduce this bug. Here are the steps I followed:
1. Create a project on ocp-3.11 cluster which uses an nfs PV.
2. Tested the nfs service (hosted on ocp-3.11 node) is not accessible from the ocp-4.5 node by running `showmount -e <IP_ADDR_OF_NFS_HOST>`. 
3. Ran the migrate on ocp-4.5. 

--------------------------------------------------
Following is the MigPlan status:
--------------------------------------------------
apiVersion: migration.openshift.io/v1alpha1
kind: MigPlan
metadata:
  annotations:
    openshift.io/touch: 56c7f4d4-2e79-11eb-bda4-0a580a83006d
  selfLink: >-
    /apis/migration.openshift.io/v1alpha1/namespaces/openshift-migration/migplans/nfspvmig
  resourceVersion: '15437564'
  name: nfspvmig
  uid: afd54578-1f39-4dc7-8204-de58cd0cb842
  creationTimestamp: '2020-11-24T17:05:41Z'
  generation: 7
  managedFields:
    - apiVersion: migration.openshift.io/v1alpha1
      fieldsType: FieldsV1
      fieldsV1:
        'f:spec':
          .: {}
          'f:destMigClusterRef':
            .: {}
            'f:name': {}
            'f:namespace': {}
          'f:migStorageRef':
            .: {}
            'f:name': {}
            'f:namespace': {}
          'f:namespaces': {}
          'f:srcMigClusterRef':
            .: {}
            'f:name': {}
            'f:namespace': {}
      manager: Mozilla
      operation: Update
      time: '2020-11-24T17:05:57Z'
    - apiVersion: migration.openshift.io/v1alpha1
      fieldsType: FieldsV1
      fieldsV1:
        'f:metadata':
          'f:annotations':
            .: {}
            'f:openshift.io/touch': {}
        'f:spec':
          'f:persistentVolumes': {}
        'f:status':
          .: {}
          'f:conditions': {}
          'f:excludedResources': {}
          'f:observedDigest': {}
      manager: manager
      operation: Update
      time: '2020-11-24T17:20:24Z'
  namespace: openshift-migration
spec:
  destMigClusterRef:
    name: host
    namespace: openshift-migration
  migStorageRef:
    name: irlvelero
    namespace: openshift-migration
  namespaces:
    - nfspvtest
  persistentVolumes:
    - capacity: 10Gi
      name: vol51
      pvc:
        accessModes:
          - ReadWriteOnce
        hasReference: true
        name: nfs-pvc
        namespace: nfspvtest
      selection:
        action: copy
        copyMethod: filesystem
        storageClass: gp2
      supported:
        actions:
          - copy
          - move
        copyMethods:
          - filesystem
          - snapshot
  srcMigClusterRef:
    name: ocp3
    namespace: openshift-migration
status:
  conditions:
    - category: Required
      lastTransitionTime: '2020-11-24T17:05:42Z'
      message: The `persistentVolumes` list has been updated with discovered PVs.
      reason: Done
      status: 'True'
      type: PvsDiscovered
    - category: Required
      lastTransitionTime: '2020-11-24T17:05:42Z'
      message: The storage resources have been created.
      status: 'True'
      type: StorageEnsured
    - category: Required
      lastTransitionTime: '2020-11-24T17:05:43Z'
      message: The migration registry resources have been created.
      status: 'True'
      type: RegistriesEnsured
    - category: Required
      lastTransitionTime: '2020-11-24T17:05:43Z'
      message: The migration plan is ready.
      status: 'True'
      type: Ready
    - category: Advisory
      lastTransitionTime: '2020-11-24T17:08:11Z'
      message: Limited validation; PV discovery and resource reconciliation suspended.
      status: 'True'
      type: Suspended
  excludedResources:
    - imagetags
    - templateinstances
    - clusterserviceversions
    - packagemanifests
    - subscriptions
    - servicebrokers
    - servicebindings
    - serviceclasses
    - serviceinstances
    - serviceplans
    - operatorgroups
    - events
  observedDigest: 772c3d0b32a1b6401ab7263b7c368d8eb7a7ae55faec66278730447e5945c1f6


--------------------------------------------------------------------------------------------
Please let me know if there is any step I might have missed in manifesting this bug.

Hello,

You followed the right steps to reproduce the issue.

I have tried to reproduce the bug too using MTC 1.3.2 and it seems that problem is not there any more.

Thank you.

Verified in MTC 1.4.0

The warning is not displayed any more.

Moved to VERIFIED status.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Migration Toolkit for Containers (MTC) 1.4.0 Operator metadata image advisory), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:5330