resource/aws_launch_configuration: Prevent ResourceInUse errors caused by eventual consistency during deletion #7819
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…d by eventual consistency during deletion References: * #502 * #646 Also discovered during acceptance testing, which was no longer present after this change: ``` --- FAIL: TestAccAWSAutoScalingGroup_basic (233.37s) testing.go:599: Error destroying resource! WARNING: Dangling resources may exist. The full state and error is shown below. Error: Error applying: 1 error occurred: * aws_launch_configuration.foobar (destroy): 1 error occurred: * aws_launch_configuration.foobar: ResourceInUse: Cannot delete launch configuration terraform-20190305190002502900000001 because it is attached to AutoScalingGroup terraform-test-xkagj2tcwm ``` It appears the Autoscaling service can display an eventual consistency delay between when an Autoscaling Group requiring a Launch Configuration is deleted and deleting the Launch Configuration immediately after. Output from acceptance testing: ``` --- PASS: TestAccAWSLaunchConfiguration_importBasic (14.18s) --- PASS: TestAccAWSLaunchConfiguration_withSpotPrice (15.10s) --- PASS: TestAccAWSLaunchConfiguration_ebs_noDevice (16.20s) --- PASS: TestAccAWSLaunchConfiguration_withBlockDevices (17.60s) --- PASS: TestAccAWSLaunchConfiguration_withEncryption (19.82s) --- PASS: TestAccAWSLaunchConfiguration_userData (26.26s) --- PASS: TestAccAWSLaunchConfiguration_basic (28.43s) --- PASS: TestAccAWSLaunchConfiguration_updateEbsBlockDevices (30.24s) --- PASS: TestAccAWSLaunchConfiguration_updateRootBlockDevice (31.82s) --- PASS: TestAccAWSLaunchConfiguration_withIAMProfile (35.39s) --- PASS: TestAccAWSLaunchConfiguration_withVpcClassicLink (37.53s) ```
bflad
added
bug
|
This has been released in version 2.1.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
|
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! |
ghost
locked and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #502
Closes #646
Also discovered during acceptance testing, which was no longer present after this change:
It appears the Autoscaling service can display an eventual consistency delay between when an Autoscaling Group requiring a Launch Configuration is deleted and deleting the Launch Configuration immediately after.
Output from acceptance testing: