-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
issue dropping a rds event subscription #9368
Comments
Related to issue #9243 - I still have the issue even though I used provider 2.19: I just ran into the same issue using version2.19.0 - the destroy removed the event from AWS but left the entry in the statefile:
Terraform has been successfully initialized! aws_db_event_subscription.EventSubscriptionAlarmInstance: Refreshing state... (ID: isg-mysql-demo4-eventsubscriptionalarminstance) Error: Error refreshing state: 1 error(s) occurred:
Statefile: |
Team , please fix this asap as it is impacting a lot. |
This appears to be another RDS API update that is being deployed out into certain regions. For example, this is reproducible in our acceptance testing in us-west-2:
us-east-1:
Given this is already reproducible in the acceptance testing, I should be able to submit a fix shortly that will get included in this week's Terraform AWS Provider release. |
…s during Read and Deletion Reference: #9368 Previously (in us-gov-west-1 and us-east-1): ``` --- FAIL: TestAccAWSDBEventSubscription_basicUpdate (1228.44s) testing.go:629: Error destroying resource! WARNING: Dangling resources may exist. The full state and error is shown below. Error: errors during apply: error waiting for RDS Event Subscription (tf-acc-test-rds-event-subs-2201031712637090321) deletion: SubscriptionNotFound: Event Subscription tf-acc-test-rds-event-subs-2201031712637090321 not found. ``` Output from acceptance testing in AWS Commercial: ``` --- PASS: TestAccAWSDBEventSubscription_withPrefix (535.76s) --- PASS: TestAccAWSDBEventSubscription_importBasic (537.39s) --- PASS: TestAccAWSDBEventSubscription_withSourceIds (539.77s) --- PASS: TestAccAWSDBEventSubscription_disappears (543.52s) --- PASS: TestAccAWSDBEventSubscription_categoryUpdate (944.42s) --- PASS: TestAccAWSDBEventSubscription_basicUpdate (945.75s) ``` Output from acceptance testing in AWS GovCloud (US): ``` --- PASS: TestAccAWSDBEventSubscription_withPrefix (622.68s) --- PASS: TestAccAWSDBEventSubscription_importBasic (623.98s) --- PASS: TestAccAWSDBEventSubscription_withSourceIds (628.56s) --- PASS: TestAccAWSDBEventSubscription_disappears (631.20s) --- PASS: TestAccAWSDBEventSubscription_basicUpdate (978.81s) --- PASS: TestAccAWSDBEventSubscription_categoryUpdate (978.91s) ```
Fix submitted: #9371 |
The fix to have the resource appropriately handle the |
The fix to the For further feature requests or bug reports with this resource, please create a new GitHub issue following the template for triage. Thanks! |
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! |
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
Actual Behavior
Steps to Reproduce
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: