Description of problem:

When creating a migration plan in the Migration Toolkit for Containers (MTC), the UI becomes stuck on the "Persistent Volumes" step and does not allow users to proceed. This issue occurs due to:

A critical reconciliation failure related to a missing VirtualMachine resource in kubevirt.io/v1.
A 404 API error when trying to fetch the migration plan from the backend.
These issues cause the migration plan to remain in a Not Ready state, preventing further progress in the wizard.

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

How reproducible:
Always

Steps to Reproduce:
1. Create a new namespace & deploy an application in it
2. Navigate to the MTC UI, and got to the migration plans page
3. Click on the Add Migration Plan button
4. go through the wizard

Actual results:

• The migration controller is trying to reconcile a VirtualMachine resource in kubevirt.io/v1, which does not exist in the target cluster.

• API error: app.bundle.js:2 GET https://migration-openshift-migration.apps.cam-tgt-65800.qe.gcp.devcluster.openshift.com/cluster-api/apis/migration.openshift.io/v1alpha1/namespaces/openshift-migration/migplans/test 404 (Not Found)

Expected results:

Additional info:

The migplan yaml contained the following conditions: 

    "conditions": [
      {
        "category": "Warn",
        "durable": true,
        "lastTransitionTime": "2025-03-05T10:19:13Z",
        "message": "Found Pods with non-default `Spec.NodeSelector` set in namespaces: [ocp-django]. This field will be cleared on Pods restored into the target cluster.",
        "reason": "NodeSelectorsDetected",
        "status": "True",
        "type": "NamespacesHaveNodeSelectors"
      },
      {
        "category": "Critical",
        "lastTransitionTime": "2025-03-05T10:17:39Z",
        "message": "Reconcile failed: [no matches for kind \"VirtualMachine\" in version \"kubevirt.io/v1\"]. See controller logs for details.",
        "status": "True",
        "type": "ReconcileFailed"
      }
    ]