Summary

OADP deployment stage fails in job deploy-ocp-bare-metal-cluster-with-abi-cnv-4.22 when deploying to an OCP 4.22 cluster. The pipeline looks up a compatible OADP version from oadp-qe-automations oadp-ocp-version-mapping.json but no entry exists for OCP 4.22, causing the stage to error and the job to fail.

Actual result

• Deploy OADP stage fails with:
  [ERROR] No compatible OADP version found for OCP 4.22
• Pipeline error: "Error while trying to Deploy OADP - hudson.AbortException: [ERROR] No compatible OADP version found for OCP 4.22"
• Subsequent stage "Sync CLUSTER_DIR to NFS" is skipped due to earlier failure.
• Job result: FAILURE

Evidence (Jenkins console)

• Job: deploy-ocp-bare-metal-cluster-with-abi-cnv-4.22 #28
• Cluster: bm08a-tlv2 (CLUSTER_DOMAIN=abi.cnv-qe.rhood.us)
• Relevant log lines:
  • [INFO] Finding latest_released OADP version compatible with OCP 4.22
  • [Pipeline] error
  • [WARNING] Failed to read oadp-ocp-version-mapping.json: hudson.AbortException: [ERROR] No compatible OADP version found for OCP 4.22
  • Error while trying to Deploy OADP - hudson.AbortException: [ERROR] No compatible OADP version found for OCP 4.22

• Repo used: https://gitlab.cee.redhat.com/migrationqe/oadp-qe-automation.git (origin/main, commit e6d2ea95cd6e4e771f93e57ec65cdecc699dd3ab)
• File consulted: oadp-ocp-version-mapping.json (checked out from origin/main)

Steps to reproduce

1. Run job deploy-ocp-bare-metal-cluster-with-abi-cnv-4.22 with DEPLOY_OADP=true (e.g. build #28).
2. Wait for stages: Deploy OCP, Deploy OCS, Deploy CNV, Deploy HPP, etc., until "Deploy OADP" stage.
3. In "Deploy OADP", the pipeline clones oadp-qe-automation, reads oadp-ocp-version-mapping.json, and looks for a compatible OADP version for the cluster OCP version (4.22).
4. No mapping for OCP 4.22 is present → script errors → stage fails.

Expected result

Either:

• oadp-ocp-version-mapping.json in oadp-qe-automation includes an entry for OCP 4.22 so that a compatible OADP version is selected and deployment proceeds, or
• The deployment pipeline handles missing OCP version gracefully (e.g. skip OADP or clear warning) when no compatible OADP version is defined.

Environment

• Jenkins: jenkins-csb-cnvqe-main.dno.corp.redhat.com
• Job: deploy-ocp-bare-metal-cluster-with-abi-cnv-4.22
• Build: 28
• Cluster: bm08a-tlv2.abi.cnv-qe.rhood.us
• OCP version: 4.22
• CNV version: 4.22.0 (candidate-stage)