Puppet Labs Modules

11/11/2011

10:45 am Bug #9083 (In Topic Branch Pending Review): Puppet-vcsrepo fails on cvs with undefined method `wo...

James Turnbull

10:44 am Bug #10751 (In Topic Branch Pending Review): No way to specify the CVS module to use

James Turnbull

10:40 am Bug #9083: Puppet-vcsrepo fails on cvs with undefined method `working_copy_exists?'

Pull req https://github.com/puppetlabs/puppet-vcsrepo/pull/12
Matthias Pigulla

10:39 am Bug #10751: No way to specify the CVS module to use

Suggested fix https://github.com/puppetlabs/puppet-vcsrepo/pull/13 Matthias Pigulla

10:25 am Bug #10751 (Closed): No way to specify the CVS module to use

The `cvs.rb` provider currently assumes that the `source` attribute ends with the name of the module to be checked ou... Matthias Pigulla

04:49 am Feature #10718 (Accepted): firewall: Add owner matching support for the firewall module

Ken Barber

09:51 pm Bug #10711 (Re-opened): In 0.0.2 of puppetlabs-firewall, source property doesn't grok what '/32' ...

I did figure this out. I have a mixed environment of some CentOS 5 and some CentOS 6. I introduced CentOS 6 at the ... Justin Ellison

11/10/2011

02:41 pm Feature #10723 (In Topic Branch Pending Review): firewall: munge hostnames to cidr

Add a helper method to munge source and destination addresses into the same format as iptables-save output.
Pull r... Jonathan Boyett

02:36 pm Feature #10723 (Closed): firewall: munge hostnames to cidr

Source and destination values accepts hostnames, but hostnames get resolved when inserting a rule which results in th... Jonathan Boyett

02:32 pm Feature #10718: firewall: Add owner matching support for the firewall module

Patch pending from reporter. Jonathan Boyett

12:44 pm Feature #10718 (Closed): firewall: Add owner matching support for the firewall module

It would be super swell to be able to support owner matching ( uid and gid ) in the firewall module Yuri Soviet

12:18 pm Bug #10715 (Merged - Pending Release): ntp: class should fail to compile when platform is not sup...

when the ntp class is used with an unsupported platform, it generates a notify resource.
This event should be a f... Dan Bode

11:24 am Bug #10711 (Closed): In 0.0.2 of puppetlabs-firewall, source property doesn't grok what '/32' means

Scratch that. I'm not sure what, but I have something locally causing this. Justin Ellison

10:55 am Bug #10711 (Duplicate): In 0.0.2 of puppetlabs-firewall, source property doesn't grok what '/32' ...

I'm about 80% sure this didn't happen with 0.0.1, but certainly could be wrong. Given the following resource:
fi... Justin Ellison

10:40 am Feature #10707 (Accepted): ntp: support for amazon linux

When I try to use the ntp module on amazon Linux, I currently get the following message:
defined 'message' as 'The... Dan Bode

11:56 pm Refactor #10372 (Merged - Pending Release): F5: Add spec tests

Ken Barber

11:54 pm Bug #10690 (In Topic Branch Pending Review): Multiport module does not accept multiple options, s...

Ken Barber

11:35 pm Bug #10690 (Accepted): Multiport module does not accept multiple options, so provide 'ports' opti...

Ken Barber

07:00 pm Bug #10700 (In Topic Branch Pending Review): firewall: comment string validation characters

Allow the [:alpha:], [:digit:], [:punct:], and [:space:] POSIX character classes.
Pull request can be found [here]... Jonathan Boyett

06:27 pm Bug #10700 (Closed): firewall: comment string validation characters

The comment property validation does not allow for certain non-alphanumeric characters, such a periods and commas. Jonathan Boyett

06:23 pm Bug #10693 (In Topic Branch Pending Review): firewall: limit may fail if module is not explicitly...

Jonathan Boyett

06:23 pm Bug #10693: firewall: limit may fail if module is not explicitly loaded

