-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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]: 5.5: database host is evaluated to null #32179
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
We ran into the same issue and looking into the terraform state, the status of the created instance is In our case the instance was newly created using |
I can reproduce this in our acceptance tests: % make testacc TESTARGS='-run=TestAccRDSInstance_identifierPrefix\|TestAccRDSInstance_identifierGenerated' PKG=rds
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/rds/... -v -count 1 -parallel 20 -run=TestAccRDSInstance_identifierPrefix\|TestAccRDSInstance_identifierGenerated -timeout 180m
=== RUN TestAccRDSInstance_identifierPrefix
=== PAUSE TestAccRDSInstance_identifierPrefix
=== RUN TestAccRDSInstance_identifierGenerated
=== PAUSE TestAccRDSInstance_identifierGenerated
=== CONT TestAccRDSInstance_identifierPrefix
=== CONT TestAccRDSInstance_identifierGenerated
=== NAME TestAccRDSInstance_identifierPrefix
instance_test.go:188: Step 2/2 error running import: ImportStateVerify attributes not equivalent. Difference is shown below. The - symbol indicates attributes missing after import.
map[string]string{
+ "address": "tf-acc-test-prefix-20230629185347776800000002.cvflxcqblmy1.us-west-2.rds.amazonaws.com",
+ "endpoint": "tf-acc-test-prefix-20230629185347776800000002.cvflxcqblmy1.us-west-2.rds.amazonaws.com:3306",
+ "hosted_zone_id": "Z1PVIF0B656C1W",
- "port": "0",
+ "port": "3306",
- "status": "creating",
+ "status": "available",
}
--- FAIL: TestAccRDSInstance_identifierPrefix (425.76s)
--- PASS: TestAccRDSInstance_identifierGenerated (547.74s)
FAIL
FAIL github.com/hashicorp/terraform-provider-aws/internal/service/rds 552.980s
FAIL
make: *** [testacc] Error 1 |
This functionality has been released in v5.6.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! |
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. |
Terraform Core Version
1.5.0
AWS Provider Version
5.5.0
Affected Resource(s)
No response
Expected Behavior
Working fine
Actual Behavior
I'm using the database host in other configurations. But after the recent release of version 5.5, I got this weird error:
The module is defined this way:
Related plan:
And it is created with no issues:
Nothing special. I believe this is related to #31594 when the provider decides that the database is ready when it is not ready.
Restarting the same deployment with no changes fixes the issue.
The text was updated successfully, but these errors were encountered: