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

provider/openstack: Can not create firewall rule with "any" protocol #7507

Closed
carlpett opened this issue Jul 6, 2016 · 4 comments · Fixed by #9617
Closed

provider/openstack: Can not create firewall rule with "any" protocol #7507

carlpett opened this issue Jul 6, 2016 · 4 comments · Fixed by #9617
Labels

Comments

@carlpett
Copy link
Contributor

carlpett commented Jul 6, 2016

Terraform Version

Terraform v0.7.0-rc2

Affected Resource(s)

  • openstack_fw_rule_v1

Terraform Configuration Files

resource "openstack_fw_rule_v1" "test-case" {
  name = "test-case"
  action = "allow"
  protocol = "any"
  destination_ip_address = "1.1.1.2"
  source_ip_address = "1.1.1.1"
  enabled = "true"
}

Expected Behavior

Create rule with protocol any

Actual Behavior

Expected HTTP response code [201 202] when accessing [POST https://OPENSTACK-PROVIDER:9696/v2.0/fw/firewall_rules], but got 400 instead {"NeutronError": {"message": "Firewall Rule protocol any is not supported. Only protocol values [None, 'tcp', 'udp', 'icmp'] and their integer representation (0 to 255) are supported.", "type": "FirewallRuleInvalidProtocol", "detail": ""}}

Setting protocol = "" gives A protocol is required (tcp, udp, icmp or any), and protocol = "0" (since the error message indicated that numerals would be accepted) gives Invalid input for protocol. Reason: '0' is not in [None, 'tcp', 'udp', 'icmp']

@carlpett
Copy link
Contributor Author

carlpett commented Jul 6, 2016

Actually, this seems to be more of a Gophercloud issue. I created a matching issue there: rackspace/gophercloud#605

@jtopjian
Copy link
Contributor

@carlpett Looping back around to this one. I have a PR opened here: gophercloud/gophercloud#162

@carlpett
Copy link
Contributor Author

Great work!

@ghost
Copy link

ghost commented Apr 21, 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 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 ghost locked and limited conversation to collaborators Apr 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants