Request OKD SCOS 4.22.0-okd-scos.4 → 5.0.0-okd-scos.0 bare-metal IPI upgrade validation

[ng023]

Describe the problem or request

We are evaluating an upgrade path for an existing bare-metal IPI OKD cluster running 4.22.0-okd-scos.4. The Cincinnati update graph currently offers no upgrade edges from this specific release to the 5.0 stream.

While a successful AWS Prow test exists for 4.22.0-okd-scos.4 → 5.0.0-okd-scos.0 (see link below), we require validation specifically for the bare-metal architecture to ensure underlying hardware/network platform layers transition smoothly.

Link to existing Prow run

• AWS Upgrade Test: https://prow.ci.openshift.org/view/gs/test-platform-results-public/logs/release-openshift-origin-installer-launch-aws-modern/2100738466840055808

Requested Validation

Could the maintainers verify if an existing Prow run already covers this pair on metal, or configure/execute a dedicated CI run using the existing e2e-metal-ipi-ovn-upgrade workflow?

The desired validation target is a complete bare-metal IPI upgrade demonstrating successful ClusterVersion, ClusterOperators, and MachineConfigPools convergence.

Release Component Details

• Source Image (4.22.0-okd-scos.4):
  registry.ci.openshift.org/origin/release-scos@sha256:79dea1961581c52b6b1674a318be012c1560acccfdf8954be46b06eaf8ca5307
• Target Image (5.0.0-okd-scos.0):
  quay.io/okd/scos-release@sha256:eca01dee0f0690a8149d58f0a8c7e3187f624d583c1b713dc660bd1b28c2dfbc