Changed the value of :limit in the resource_map.
Pull request can be found [here](https://github.com/puppetlabs/pu... Jonathan Boyett

11/09/2011

03:47 pm Bug #10693 (Closed): firewall: limit may fail if module is not explicitly loaded

The --limit module may cause rule insertion to fail if the module is not loaded (-m limit --limit). Jonathan Boyett

03:44 pm Bug #10690: Multiport module does not accept multiple options, so provide 'ports' option as a wor...

This is applicable for all versions of multiport. Multiport can only accept one option at a time. Pull request can be... Jonathan Boyett

03:30 pm Bug #10690: Multiport module does not accept multiple options, so provide 'ports' option as a wor...

To be clear - this is specifically for iptables 1.3.x right? Ken Barber

03:11 pm Bug #10690 (Closed): Multiport module does not accept multiple options, so provide 'ports' option...

The multiport module does not support multiple options, so the following fails:
<blockquote>
firewall { '001 test... Jonathan Boyett

12:43 pm Feature #10674 (Needs Decision): 'action' property in puppetlabs-firewall has no default, and isn...

Actually the action parameter was never in v0.0.1 either - it was in a pre-release.
So the default was dropped - and... Ken Barber

12:12 pm Feature #10674 (Closed): 'action' property in puppetlabs-firewall has no default, and isn't required

This may be a feature request, feel free to reclassify if so.
With 0.0.1 of puppetlabs-firewall, the default value... Justin Ellison

10:36 am Bug #10654: firewall: Action property still jumping to ACCEPT chain

That's fine, glad we found the issue & always happy to help :-). Ken Barber

10:21 am Bug #10654 (Closed): firewall: Action property still jumping to ACCEPT chain

So, so, sorry.
I found a big fat config error where module path was a list of directories, one of them was my deve... Justin Ellison

09:49 am Bug #10654: firewall: Action property still jumping to ACCEPT chain

Okay - I can replicate it now:
debug: Puppet::Type::Firewall::ProviderIptables: Executing '/sbin/iptables -I I... Ken Barber

09:26 am Bug #10665 (Accepted): firewall: exec is not notified when purging rules

Okay great. Yes - there is still a bug. I've modified the title and description to suit. Ken Barber

08:28 am Bug #10665: firewall: exec is not notified when purging rules

Now it works as you told. Many thanks - great work!
The problem with removed rules not notifying remains.
Michael Arlt

08:02 am Bug #10654: firewall: Action property still jumping to ACCEPT chain

Ken, I think you missed the 'iptables -F' above. I'm actually starting with an empty ruleset now for testing. There... Justin Ellison

07:52 am Bug #10654: firewall: Action property still jumping to ACCEPT chain

> # find /var/lib/puppet/ -name 'puppetlabs-firewall'
> #
>
> Another indicator that I'm using the right ... Ken Barber

07:47 am Bug #10654: firewall: Action property still jumping to ACCEPT chain

This is returning nothing?
puppet resource firewall
Thats very odd. I get a full return of firewall rules.
... Ken Barber

07:41 am Bug #10654: firewall: Action property still jumping to ACCEPT chain

It's not just the updates:
# iptables -F && puppet apply --debug /tmp/firewalltest.pp
...
debug: Pup... Justin Ellison

07:09 am Bug #10654: firewall: Action property still jumping to ACCEPT chain

Odd. Thats different to what I'm getting:
debug: Puppet::Type::Firewall::ProviderIptables: Executing '/sbin/ip... Ken Barber

07:01 am Bug #10665: firewall: exec is not notified when purging rules

I'm talking specifically about moving the default and persist-firewall definition:
exec { "persist-firewall":
... Ken Barber

06:28 am Bug #10654: firewall: Action property still jumping to ACCEPT chain

# uname -a
Linux xxxxxxx.com 2.6.18-238.12.1.el5 #1 SMP Tue May 31 13:23:01 EDT 2011 i686 i686 i386 GNU/Linu... Justin Ellison

06:03 am Bug #10665: firewall: exec is not notified when purging rules

>> The default Firewall notify works only for rules in the same class (not for remove – i suppose, too)
> This is a s... Michael Arlt

05:44 am Bug #10665: firewall: exec is not notified when purging rules

> - Per rule notification does work for new and changed rules (not for removed)
Okay - yes thats a bug.
> - The... Ken Barber

04:47 am Bug #10665: firewall: exec is not notified when purging rules

>Under what scope are you creating the firewall default?
We have a class fw where several default firewall rules are... Michael Arlt

03:48 am Bug #10665 (Needs More Information): firewall: exec is not notified when purging rules

Under what scope are you creating the firewall default?
Firewall {
notify => Exec["persist-firewall"]
... Ken Barber

02:52 am Bug #10654 (Needs More Information): firewall: Action property still jumping to ACCEPT chain

For the first snippet:
firewall { '999 drop all others':
action => "reject",
proto => "all",
... Ken Barber

11:39 pm Bug #10665 (Closed): firewall: exec is not notified when purging rules

I configured the firewall for persistence as described at http://forge.puppetlabs.com/puppetlabs/firewall:
exe... Michael Arlt

06:05 pm Bug #10654: firewall: Action property still jumping to ACCEPT chain

Just a note that as I left, I rolled puppetlabs-firewall back to 0.0.1, and used this snippet:
firewall { '999 d... Justin Ellison

05:58 pm Bug #10654 (Closed): firewall: Action property still jumping to ACCEPT chain

I was just updating my module from a pre-release version of puppetlabs-firewall, and found what I think might be a ve... Justin Ellison

11/08/2011

05:14 am Bug #10619 (Accepted): firewall: Unable to purge unmanaged rules tables other than "filter"

Ken Barber

05:30 pm Bug #10619 (Merged - Pending Release): firewall: Unable to purge unmanaged rules tables other tha...

If you try and purge unmanaged rules across different tables (mangle, nat, raw, etc), you'll get an error from iptabl... Chris Boulton

04:24 pm Bug #8354 (Needs Decision): keeping a repository up to date

Nick - docs? James Turnbull

04:24 pm Bug #8354 (Accepted): keeping a repository up to date

James Turnbull