From baad2d17b9e6b3b06dd5f661e8029691c8b5b3b9 Mon Sep 17 00:00:00 2001 From: William Gabor Date: Fri, 17 Oct 2025 08:03:27 -0400 Subject: [PATCH] OSDOCS-15028 updated storage RNs --- release_notes/ocp-4-20-release-notes.adoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/release_notes/ocp-4-20-release-notes.adoc b/release_notes/ocp-4-20-release-notes.adoc index ef27d22477..cb9a1e25e8 100644 --- a/release_notes/ocp-4-20-release-notes.adoc +++ b/release_notes/ocp-4-20-release-notes.adoc @@ -1723,10 +1723,9 @@ As a result, the controller handles errors during migration better. [id="ocp-release-note-storage-bug-fixes_{context}"] === Storage +* Before this update, resizing or cloning small {gcp-first} Hyperdisk volumes (e.g., from 4Gi to 5Gi) would fail due to an Input/Output Operations Per Second (IOPS) validation error from the {gcp-full} API. This occurred because the Container Storage Interface (CSI) driver did not automatically adjust the provisioned IOPS to meet the minimum requirements of the new volume size. With this release, the driver has been updated to correctly calculate and provide the required IOPS during volume expansion operations. Users can now successfully resize and clone these smaller Hyperdisk volumes. (link:https://issues.redhat.com/browse/OCPBUGS-62117[OCPBUGS-62117]) - - - +* Before this update, a race condition would sometimes cause an intermittent failure, or _flake_, when a Persistent Volume Claim (PVC) was resized too quickly after being created. This resulted in an error where the system would incorrectly report that the bound Persistent Volume (PV) could not be found. With this release, the timing issue was fixed, so resizing a PVC right after its creation works. (link:https://issues.redhat.com/browse/OCPBUGS-61546[OCPBUGS-61546]) [id="ocp-release-note-rhcos-bug-fixes_{context}"]