I don't have a suggestion but I can confirm I see the same behavior with a
2.7.10 server and 2.7.10
client running the very latest puppetlabs-firewall code. It constantly
claims things have changed to
the exact identical stuff:
notice: /Firewall[000 INPUT allow related and established]/state: state
changed 'ESTABLISHED,RELATED' to 'ESTABLISHED,RELATED'
notice: Firewall[000 INPUT allow related and
established](provider=iptables): Properties changed - updating rule
info: /Firewall[000 INPUT allow related and established]: Scheduling
refresh of Exec[persist-firewall]
notice: /Firewall[001 rundeck]/dport: dport changed '4440,4443' to
'4440,4443'
notice: Firewall[001 rundeck](provider=iptables): Properties changed -
updating rule
notice: /Stage[main]/Firewall::Standard/Exec[persist-firewall]: Triggered
'refresh' from 1 events
notice: /Firewall[001 inbound ports for foreman]/dport: dport changed
'80,443' to '80,443'
notice: Firewall[001 inbound ports for foreman](provider=iptables):
Properties changed - updating rule
I'll raise a bug in a little bit for this (I'm bringing a new guy up to
speed so I'm a bit busy this morning)
On Thu, Jan 26, 2012 at 10:57 AM, Steve Traylen <steve.tray...@cern.ch>wrote:
> Hi,
>
> After upgrading a server and client from 2.6.13 to 2.7.10 my configuration
> with array attributes
> are behaving differently. 3 examples:
>
> (1)
> k5login {'/root/.k5login-test':
> principals => ['m...@cern.ch', 't...@cern.ch'],
> }
>
> while .k5login file is created perfectly but every puppet run updates the
> file with.
>
> notice:
> /Stage[main]/Kerberos::Root/K5login[/root/.k5login-test]/principals:
> principals changed ['m...@cern.ch', 't...@cern.ch'] to 'm...@cern.ch
> t...@cern.ch'
>
> Notice how the ['A','B'] is compared to 'A B'
>
> (2)
> I see the same thing elsewhere as well, e.g. (puppetlabs-firewall-0.0.4)
>
> e.g:
> firewall { '000 allow packets with valid state':
> proto => all,
> state => ['RELATED', 'ESTABLISHED'],
> action => accept,
> }
>
> info: /Firewall[000 allow packets with valid state]/state: state changed
> ['ESTABLISHED', 'RELATED'] to 'ESTABLISHED,RELATED'
>
> or
> (3)
> firewall{'100 openup for glusterfs':
> state => 'NEW',
> proto => 'tcp',
> dport => ['111','24007-24047','38465-38467'],
> action => accept,
> }
> info: /Firewall[100 openup for glusterfs]/dport: dport changed ['111',
> '24007-24047', '38465-38467'] to '111,24007-24047,38465-38467'
>
> This is on RHEL/SLC6
>
> I did not see this for the brief time I had a 2.7.10 server and 2.6
> client, only with the client update did it appear.
> A colleague has reproduced the k5login example above with a 2.7.9 server
> and client.
>
> Any suggestions.. ?
>
> Steve.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
