Hi all,
I got a strange problem with latest puppet/ruby, when i execute puppet
on solaris 9 or 10 with a group ownership check it always changes the
value to "1" aka "other".
Do you know if this a ruby or puppet problem ?
For cfg as below
file { "/etc/shadow":
owner => root,
group => sys,
mode => 400,
}
When executed we get
#:/# /usr/local/bin/puppetd --server myserver --waitforcert 60 --test
notice: Ignoring cache
info: Caching configuration at /var/puppet/state/localconfig.yaml
notice: Starting configuration run
notice: //basenode/solaris_permissions/File[/etc/passwd]/group: group
changed ''other'' to ''other''
info: Sent transaction report in 0.64 seconds
notice: Finished configuration run in 0.96 seconds
Same with a "realize" user, the gid is always set to 1
Ruby version is 1.8.6 compiled from source.
cheers,
lionel
_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
On Mon, 2007-05-21 at 13:02 +0200, Lionel Culot wrote:> Hi all, > > I got a strange problem with latest puppet/ruby, when i execute puppet > on solaris 9 or 10 with a group ownership check it always changes the > value to "1" aka "other". > Do you know if this a ruby or puppet problem ?It''s a bug in Ruby. There is a fix in upstream SVN but I don''t know if the fix has made it into a released version. Here''s the bug on Red Hat''s bugzilla that has more information about the bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236647 Jeff _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
Thanks Jeffrey, the latest stable snapshot now works indeed. Jeffrey C. Ollie wrote:> On Mon, 2007-05-21 at 13:02 +0200, Lionel Culot wrote: > >> Hi all, >> >> I got a strange problem with latest puppet/ruby, when i execute puppet >> on solaris 9 or 10 with a group ownership check it always changes the >> value to "1" aka "other". >> Do you know if this a ruby or puppet problem ? >> > > It''s a bug in Ruby. There is a fix in upstream SVN but I don''t know if > the fix has made it into a released version. > > Here''s the bug on Red Hat''s bugzilla that has more information about the > bug: > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236647 > > Jeff > > > ------------------------------------------------------------------------ > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users >_______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users