Skip to content

RHOAING-32257 Storage size note #921

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

RHOAING-32257 Storage size note #921

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1c0a1f2
making upstream changes
kudemba-rh Aug 29, 2025
26d3a76
removing quotes from code block
kudemba-rh Aug 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions modules/configuring-the-default-pvc-size-for-your-cluster.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,16 @@ NOTE: Changing the PVC setting restarts the workbench pod and makes it unavailab
.Verification
* New PVCs are created with the default storage size that you configured.

When resizing a PVC backed by AWS EBS in {productname-short}, you might see the following error message:

[source,terminal]
----
"VolumeModificationRateExceeded: You've reached the maximum modification rate per volume limit. Wait at least 6 hours between modifications per EBS volume".
----
This is an AWS EBS service limit, not specific to NVIDIA NIM, KServe, or any application.
It applies to all workloads using EBS-backed PVCs.
If a PVC resize is attempted before the cooldown expires, the AWS EBS CSI driver (ebs.csi.aws.com) will fail the operation with this error.

Copy link

@coderabbitai coderabbitai bot Aug 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Use an admonition and state the limit explicitly (per volume, 6-hour cooldown).

This reads like a troubleshooting note, not verification. Present it as a NOTE and make the “once per 6 hours per EBS volume” rule explicit. Also prefer “Amazon EBS” on first mention.

-When resizing a PVC backed by AWS EBS in {productname-short}, you might see the following error message:
-
-[source,terminal]
-----
-"VolumeModificationRateExceeded: You've reached the maximum modification rate per volume limit. Wait at least 6 hours between modifications per EBS volume".
-----
-This is an AWS EBS service limit, not specific to NVIDIA NIM, KServe, or any application. 
-It applies to all workloads using EBS-backed PVCs. 
-If a PVC resize is attempted before the cooldown expires, the AWS EBS CSI driver (ebs.csi.aws.com) will fail the operation with this error.
+[NOTE]
+If your cluster runs on AWS, Amazon EBS allows only one modification of the same volume every 6 hours. Attempting to resize an EBS‑backed PVC again before the 6‑hour cooldown will fail with an error from the AWS EBS CSI driver (ebs.csi.aws.com):
+
+[source,terminal]
+----
+VolumeModificationRateExceeded: You've reached the maximum modification rate per volume limit. Wait at least 6 hours between modifications per EBS volume.
+----
+This is an Amazon EBS service limit and applies to all EBS‑backed workloads, not to any particular application.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
When resizing a PVC backed by AWS EBS in {productname-short}, you might see the following error message:
[source,terminal]
----
"VolumeModificationRateExceeded: You've reached the maximum modification rate per volume limit. Wait at least 6 hours between modifications per EBS volume".
----
This is an AWS EBS service limit, not specific to NVIDIA NIM, KServe, or any application.
It applies to all workloads using EBS-backed PVCs.
If a PVC resize is attempted before the cooldown expires, the AWS EBS CSI driver (ebs.csi.aws.com) will fail the operation with this error.
[NOTE]
If your cluster runs on AWS, Amazon EBS allows only one modification of the same volume every 6 hours. Attempting to resize an EBS-backed PVC again before the 6-hour cooldown will fail with an error from the AWS EBS CSI driver (ebs.csi.aws.com):
[source,terminal]
----
VolumeModificationRateExceeded: You've reached the maximum modification rate per volume limit. Wait at least 6 hours between modifications per EBS volume.
----
This is an Amazon EBS service limit and applies to all EBS-backed workloads, not to any particular application.
🤖 Prompt for AI Agents 
In modules/configuring-the-default-pvc-size-for-your-cluster.adoc around lines
26 to 35, replace the current troubleshooting text with an Asciidoc NOTE
admonition that explicitly states this is an Amazon EBS service limit and that
volume modifications are limited to once per EBS volume every 6 hours
(per-volume 6-hour cooldown); ensure the first mention reads "Amazon EBS",
phrase it as a NOTE (admonition) and clearly state the rule "once per 6 hours
per EBS volume" and that attempts before the cooldown will cause the AWS EBS CSI
driver (ebs.csi.aws.com) to fail with the VolumeModificationRateExceeded error.

[role='_additional-resources']
.Additional resources
* link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-latest-version}/html/storage/understanding-persistent-storage[Understanding persistent storage]