[Puppet Users] firewallchain issues w/ 1.0.0 release

Hi, First, some software versions, just to get them out of the way: - CentOS 5.x through Centos 6.2 - Ruby 1.8.5 - 1.8.7 - Puppet 2.7.19 - Facter 1.6.11 Just a note - we're working from the EPEL repos almost exclusively. I am working with the firewall module, and so far I am unable to use fir

Re: [Puppet Users] firewallchain issues w/ 1.0.0 release

ues w/ 1.0.0 release I believe this is to implement user defined chain-names. It is a way to group firewall rules. Try this for explanation: http://my.safaribooksonline.com/book/operating-systems-and-server-administration/linux/0596004613/networking/linuxsvrhack-chp-4-sect-5 “Sometimes I thin

[Puppet Users] Puppet dashboard - having cached catalog runs show up as warnings

Hi, I have noticed that when a typo is introduced or a module is plain broken, puppet will run using a cached catalog. This is logged as an error on the local client, however, it is not logged as an error on Puppet Dashboard. How can I change this behavior, so that using the cached catalog wi

[Puppet Users] puppetlabs-firewall module - purging unmanaged firewall chains?

Hi, We (my colleagues and I) have a question about using the purge attribute in puppetlabs/firewall 1.1.3. Specifically, the per-chain purge attribute listed here: https://forge.puppetlabs.com/puppetlabs/firewall#050---2014-02-10 If I have this as my node definition: node oogs-test01

Re: [Puppet Users] puppetlabs-firewall module - purging unmanaged firewall chains?

Hi Hunter, Yes, oogs-dev is the master in this case. This environment also has the latest version of puppetlabs/firewall. As for the caching issue, the puppet daemon uses passenger to have multiple copies of the daemon running simultaneously, and they usually reload every 5-10 minutes