You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Error revoking security group sg-9136df35 rules: InvalidPermission.NotFound: The specified rule does not exist in this security group.
status code: 400, request id: []
Error applying plan:
1 error(s) occurred:
* 1 error(s) occurred:
* 1 error(s) occurred:
* Error revoking security group sg-9136df35 rules: InvalidPermission.NotFound: The specified rule does not exist in this security group.
status code: 400, request id: []
After I manually modified security group sg-9136df35 from AWS console to allow all TCP traffic 'terraform destroy' worked fine.
The text was updated successfully, but these errors were encountered:
Issue for some reason persists in 0.5.3 even with 0-0 range. Seems like the issue with "self" reference, because the following works:
Note absence of "self" reference and adding SG source back to itself.
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 27, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@catsby
Terraform version 0.5.3
This is NOT a duplicate of #1985 (#1985)
#2305 only fixes a specific use case where:
Following case is still broken (note specific port number range):
Error:
After I manually modified security group sg-9136df35 from AWS console to allow all TCP traffic 'terraform destroy' worked fine.
The text was updated successfully, but these errors were encountered: