Steps to Reproduce:

1. Create a MongoDB cluster (e.g., 1-node) in Everest UI using a gp2 storage class.

2. Increase the disk size via the Edit Resources modal.

3. Wait for the resize to complete.

4. Attempt another disk size increase (i.e., within AWS's 6-hour modification window).

5. Observe the cluster status in the UI and compare it to the backend. (kubectl describe psmdb/<cluster-name> -n <namespace>)

Actual Outcome:

• The UI shows the cluster stuck in a 'Resizing Volumes' state.

• No error message or retry guidance is shown.

• The backend (kubectl describe) shows:

  • An error condition indicating the failure:
    Message: reconcile StatefulSet for rs0: reconcile PVCs for mongodb-2yz-rs0: resize volumes if needed: volume resize failed: (combined from similar events): resize volume "pvc-98538105-4193-46ef-9529-077bdc8c74bf" by resizer "ebs.csi.aws.com" failed: rpc error: code = Internal desc = Could not resize volume "vol-0bf041ab977cb4cf3": rpc error: code = Internal desc = Could not modify volume "vol-0bf041ab977cb4cf3": operation error EC2: ModifyVolume, https response error StatusCode: 400, RequestID: a1f62ecf-af06-4eb4-807a-218a1b7752b3, api error VolumeModificationRateExceeded: You've reached the maximum modification rate per volume limit. Wait at least 6 hours between modifications per EBS volume.

Expected Outcome:

• The UI should not show “Resizing Volumes” indefinitely if the operation has failed in the backend. It should display a clear error message derived from the backend, such as: "Disk resize failed due to AWS rate limits. You can retry after 6 hours."

Open