-
Notifications
You must be signed in to change notification settings - Fork 348
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.
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
ec2_vol
sets all volumes with an iops
field to be io1
#330
Comments
Files identified in the description: If these files are inaccurate, please update the |
Files identified in the description:
If these files are inaccurate, please update the |
Another possible result of this bug:
|
It was a long journey to implement modifying ec2 volumes using |
yeah, it was not covered by integration tests :-/ |
SUMMARY
It seems that any volume created via
amazon.aws.ec2_vol
with aniops
field specified gets its type changed toio1
, even though both theio2
andgp3
disk types allow for variable IOPS as well.See here:
amazon.aws/plugins/modules/ec2_vol.py
Lines 417 to 418 in 8011d3a
ISSUE TYPE
COMPONENT NAME
https://github.com/ansible-collections/amazon.aws/blob/8011d3a0dc83857ef75f8a19650441a59f9e10f7/plugins/modules/ec2_vol.py
ANSIBLE VERSION
STEPS TO REPRODUCE
EXPECTED RESULTS
A new
gp3
disk gets created with 4000 IOPS instead of the default 3000.ACTUAL RESULTS
A new
io1
disk gets created with 4000 IOPS.The text was updated successfully, but these errors were encountered: