Enabling z-stream updates for clusters affected by RHTAS Operator 1.2.1 to 1.3.2 incorrect update

Solution Unverified - Updated

Environment

  • Red Hat OpenShift Container Platform 4.15 clusters
  • Stable channel with auto-update enabled
  • RHTAS Operator version 1.2.1

Issue

An incident involving the Operator Lifecycle Manager (OLM) catalog has caused Red Hat OpenShift to incorrectly update the RHTAS Operator from version 1.2.1 to 1.3.2. This mismatch affects Red Hat OpenShift 4.15 clusters by locking them on RHTAS version 1.3.2 unexpectedly.

Resolution

To resolve this and ensure future security patches:

  1. Perform a full backup of your RHTAS data.
  2. Upgrade the Red Hat OpenShift cluster to version 4.16 or newer.
  3. Restore your RHTAS data.

Upgrading the underlying cluster ensures platform compatibility with RHTAS Operator versioning requirements and resolves the OLM routing conflict.

For more details, see the RHTAS support policy

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.
    Incident Article

Diagnostic Steps

Diagnostic Steps

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.