Bug 1952009
| Summary: | [aws ebs in-tree plugin] events for io1 type storage is not clear | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Qin Ping <piqin> |
| Component: | Storage | Assignee: | aos-storage-staff <aos-storage-staff> |
| Storage sub component: | Kubernetes External Components | QA Contact: | Qin Ping <piqin> |
| Status: | CLOSED WONTFIX | Docs Contact: | |
| Severity: | low | ||
| Priority: | unspecified | CC: | aos-bugs, jsafrane |
| Version: | 4.8 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-04-27 14:34:40 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Yes, the message is confusing, but IMO it was always like this and nobody has complained. I am closing it, as we're moving towards CSI. |
Description of problem: when create a invalid PVC with io1 type storage, the events are not clear Version-Release number of selected component (if applicable): 4.8.0-fc.0 How reproducible: Always Steps to Reproduce: 1. Create a storageclass as: kind: StorageClass apiVersion: storage.k8s.io/v1 metadata: name: sc1-vtsag provisioner: kubernetes.io/aws-ebs parameters: type: io1 iopsPerGB: '400000' 2. Create a PVC as: { "kind": "PersistentVolumeClaim", "apiVersion": "v1", "metadata": { "name": "pvc1-vtsag", "annotations": {}, "labels": { "name": "dynamic-pvc" } }, "spec": { "accessModes": [ "ReadWriteOnce" ], "resources": { "requests": { "storage": "4Gi" } }, "storageClassName": "sc1-vtsag" } } 3. Check the event Actual results: Warning ProvisioningFailed <invalid> persistentvolume-controller Failed to provision volume with StorageClass "sc1-vtsag": InvalidParameterValue: Iops to volume size ratio of 16000.000000 is too high; maximum is 50 status code: 400, request id: 61687148-6728-410a-b3c5-fe1f8faf103f Expected results: The csi event is more clear, like: Warning ProvisioningFailed <invalid> ebs.csi.aws.com_ip-10-0-146-24_2d5241f1-57a7-4310-abbd-f2d153116c48 failed to provision volume with StorageClass "sc1-xjrfz": rpc error: code = Internal desc = Could not create volume "pvc-93e6825a-4174-435d-8eb6-899947edbbd4": could not create volume in EC2: InvalidParameterValue: Volume iops of 1600000 is too high; maximum is 64000. Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info: