Enabling z stream updates for clusters that automatically updated ODF to v4.18.z while running on OCP 4.17.z

Solution Verified - Updated

Environment

  • Red Hat OpenShift Data Foundation (RHODF) 4.18.z

  • Red Hat OpenShift Container Platform (RHOCP) 4.17.z

Issue

  • Enabling z stream updates for clusters that automatically updated ODF to v4.18.z while running on OCP 4.17.z

Resolution

  • To fully resolve this issue and restore a standard supported configuration, it is recommended to upgrade the cluster from OCP 4.17.z to OCP 4.18.z immediately.

  • While running ODF 4.18 on OCP 4.17 is not a standard recommended configuration, internal QE verification and basic regression testing have confirmed cluster should remain stable.

  • If an OCP upgrade is not immediately feasible, the following workaround allows you to maintain your current environment while continuing to receive critical ODF bug fixes and CVE updates for 4.18. Use these steps until a full OCP platform upgrade can be scheduled.

  1. Red Hat will be maintaining a snapshot of the latest ODF 4.18.z at quay.io/rh-storage-partners/olm-incident-index:v4.17 which can be used for upgrading ODF to latest 4.18.z until OCP upgrade is done. The content will be kept updated until End-of-life of OCP/ODF 4.17 (April 1 2026).

  2. Apply below ITMS rule:

    apiVersion: config.openshift.io/v1
kind: ImageTagMirrorSet
metadata:
  name: redhat-operators-stage
spec:
  imageTagMirrors:
  - source: registry.redhat.io/redhat/redhat-operator-index
    mirrors:
    - quay.io/rh-storage-partners/olm-incident-index
  mirrorSourcePolicy:
    AllowContactingSource 0

IMPORTANT Note: Once the OCP upgrade is planned, delete the above ITMS rule before OCP upgrade is triggered.

Root Cause

  • A repository management error led to the accidental publication of v4.18 redhat-operators catalog content into legacy tags (v4.12 - v4.16). This caused a catalog-to-platform version mismatch.
  • For clusters with automatic OLM updates enabled, the OLM interpreted the v4.18 content as a valid "recommended update" path. Consequently, operators were upgraded to versions incompatible with the underlying OpenShift version, leading to a failure state that persisted even after the catalog was corrected, Reference OCP Bug: This content is not included.OCPBUGS-75921.
SBR
Product(s)
Category

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.