Skip to content
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

Minimum AWS FSx size is set to 3600GB instead of 1200GB #11828

Closed
giacomodabisias opened this issue Jan 31, 2020 · 5 comments · Fixed by #11847
Closed

Minimum AWS FSx size is set to 3600GB instead of 1200GB #11828

giacomodabisias opened this issue Jan 31, 2020 · 5 comments · Fixed by #11847
Labels
enhancement Requests to existing resources that expand the functionality or scope. good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. service/fsx Issues and PRs that pertain to the fsx service.
Milestone

Comments

@giacomodabisias
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

Terraform v0.12.20

Affected Resource(s)

AWS FSx

  • aws_fsx_lustre_file_system

Debug Output

Error: module.onebox.aws_fsx_lustre_file_system.permanent_storage: expected storage_capacity to be at least (3600), got 1200

Expected Behavior

Creation of an FSx filesystem with 1200GB capacity

Actual Behavior

produced an error message stating that the minimum capacity is 3600GB

Steps to Reproduce

Create an FSx filesystem

resource "aws_fsx_lustre_file_system" "fsx_storage" {
storage_capacity = 1200
subnet_ids = ["test_subnet"]
}

Important Factoids

References

AWS announcement about the size decrease:
https://aws.amazon.com/about-aws/whats-new/2019/09/amazon-fsx-lustre-reduces-minimum-file-system-size/

  • #0000
@ghost ghost added the service/fsx Issues and PRs that pertain to the fsx service. label Jan 31, 2020
@giacomodabisias giacomodabisias changed the title Minimum Luster size is set to 3600GB instead of 1200 Minimum AWS FSx size is set to 3600GB instead of 1200 Jan 31, 2020
@giacomodabisias giacomodabisias changed the title Minimum AWS FSx size is set to 3600GB instead of 1200 Minimum AWS FSx size is set to 3600GB instead of 1200GB Jan 31, 2020
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Jan 31, 2020
@bflad bflad added enhancement Requests to existing resources that expand the functionality or scope. good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. and removed needs-triage Waiting for first response or review from a maintainer. labels Jan 31, 2020
@bflad
Copy link
Contributor

bflad commented Jan 31, 2020

For inspiration on how to address this, please see the similar decrease that was made in the aws_fsx_windows_file_server resource here: #11272

@giacomodabisias
Copy link
Author

@bflad thanks.
Can I just move on with this and make a PR for it?

@bflad bflad added this to the v2.48.0 milestone Feb 6, 2020
@bflad
Copy link
Contributor

bflad commented Feb 6, 2020

The validation update has been merged and will release with version 2.48.0 of the Terraform AWS Provider, tomorrow. Thanks to @slapula for the implementation. 👍

@ghost
Copy link

ghost commented Feb 7, 2020

This has been released in version 2.48.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks!

@ghost
Copy link

ghost commented Mar 27, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. service/fsx Issues and PRs that pertain to the fsx service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants