Bug 1691208
Summary: | [cloud] For volume io1, the minimum of iops should be 100 instead of 1 | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | sunzhaohua <zhsun> |
Component: | Cloud Compute | Assignee: | Jan Chaloupka <jchaloup> |
Status: | CLOSED ERRATA | QA Contact: | sunzhaohua <zhsun> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 4.1.0 | CC: | agarcial, aos-cloud, jchaloup, mgugino |
Target Milestone: | --- | ||
Target Release: | 4.1.0 | ||
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: | 2019-06-04 10:46:16 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: |
Description
sunzhaohua
2019-03-21 06:49:46 UTC
> E0321 05:50:10.196648 1 instances.go:310] Error creating EC2 instance: VolumeIOPSLimit: Volume iops of 0 is too low; minimum is 1.
We do not have control over the error message. It's reported by the AWS client itself. We are only wiring the message down the logs.
Why is the minimum expected to be 100 instead of 1?
I tried according the doc https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html and the code https://github.com/enxebre/cluster-api-provider-aws-2/blob/e8362ca5a52914921d0d20d9c89b870e48285dc1/pkg/apis/awsproviderconfig/v1alpha1/awsmachineproviderconfig_types.go#L191 And from the aws webconsole createVolume show that the minimum is 100. https://ap-southeast-1.console.aws.amazon.com/ec2/v2/home?region=ap-southeast-1#CreateVolume: I think in this case, docs are wrong, probably should go with what the API thinks is valid. I'd prefer not to have to code around these types of things because that code may get stale in the future. What if they decide to say 25 is the minimum at some later point? Better to let the upstream API make the determination. Perhaps we should update our code comment to reflect. The same comment is also in the latest openshift/cluster-api-provider-aws: https://github.com/openshift/cluster-api-provider-aws/blob/master/pkg/apis/awsproviderconfig/v1beta1/awsmachineproviderconfig_types.go#L193 Yeah, we need to re-phrase the comment and just re-direct a reader to the upstream docs. Verified. clusterversion: 4.0.0-0.9 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758 |