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

Aurora Cluster instance update "storage-optimization" state is not implemented #6455

Closed
alberts-s opened this issue Nov 13, 2018 · 3 comments · Fixed by #21900
Closed

Aurora Cluster instance update "storage-optimization" state is not implemented #6455

alberts-s opened this issue Nov 13, 2018 · 3 comments · Fixed by #21900
Assignees
Labels
bug Addresses a defect in current functionality. service/rds Issues and PRs that pertain to the rds service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Milestone

Comments

@alberts-s
Copy link

alberts-s commented Nov 13, 2018

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 "me too" comments, 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

  • v0.11.8

Provaider Version

  • v1.27 - the available RDS states have not been changed after v1.27

Affected Resource(s)

  • aws_rds_cluster_instance

Expected Behavior

States listed in AWS provider aws_rds_cluster_instance resource should contain "storage-optimization" state and the instance update should not abruptly fail.

Actual Behavior

Whilst applying the database instance type change the following error is shown:
aws_rds_cluster_instance.instance.0: unexpected state 'storage-optimization', wanted target 'available'. last error: %!s(<nil>)

Steps to Reproduce

  • Create AWS RDS Aurora MySQL 5.7 cluster with 2 instances with the following instance types
    • r4.2xlarge
    • r4.2xlarge
  • Increase size of one of the instances to r4.4xlarge
  • During applying of the change Terraform will fail update due to unknown state

Important Factoids

  • All available states for RDS instances are documented here.
@bflad bflad added the service/rds Issues and PRs that pertain to the rds service. label Nov 14, 2018
@aeschright aeschright added the needs-triage Waiting for first response or review from a maintainer. label Jun 24, 2019
@bflad bflad added bug Addresses a defect in current functionality. and removed needs-triage Waiting for first response or review from a maintainer. labels Nov 13, 2019
@github-actions
Copy link

github-actions bot commented Nov 3, 2021

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Nov 3, 2021
@YakDriver YakDriver self-assigned this Nov 24, 2021
@github-actions github-actions bot added this to the v3.67.0 milestone Nov 25, 2021
@github-actions
Copy link

github-actions bot commented Dec 1, 2021

This functionality has been released in v3.67.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. Thank you!

@github-actions
Copy link

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/rds Issues and PRs that pertain to the rds service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants