-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
[Bug]: aws_msk_cluster error out updating ebs_volume_info though there is no change #37043
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Maybe similar #20327 |
confirmed same problem while trying to upgrade from 4.20.1 -> 5.47.0 of the AWS provider. |
looks like this is related to #26031 |
Warning This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
This functionality has been released in v5.84.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! |
Terraform Core Version
1.5.3
AWS Provider Version
5.46.0
Affected Resource(s)
aws_msk_cluster
Expected Behavior
aws_msk_cluster broker_node_group_info storage_info ebs_storage_info should not be updated if there is no change
Actual Behavior
terraform is adding provisioned_throughput to eb_storage_info though it is null and eventually error out
Relevant Error/Panic Output Snippet
broker storage: operation error Kafka: UpdateBrokerStorage, https response error StatusCode: 400, RequestID: a58ed9fd-5102-462c-a77e-d5972fc821cf, BadRequestException: The request does not include any updates to the EBS volumes of the cluster. Verify the request, then try again.
If voulme_storage variable value is increased and reapplied, this error doesn't occur
Terraform Configuration Files
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: