Created migration plans get stuck in unknown status

[marc-sensenich]

When creating a new migration plan using OpenShift 4.18.15 and Forklift 2.9.0, we're seeing a consistent issue where the NetworkMap and/or StorageMap are not created when referencing an existing NetworkMap and StorageMap in OpenShift

Current behavior

• Create a new migration plan that references an existing NetworkMap and StorageMap
• Migration plan is created
• Referenced NetworkMap and/or StorageMap are not created
• Migration plan gets stuck in unknown status with the following error in the logs

{"level":"error","ts":"2025-09-30 09:57:02.195","logger":"plan|g95r5","msg":"Reconcile failed.","plan":{"name":"redacted","namespace":"openshift-mtv"},"error":"Not enough data to build plan context.","stacktrace":"github.com/kubev2v/forklift/pkg/controller/base.(*Reconciler).Ended\n\t/app/pkg/controller/base/controller.go:64\ngithub.com/kubev2v/forklift/pkg/controller/plan.Reconciler.Reconcile.func1\n\t/app/pkg/controller/plan/controller.go:174\ngithub.com/kubev2v/forklift/pkg/controller/plan.Reconciler.Reconcile\n\t/app/pkg/controller/plan/controller.go:223\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Reconcile\n\t/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:119\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).reconcileHandler\n\t/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:334\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).processNextWorkItem\n\t/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:294\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Start.func2.2\n\t/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:255"}

Expected behavior

• Create a new migration plan that references an existing NetworkMap and StorageMap
• Migration plan is created
• Referenced NetworkMap and/or StorageMap are created
• Migration plan enters ready state

[mrnold]

Are you able to share any further details? I would be interested to see YAML for the Plan, Provider, NetworkMap, and StorageMap if possible.

[marc-sensenich]

I put some cleaned up YAML as asked for in a Gist at https://gist.github.com/marc-sensenich/bb6ba7a06e287aa9ee49c8d9521a1b52 to give you an idea of the size of NetworkMap and StorageMap that would be duplicated, outside of that the migration and provider are fairly basic.

And to give a rough estimate of the size of the source vCenter provider if that is of use
Datastores: ~600
Hosts: ~200
Network interfaces: ~50
Virtual machines: ~3000
Clusters: ~20
Datacenters: 1

[mrnold]

Are you directly creating the plan from the command line by any chance? I finally managed to reproduce these symptoms when I created a plan from my own YAML. It looks like the forklift UI itself creates the copies of the maps you want. Otherwise it might be okay to just reference the maps directly from your plan if you aren't worried about them changing out from under you.

[marc-sensenich]

@mrnold we're creating the migration plans from the OpenShift web console

[yaacov]

from the OpenShift web console

hi, a little off topic, for large migrations, maybe using automation may be helpful, for example:

STORAGE_PAIRS="datastore-1:default-storageclass"
for i in {2..86}; do
  STORAGE_PAIRS="${STORAGE_PAIRS},datastore-${i}:default-storageclass"
done

kubectl-mtv create mapping storage source-storagemap \
  --namespace "${NAMESPACE}" \
  --source "${SOURCE_PROVIDER}" \
  --target "${TARGET_PROVIDER}" \
  --storage-pairs "${STORAGE_PAIRS}"