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

Cannot create rich rule with reject type #193

Closed
bmagistro opened this issue Nov 18, 2018 · 1 comment · Fixed by #329
Closed

Cannot create rich rule with reject type #193

bmagistro opened this issue Nov 18, 2018 · 1 comment · Fixed by #329

Comments

@bmagistro
Copy link
Contributor

bmagistro commented Nov 18, 2018

Using the following:
Puppet Agent: 5.5.3
Puppet Server: 5.3.4
firewalld module: master (issue exists on 3.4.0 too)

Using the following rich rule, puppet continually returns an error. I have't been able to track down the cause yet. Zone is present and has other rich rules associated. Under master, I get "Rule action hash should contain 'action' and 'type' keys. ... Got { "action"=>"reject", "type"=>"icmp-net-unreachable"}. Changing "lib/puppet_x/firewalld/property/rich_rule_action.rb" line 10 to if value.keys.sorted != ["action", "type"] I can get past this but then get "Authorized action values are ... got" implying something from the hash isn't being access/passed cleanly.

firewalld_rich_rule { 'rich_rule':
  ensure => 'present',
  zone => 'myzone',
  port => { 'port' => 12345, 'protocol' => 'tcp', },
  action => { 'action' => 'reject', 'type' => 'icmp-net-unreachable', },
}

Edit: Light clicked on, after some more experimenting, another change in the file mentioned above and two changes to "lib/puppet/provider/firewall_rich_rule/firewall_cmd.rb" I can get it working. Will look at creating a PR with these changes.

bmagistro added a commit to bmagistro/puppet-firewalld that referenced this issue Nov 30, 2018
@bmagistro
Copy link
Contributor Author

Checking in:
OS: CentOS 7.9
Puppet Server: 6.19.0
Puppet Agent: 6.27.1
firewalld (module): v4.4.0

It looks like this is still an issue. Will try to take my old changes and turn this into a proper PR

bmagistro pushed a commit to bmagistro/puppet-firewalld that referenced this issue Jun 24, 2022
bmagistro pushed a commit to bmagistro/puppet-firewalld that referenced this issue Jun 26, 2022
Signed-off-by: Ben Magistro <koncept1@gmail.com>
bmagistro added a commit to bmagistro/puppet-firewalld that referenced this issue Jun 26, 2022
Signed-off-by: Ben Magistro <koncept1@gmail.com>
bmagistro added a commit to bmagistro/puppet-firewalld that referenced this issue Jun 26, 2022
Fixes: voxpupuli#193
Replaces: voxpupuli#194

Signed-off-by: Ben Magistro <koncept1@gmail.com>
jcpunk pushed a commit that referenced this issue Aug 24, 2023
Signed-off-by: Ben Magistro <koncept1@gmail.com>
jcpunk pushed a commit that referenced this issue Aug 24, 2023
Fixes: #193
Replaces: #194

Signed-off-by: Ben Magistro <koncept1@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant