RHSA-2026:56366: Red Hat OpenShift Data Foundation 4.19.22 security, enhancement & bug fix update
Red Hat OpenShift Data Foundation 4.19.22 security, enhancement & bug fix updateFIXED BUGS:==========DFBUGS-7382: [Backport to odf-4.19.z] [GSS] PDB is created for rgw even though the gateway instance count is 1DFBUGS-7005: [Backport to odf-4.19.z] [GSS][Disconnected env] ODF is upgraded itself from ODF v4.20.2 to ODF v4.20.7 without Manual Approval when upgrdaing OCP v4.20.5 to OCP v4.20.16DFBUGS-6996: [Backport to odf-4.19.z] [GSS][ODF] Noobaa DBCLEANER not honoring set valueDFBUGS-6815: release-4.19 ODF must-gather missing CR storageclusterpeer.yamlDFBUGS-6704: Backport to odf-4.19.z [GSS] Unnecessary OSD redeployments on 4.19.z upgrade for already-encrypted OSDsDFBUGS-5636: [4.19]Topology awareness issueDFBUGS-3947: 4.19 [RDR] cephblockpool radosnamespaces contains "failed to retrieve mirroring pool ocs-storagecluster-cephblockpool" message after the uninstallation of DR
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Red Hat OpenShift Data Foundationto a version that resolves this vulnerability.Fixed in 4.19.22Patch Red Hat OpenShift Data Foundation 4.19.22 security, enhancement & bug fix update - Operational
Before applying the 4.19.22 update, make sure all previously released errata relevant to your system have been applied.
Event History
Frequently Asked Questions
Which environments are most likely to benefit from this update?
The listed fixes apply to Red Hat OpenShift Data Foundation 4.19.z environments, including deployments using RGW, NooBaa, encrypted OSDs, topology awareness, or disaster recovery components.
Are single-instance RGW deployments affected by a known issue?
Yes. The update fixes an issue where a Pod Disruption Budget was created for RGW even when the gateway instance count was one.
Does this update address upgrade behavior in disconnected environments?
Yes. It fixes an issue in disconnected environments where ODF could upgrade from version 4.20.2 to 4.20.7 without manual approval during an OpenShift Container Platform upgrade from 4.20.5 to 4.20.16.
How can administrators identify one of the addressed disaster recovery issues?
After uninstalling DR, affected environments may show a "failed to retrieve mirroring pool ocs-storagecluster-cephblockpool" message in cephblockpool radosnamespaces.