When creating a migration plan using VDDK upload, if the target namespace is different from openshift-mtv, the plan remains in not ready state and the vddk-validator job is not created.However, once another plan is created with openshift-mtv as the target namespace, both plans suddenly become ready and complete successfully.This may indicate a permission or namespace scoping problem similar to the original VDDK upload issue.

├── OCP version: 4.19.18
├── MTV version: 2.10.0 (redhat-osbs-on-pr-432f7fbaf4da82396688b9787f228a2d3a0a6564)
└── CNV version: 4.19.14

Always

curl -k -i -X POST -H "Authorization: Bearer $(oc whoami --show-token)" \ -F "file=@/Users/msafra/Documents/vddk/VMware-vix-disklib-8.0.0-20521017.x86_64.tar.gz" \ https://forklift-inventory-openshift-mtv.apps.qemtvd-05.rhos-psi.cnv-qe.rhood.us/vddk/build-image 

wscat --no-check \ -c "wss://forklift-inventory-openshift-mtv.apps.qemtvd-05.rhos-psi.cnv-qe.rhood.us/vddk/image-url?build-name=vddk-8" \ -H "Authorization: Bearer $(oc whoami --show-token)" \ -H "X-Watch: true"  

 kubectl-mtv create plan mig \   --source vmware-7 \   --vms ameen-RHEL9 \   --default-target-storage-class ocs-storagecluster-ceph-rbd-virtualization \   --target-namespace default  

oc get plan mig oc get jobs  

NAME   READY   EXECUTING   SUCCEEDED   FAILED   AGE mig                                             3m29s No resources found in openshift-mtv namespace. 

kubectl-mtv create plan mig-openshift-mtv \   --source vmware-7 \   --vms ameen-RHEL9 \   --default-target-storage-class ocs-storagecluster-ceph-rbd-virtualization \   --target-namespace openshift-mtv 

oc get plan oc get jobs  

NAME                READY   EXECUTING   SUCCEEDED   FAILED   AGE mig                 True                                     7m47s mig-openshift-mtv   True                                     76sNAME                                    STATUS     COMPLETIONS   DURATION   AGE vddk-validator-mig-openshift-mtvzmfp2   Complete   1/1           6s         30s  

When the target namespace is not openshift-mtv, the plan never becomes ready and no validator job is created.

After creating another plan targeting openshift-mtv, both plans become ready and succeed.

Plan should become ready regardless of the target namespace.
vddk-validator job should be created immediately for each plan.