Red Hat Workload Availability operators inadvertently upgraded to their v4.16 version on OCP 4.12 - 4.15 clusters
Environment
- Red Hat OpenShift Container Platform < 4.16
- Red Hat Operators:
- node-healthcheck-operator
- self-node-remediation
- fence-agents-remediation
- machine-deletion-remediation
- node-maintenance-operator
Issue
For several hours on February 3, 2026, Red Hat released version 4.18 of the Red Hat Operators catalog content into OpenShift Container Platform (OCP) cluster versions 4.12-4.17, inclusive.
For more information, including Diagnostic Steps, please refer to Red Hat Operator has version higher than the cluster version.
Due to this incident, the Red Hat Workload Availability (RHWA) Operators may have been upgraded to a version higher than what is supported by the underlying OCP cluster version. Since the 4.18 versions of the RHWA operators were already supported on OCP 4.16 and OCP 4.17, those OCP versions are not affected by the above incident.
Note: The console plugin which is installed with the node-healthcheck-operator, and is caused by incompatibilities of the OCP 4.16 version of that plugin with older OCP versions. For assistance regarding that known breakage, please reach out to This content is not included.Red Hat Support and reference this Knowledgebase article.
Resolution
When running OCP 4.16 versions of the RHWA Operators on OCP less than version 4.16, it is not a standard recommended configuration. Internal verification and basic regression testing have confirmed that clusters should remain stable though there are known incompatibilities (such as the console plugin mentioned above).
- Red Hat will offer the OCP version 4.16 of the RHWA operators on OCP 4.12 to OCP 4.15 (inclusive) in a specific OLM channel, which allows you to maintain your current environment, and receive critical operator updates on the OCP EUS versions 4.12 and 4.14.
- Affected customers need to update the Subscriptions of the RHWA operators to use the
ITN-2026-00040-stablechannel. When a cluster is upgraded to OCP 4.16 or later, it is required that these operators revert to the "stable" channel. - Because of indirect dependencies between the RHWA operators, using different channels for each operator is strongly recommended against and not supported.
Diagnostic Steps
For any of the following Operators, verify the corresponding version is installed. The versions can be verified via the CLI via oc get csv and also under the "Installed Operators" menu (Nested under "Operators") within the Console:
| Operator | OCP 4.12 | OCP 4.13 | OCP 4.14 | OCP 4.15 |
|---|---|---|---|---|
| node-healthcheck-operator | 0.8.2 | 0.8.2 | 0.9.1 | 0.9.1 |
| self-node-remediation | 0.9.0 | 0.9.0 | 0.10.2 | 0.10.2 |
| fence-agents-remediation | 0.4.1 | 0.4.1 | 0.5.1 | 0.5.1 |
| machine-deletion-remediation | 0.3.1 | 0.3.1 | 0.4.1 | 0.4.1 |
| node-maintenance-operator | 5.3.1 | 5.3.1 | 5.4.1 | 5.4.1 |
If an unexpected version is present, such as the following, the cluster is affected:
- node-healthcheck-operator
0.10.1 - self-node-remediation:
0.11.0 - fence-agents-remediation:
0.6.0 - machine-deletion-remediation:
0.5.0 - node-maintenance-operator:
5.5.0
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.