AWS aurora unexpected state 'configuring-iam-database-auth' when modifying the iam_database_authentication_enabled flag

[reegnz]

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

Terraform v0.12.9
AWS provider v2.29.0

Affected Resource(s)

• aws_rds_cluster

Expected Behavior

Terraform should have waited for the database to have the iam-authentication enabled.

Actual Behavior

I got this error:

Error: error waiting for RDS Cluster (playground-aurora-db-postgres) to be available: unexpected state 'configuring-iam-database-auth', wanted target 'available'. last error: %!s(<nil>)

  on main.tf line 27, in resource "aws_rds_cluster" "this":
  27: resource "aws_rds_cluster" "this" {


Releasing state lock. This may take a few moments...

Steps to Reproduce

1. provision an rds aurora database (postgres v10.7) with the apply_immediately flag.
2. once provisioned, add iam_database_authentication_enabled = true flag and try to reprovision

[tecnobrat]

I took a look at the code, this looks like its missing from the state transitions for rds_cluster_instance but not for db_instance:

Missing: https://github.com/terraform-providers/terraform-provider-aws/blob/e903501d82b3d83a5342deb4ec2df95732d61ba5/aws/resource_aws_rds_cluster_instance.go#L629-L639

Does exist: https://github.com/terraform-providers/terraform-provider-aws/blob/e903501d82b3d83a5342deb4ec2df95732d61ba5/aws/resource_aws_db_instance.go#L1774

[ldalorion]

Any updates on this issue? Currently seeing this with terraform version 0.13.5 and hashicorp/aws v3.22.0.

[ghost]

This has been released in version 3.32.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!

[azhurbilo]

The same issue reproduced with 3.33 aws provider

unexpected state 'configuring-iam-database-auth', wanted target 'available'

@bill-rich could you reopen?

[bill-rich]

Hi @azhurbilo! I wasn't able to reproduce this problem with v3.33. Can you please provide an example configuration and steps to reproduce it?

[azhurbilo]

@bill-rich thnx for checking. now I don't have candidate DB for an upgrade to reproduce it. you can close issue, if I face with unexpected state one more time, I will share the config with you

[bill-rich]

That sounds good. Thank you!

[ghost]

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!