Description of problem:

Create migration plan to migrate VM from ova provider to OCP cluster, hit error below, more details in attached file: "Screencast From 2026-01-13 19-37-07.mp4"

"The plan is not ready Map.Network does not have Ready condition. To troubleshoot, check the Forklift controller pod logs."

Check on the cluster, the root cause is the nfs dir permission is changed during the plan execution, the provider is ready status but without listing any VMs, the plan is hang.

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

MTV 2.10.3-6 with OCP 4.20.8, CNV 4.20.5

How reproducible:

Always

Steps to Reproduce:

1) Add the feature flag in the forklift-controller: `feature_ova_appliance_management: 'true'`

2) Create a ova provider: ova-nfs-ap with "applianceManagement: 'true'", it has VMs: Auto-esx8.0-win2019-efi-with-extra-online-disks

3) Create migration plan: pva-nfs-test to migrate VM:  mtv-rhel8-warm-2disks2nics from ova provider to OCP cluster, hit error below, more details in attached file: "Screencast From 2026-01-13 19-37-07.mp4"

"The plan is not ready Map.Network does not have Ready condition. To troubleshoot, check the Forklift controller pod logs."

3) Check on the cluster, the root cause is that the ova provider path permission is changed during the plan execution,

the provider is Reay status, but without any Virtual machines.

4) The plan is hang, it's keep on 57%, more details in attached files: forklift-controller-74dcbd87fd-sd5mg-main.log, plan-ova-nfs-test.yaml, networkmap-ova-nfs-ap-c57dr.yaml

Actual results:

In step3: Hit unexpected Map.Network error, plan is hang

Expected results:

In step3: Plan is failed.

Additional info: