Hi Team,

  During execution of the puppet agent I got the following error when 
applying the puppetlabs-firewall module:

 Error: 
/Stage[main]/Profile::Firewall::Purge_unmanaged/Resources[firewallchain]: 
Failed to generate additional resources using 'generate': Parameter name 
failed on Firewallchain[INPUT:security:IPv4]: Inbuilt chains must be in the 
form {chain}:{table}:{protocol} where {table} is one of FILTER, NAT, 
MANGLE, RAW, RAWPOST, BROUTE or empty (alias for filter), chain can be 
anything without colons or one of PREROUTING, POSTROUTING, BROUTING, INPUT, 
FORWARD, OUTPUT for the inbuilt chains, and {protocol} being IPv4, IPv6, 
ethernet (ethernet bridging) got 'INPUT:security:IPv4' table:'' chain:'' 
protocol:''
/opt/puppetlabs/puppet/cache/lib/puppet/type/firewallchain.rb:44:in `block 
(3 levels) in <top (required)>'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parameter.rb:452:in 
`validate'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parameter.rb:487:in 
`value='
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:673:in `[]='
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:2411:in 
`set_name'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:2383:in 
`initialize'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:1178:in `new'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:1178:in `block 
(2 levels) in instances'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:1168:in `collect'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:1168:in `block 
in instances'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:1161:in `collect'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:1161:in 
`instances'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/resources.rb:111:in 
`generate'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/additional_resource_generator.rb:19:in
 
`generate_additional_resources'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:84:in 
`block in evaluate'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:84:in 
`each'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:84:in 
`evaluate'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:222:in 
`block in apply'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/log.rb:155:in 
`with_destination'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/report.rb:118:in 
`as_logging_destination'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:221:in 
`apply'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:171:in 
`block in apply_catalog'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:223:in `block in 
benchmark'
/opt/puppetlabs/puppet/lib/ruby/2.1.0/benchmark.rb:294:in `realtime'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:222:in 
`benchmark'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:170:in 
`apply_catalog'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:315:in 
`run_internal'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:186:in 
`block in run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in 
`override'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:240:in `override'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:185:in 
`run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/agent.rb:45:in `block (4 
levels) in run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/agent/locker.rb:21:in 
`lock'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/agent.rb:45:in `block (3 
levels) in run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/agent.rb:98:in 
`with_client'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/agent.rb:42:in `block (2 
levels) in run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/agent.rb:65:in 
`run_in_fork'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/agent.rb:41:in `block in 
run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:179:in 
`call'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:179:in 
`controlled_run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/agent.rb:39:in `run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/agent.rb:353:in 
`onetime'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/agent.rb:331:in 
`run_command'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:344:in 
`block in run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:540:in 
`exit_on_fail'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:344:in 
`run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:128:in 
`run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in 
`execute'
/opt/puppetlabs/puppet/bin/puppet:5:in `<main>'

My Operating systems is RHEL 7.2, running 
kernel 3.10.0-327.18.2.el7.x86_64. My using the latest puppetlabs-firewall 
module version 1.8.1.

I can see that there has been two bug tickets raised on Puppet's jira to 
look into this issue:

1 -  https://tickets.puppetlabs.com/browse/MODULES-1736 - Issue reported on 
 RHEL 5 and puppetlabs-firewall version 1.4.0

2 - https://tickets.puppetlabs.com/browse/MODULES-2769 - Issue reported on 
Centos 7, iptables-1.4.21-13

Both tickets deal with the same issue and neither of those fixes have been 
delivered as yet on the latest puppet-firewall module version 1.8.1. 

I am wondering if anyone has found the same issue and got to fix it. I also 
want to know what puppetlabs-firewall the release a fix for this bug will 
be delivered.

Thanks !

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/9e0f2175-a04b-4779-badd-bc6607daaf5f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to