Skip to content
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

Unable to add inline rules to aws_default_security_group permanently #10019

Closed
nicoleyson opened this issue Sep 6, 2019 · 4 comments
Closed
Assignees
Labels
service/ec2 Issues and PRs that pertain to the ec2 service.

Comments

@nicoleyson
Copy link

nicoleyson commented Sep 6, 2019

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

Terraform v0.12.8
+ provider.archive v1.2.2
+ provider.aws v2.26.0
+ provider.datadog v2.3.0
+ provider.http v1.1.1
+ provider.pagerduty v1.4.0

Affected Resource(s)

  • aws_default_security_group

Terraform Configuration Files

resource "aws_default_security_group" "default" {
  vpc_id = module.vpc.vpc_id
  egress {
    from_port        = 443
    to_port          = 443
    protocol         = "tcp"
    cidr_blocks      = ["0.0.0.0/0"]
    ipv6_cidr_blocks = ["::/0"]
    description      = "Allows HTTPS outbound to any IP"
  }
}

Debug Output

Panic Output

Expected Behavior

terraform apply -> adds the rules to the default security group
a subsequent terraform apply -> no changes should occur

Actual Behavior

terraform apply -> adds the rules to the default security group
terraform apply -> tries to remove rules from the default security group
terraform apply -> adds the rules back again
image

image

I've also tried terraform destroy --target aws_default_security_group.default and applying again, but the results were the same.

Steps to Reproduce

terraform apply
terraform apply

Important Factoids

References

The behavior seems similar to:
#2069
#3628
#4410

(Edit 9/23):
It appears as though it's happening now to normal security groups as well, leading me to believe it's a general issue with inline rules?
#370
#10097

@ghost ghost added the service/ec2 Issues and PRs that pertain to the ec2 service. label Sep 6, 2019
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Sep 6, 2019
@gdavison gdavison self-assigned this Aug 12, 2020
@gdavison
Copy link
Contributor

Hi @nicoleyson, are you still seeing this error? I'm not able to reproduce it, but unfortunately it has been some time since you reported this.

@gdavison gdavison added waiting-response Maintainers are waiting on response from community or contributor. and removed needs-triage Waiting for first response or review from a maintainer. labels Aug 12, 2020
@nicoleyson
Copy link
Author

nicoleyson commented Aug 16, 2020

Hi @gdavison! I have not had the time to attempt to reproduce this yet, because I no longer have access to the repository that this was an issue in.
But I do see that in similar issues, people are reporting it is still an issue in 0.12 this year:

I will let you know if I get the chance to attempt to reproduce. But if it makes it easier on you, because I know this repository has a ton of issues, feel free to close this and maybe someone can reopen it if the issue persists?
It's no longer a pressing issue for me, personally.

@ghost ghost removed the waiting-response Maintainers are waiting on response from community or contributor. label Aug 16, 2020
@gdavison
Copy link
Contributor

Thanks for the reply, @nicoleyson. I'll close this issue. If anyone encounters it in the future, they can open a new issue and link this one for additional context.

@ghost
Copy link

ghost commented Sep 26, 2020

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 ghost locked and limited conversation to collaborators Sep 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
service/ec2 Issues and PRs that pertain to the ec2 service.
Projects
None yet
Development

No branches or pull requests

2 participants