resource/aws_servicequotas_service_quota: Remove resource from Terraform state on NoSuchResourceException error #10735
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
…orm state on NoSuchResourceException error Reference: https://aws.amazon.com/blogs/compute/preview-vcpu-based-instance-limits/ Recently, AWS EC2 removed certain instance service quotas: > Beginning October 24, 2019, all accounts will switch to vCPU-based instance limits, and the current count-based instance limits will no longer be supported. These may have been managed previously by Terraform configurations, however they now return the following error (as would any other quotas removed in the future): ``` Error: error getting Service Quotas Service Quota (ec2/L-F26B0BF2): NoSuchResourceException: status code: 400, request id: d37df234-c1eb-420e-abce-a73c6cde2999 ``` Given this error, it is not possible to remove the problematic resource without manually calling `terraform state rm`. The correct behavior in this case is for the Terraform resource to remove itself from the state and propose recreation, which would allow operators to successfully remove the missing quotas from their configurations. This particular change cannot be directly acceptance tested since the availability of quotas is managed by AWS, not a managable resource. Output from acceptance testing (requesting increase of VPC internet gateways and VPCs limits in a personal testing account): ``` export SERVICEQUOTAS_INCREASE_ON_CREATE_QUOTA_CODE=L-A4707A72 export SERVICEQUOTAS_INCREASE_ON_CREATE_SERVICE_CODE=vpc export SERVICEQUOTAS_INCREASE_ON_CREATE_VALUE=6 export SERVICEQUOTAS_INCREASE_ON_UPDATE_QUOTA_CODE=L-F678F1CE export SERVICEQUOTAS_INCREASE_ON_UPDATE_SERVICE_CODE=vpc export SERVICEQUOTAS_INCREASE_ON_UPDATE_VALUE=6 --- PASS: TestAccAwsServiceQuotasServiceQuota_Value_IncreaseOnCreate (13.62s) --- PASS: TestAccAwsServiceQuotasServiceQuota_basic (15.23s) --- PASS: TestAccAwsServiceQuotasServiceQuota_Value_IncreaseOnUpdate (23.09s) ```
ghost
added
size/XS
bflad
deleted the
b-aws_servicequotas_service_quota-NoSuchResourceException
branch
bflad
added a commit
that referenced
this pull request
Nov 15, 2019
|
This has been released in version 2.37.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! |
|
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.
Community Note
Reference: https://aws.amazon.com/blogs/compute/preview-vcpu-based-instance-limits/
Release note for CHANGELOG:
Recently, AWS EC2 removed certain instance service quotas:
These may have been managed previously by Terraform configurations, however they now return the following error (as would any other quotas removed in the future):
Given this error, it is not possible to remove the problematic resource without manually calling
terraform state rm. The correct behavior in this case is for the Terraform resource to remove itself from the state and propose recreation, which would allow operators to successfully remove the missing quotas from their configurations.This particular change cannot be directly acceptance tested since the availability of quotas is managed by AWS, not a managable resource.
Output from acceptance testing (requesting increase of VPC internet gateways and VPCs limits in a personal testing account):