-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
provider/openstack: Remove default egress rule from Security Group on creation #9799
Comments
Thanks for the report. I do see some default security group rules being created, but not specifically for a Here's the output that I see:
I'll dig into this a bit more and see if I can find a resolution. |
Hi @jtopjian, The default security group I mean is the ANY:ANY for egress below. The rule for 10.0.0.0/8 is the one I'm trying to add.
I'm wondering why the content of the default security group rule you see is different than mine but I don't have another Openstack installation to test this further. According to the documentation what I'm seeing, which mimics AWS behavior, is to be expected:
|
@gpaggi Ah, understood. Thanks for the notes. Do you know what version of Neutron your cloud is using? As well, do you know what plugins it's using? |
Yes, we are using Liberty with Contrail plugin but I understood from my colleague that it shouldn't be relevant. |
Right, it shouldn't, but I was asking just incase + collecting as much info as I can. |
We would also be interested in getting this patched in. I was taking a look at what the aws provider did and it appears that they remove the default rules on group creation letting terraform handle all rules. |
+1 |
Hi all, Sorry for the delay. #11466 should fix this. |
This commit modifies the behavior implemented in hashicorp#9799 by enabling the user to be able to toggle the creation of the default security group rules.
This commit modifies the behavior implemented in hashicorp#9799 by enabling the user to be able to toggle the creation of the default security group rules.
This commit modifies the behavior implemented in hashicorp#9799 by enabling the user to be able to toggle the creation of the default security group rules.
…ashicorp#12119) This commit modifies the behavior implemented in hashicorp#9799 by enabling the user to be able to toggle the creation of the default security group rules.
For the record, here is the place in the code where those rules are created:
|
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. |
Hi there,
Terraform Version
Terraform v0.7.8
Affected Resource(s)
openstack_networking_secgroup_v2
openstack_networking_secgroup_rule_v2
Terraform Configuration Files
Expected Behavior
Terraform should create a security group with one egress rule limiting TCP traffic to only 10.0.0.0/8.
Actual Behavior
On security group creation, a default egress ANY:ANY is added by Neutron next to the one managed by TF.
This makes it impossible to manage egress rules from TF, since they are overridden by the default egress rule.
Steps to Reproduce
Apply the TF code above.
References
This was fixed for the AWS provider in #1765
Is it possible to have the same fix implemented for the Openstack provider?
Thanks!
The text was updated successfully, but these errors were encountered: