Puppet users - Jan 2012 - arrays after upgrade to 2.7 and ['A','B'] compared to 'A B'?

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 => [''me@CERN.CH'',
''them@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 [''me@CERN.CH'',
''them@CERN.CH''] to ''me@CERN.CH them@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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

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.traylen@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 => [''me@CERN.CH'',
''them@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 [''me@CERN.CH'',
''them@CERN.CH''] to ''me@CERN.CH
> them@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+unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Thu, Jan 26, 2012 at 03:57:08PM +0000, Steve Traylen
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 => [''me@CERN.CH'',
''them@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 [''me@CERN.CH'', ''them@CERN.CH''] to
''me@CERN.CH them@CERN.CH''
> 
> Notice how the [''A'',''B''] is compared to
''A B''
> 
The [''A'',''B''] vs ''A B''
*seems* to be just a display thing because the
current value and the desired value are handled differently when
printing them out (should_to_s vs. is_to_is in property.rb).

Can you please tell me the ruby version you are using? So we can rule
1.8.5 incompabilities out?

-Stefan

On 26 Jan 2012, at 19:29, "Stefan Schulte"
<stefan.schulte@taunusstein.net> wrote:
> On Thu, Jan 26, 2012 at 03:57:08PM +0000, Steve Traylen 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 => [''me@CERN.CH'',
''them@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 [''me@CERN.CH'', ''them@CERN.CH''] to
''me@CERN.CH them@CERN.CH''
>> 
>> Notice how the [''A'',''B''] is
compared to ''A B''
>> 
> 
> The [''A'',''B''] vs ''A
B'' *seems* to be just a display thing because the
> current value and the desired value are handled differently when
> printing them out (should_to_s vs. is_to_is in property.rb).
> 
> Can you please tell me the ruby version you are using? So we can rule
> 1.8.5 incompabilities out?
Hi, Stefan, other than puppet and facter which are from the puppetlabs repo
everything is rhel6 defaults so ruby 1.8.7 and facter
1.6.5
> 
> -Stefan
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Thu, Jan 26, 2012 at 10:39, Steve Traylen <steve.traylen@cern.ch>
wrote:
> On 26 Jan 2012, at 19:29, "Stefan Schulte"
<stefan.schulte@taunusstein.net> wrote:
>> On Thu, Jan 26, 2012 at 03:57:08PM +0000, Steve Traylen wrote:
>>>
>>> After upgrading a server and client from 2.6.13 to 2.7.10 my
configuration with array attributes
>>> are behaving differently. 3 examples:
[…]
>> Can you please tell me the ruby version you are using? So we can rule
>> 1.8.5 incompabilities out?
>
> Hi, Stefan, other than puppet and facter which are from the puppetlabs repo
everything is rhel6 defaults so ruby 1.8.7 and facter 1.6.5
Hrm.  Looks like that might be a bug.  Can you file tickets reflecting
the different issues you are hitting?
-- 
Daniel Pittman
⎋ Puppet Labs Developer – http://puppetlabs.com
♲ Made with 100 percent post-consumer electrons

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Thu, Jan 26, 2012 at 11:52:52AM -0800, Daniel Pittman
wrote:
> On Thu, Jan 26, 2012 at 10:39, Steve Traylen <steve.traylen@cern.ch>
wrote:
> > On 26 Jan 2012, at 19:29, "Stefan Schulte"
<stefan.schulte@taunusstein.net> wrote:
> >> On Thu, Jan 26, 2012 at 03:57:08PM +0000, Steve Traylen wrote:
> >>>
> >>> After upgrading a server and client from 2.6.13 to 2.7.10 my
configuration with array attributes
> >>> are behaving differently. 3 examples:
> 
> […]
> 
> >> Can you please tell me the ruby version you are using? So we can
rule
> >> 1.8.5 incompabilities out?
> >
> > Hi, Stefan, other than puppet and facter which are from the puppetlabs
repo everything is rhel6 defaults so ruby 1.8.7 and facter 1.6.5
> 
> Hrm.  Looks like that might be a bug.  Can you file tickets reflecting
> the different issues you are hitting?
I was able to reproduce the issue and filed a bug:
http://projects.puppetlabs.com/issues/12197

I''ve tried the following combinations

puppet 2.7.9 / ruby 1.8.7 -> No issue
puppet 2.7.9 / ruby 1.9.3 -> No issue
puppet 2.7.10 / ruby 1.8.7 -> Bug as described earlier
puppet 2.7.10 / ruby 1.9.3 -> No issue

-Stefan