Description

When running migrations using MTC 1.8.7 on OpenShift 4.19, the process gets stuck in the Prepare phase with the MigPlan being marked as Suspended, despite no completed migration. The root cause is the deployment of an incompatible OADP version (< 1.5) whose DataProtectionApplication (DPA) spec format is not compatible with OCP 4.19.

Root Cause

MTC’s current logic does not account for breaking changes introduced in OADP 1.5 and its incompatibility with older DPA schemas. OpenShift 4.19 requires OADP 1.5+, but the system still deploys or assumes compatibility with older versions by default.

Observed events

Normal   Ready                     The migration plan is ready.
Normal   MigrationTypeIdentified   This plan was previously used for migrating namespaces...
Normal   Suspended                 The plan is in suspended state; PV discovery suspended.
(repeats multiple times without any successful migration)

Steps to Reproduce

1. Deploy MTC 1.8.7 on OpenShift 4.19.

1. Let MTC auto-create the velero DPA resource

   configuration:
     restic:
       enable: true

1. Attempt a migration using a new MigPlan.

Actual Result

• Migration never starts; the plan gets stuck in Prepare.

• MigPlan is incorrectly marked as Suspended.

• No data is migrated, and Velero is broken.

• Logs from openshift-adp-controller-manager show
   

  error: Delete restic object from spec.configuration, use spec.configuration.nodeAgent instead