-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18
-
None
-
Quality / Stability / Reliability
-
True
-
-
None
-
None
-
None
-
None
-
None
-
None
-
In Progress
-
Bug Fix
-
-
None
-
None
-
None
-
None
Description of problem:
Hyperdisk volume original size need to be larger than 6Gi when do resize/clone operation
Version-Release number of selected component (if applicable):
4.18
How reproducible:
Always
Steps to Reproduce:
1.Create sc with hypberdisk-balanced volume type 2.Create pvc/pod and pvc volume capacity is 6Gi 3.Try to resize the volume 4. "pd.csi.storage.gke.io" failed: rpc error: code = InvalidArgument desc = ControllerExpandVolume failed to resize disk: failed to resize zonal volume Key{"pvc-6c8daf11-e550-4371-bd3d-cace223d3590", zone: "us-central1-b"}: googleapi: Error 400: Requested provisioned IOPS cannot be smaller than 2500., badRequest 5.Test on clone feature with original volume capacity is 6Gi, issue reproduced.
Actual results:
Expected results:
Additional info:
- blocks
-
CNV-56518 Clone populator is stuck forever when VolumeSnapshot is not Ready
-
- Verified
-
-
CNV-59689 [4.19] Clone populator is stuck forever when VolumeSnapshot is not Ready
-
- Closed
-
- depends on
-
OCPBUGS-62116 [GCP-PD] Hyperdisk volume original size need to be larger than 6Gi when do resize/clone operation
-
- ASSIGNED
-
- is related to
-
STOR-2043 GCP PD CSI support for C3 instance type with hyperdisk-balanced disk
-
- Closed
-
-
STOR-2042 GCP PD CSI support for N4 instance type with hyperdisk-balanced disk
-
- Closed
-
-
CNV-64421 [QE][storage] adjust tier2 sizing
-
- Testing
-
-
CNV-38938 [QE][Storage] run tier1 on GCP with baremetal nodes
-
- Closed
-
- relates to
-
OCPBUGS-53401 [GCP-PD] Hyperdisk volume smaller than 4Gi cannot be created
-
- Closed
-
- links to