Puppet users - Sep 2010 - puppet file recursion requires two passes to converge

Hi,

So for awhile I have been seeing this issue but it hasn''t been painful.
However, recently I have been deploying a new module that has made it much more
annoying.

 	file { cdh3_config:
                recurse => true,
                ignore => ".svn",
                checksum => md5,
                notify => Exec[hadoop_alternatives],
                require => Package[hadoop],
		path => "/etc/hadoop-$bespin_cdh3_version/conf.bespin",
		source => "puppet:///modules/cdh/cdh3/conf.bespin",
        }

Then I have 2-3 different hadoop services that subscribe this resource.

So if you make a change in the directory it will correctly refresh the services.
However the next time puppet runs, it will notice there is a mtime difference on
the directory and this will also trigger a refresh.

notice: //cdh::cdh3/File[cdh3_config]/checksum: checksum changed
''{mtime}Wed Sep 01 21:28:46 -0400 2010'' to
''{mtime}Thu Sep 02 08:53:56 -0400 2010''

This is not good since this forces the services to restart again, which is
really annoying.

We run, puppet 0.25.4.

Thanks,
derek

Derek Yarnell
UNIX Systems Administrator
University of Maryland
Institute for Advanced Computer Studies



-- 
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.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> So if you make a change in the directory it will correctly refresh
> the services.  However the next time puppet runs, it will notice
> there is a mtime difference on the directory and this will also
> trigger a refresh.
> 
> notice: //cdh::cdh3/File[cdh3_config]/checksum: checksum changed
> ''{mtime}Wed Sep 01 21:28:46 -0400 2010'' to
''{mtime}Thu Sep 02
> 08:53:56 -0400 2010''
> 
> This is not good since this forces the services to restart again,
> which is really annoying.
> 
> We run, puppet 0.25.4.
This might be a bug. It would be good if you could test if it still
exists on lates 2.6.1rcX an/or file a bug if there isn''t yet one.

pete
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkx/x+gACgkQbwltcAfKi3/GngCgh3gI8ufV4kIdGkp8f10D97BR
wrUAmgOoo1mnU989whu9hDoPSwk9qDk9
=PtFf
-----END PGP SIGNATURE-----

-- 
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.

Hi Pete,

It does seem fixed in 2.6.1rc3, however 0.25.5 it is still happens.  Has there
been a convergence of opinion on how to roll out 2.6.x?  Server first then
clients?  Clients first then the server?  Everything at once? (that is hard
obviously)

Thanks,
derek

On Sep 2, 2010, at 11:51 AM, Peter Meier wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
>> So if you make a change in the directory it will correctly refresh
>> the services.  However the next time puppet runs, it will notice
>> there is a mtime difference on the directory and this will also
>> trigger a refresh.
>> 
>> notice: //cdh::cdh3/File[cdh3_config]/checksum: checksum changed
>> ''{mtime}Wed Sep 01 21:28:46 -0400 2010'' to
''{mtime}Thu Sep 02
>> 08:53:56 -0400 2010''
>> 
>> This is not good since this forces the services to restart again,
>> which is really annoying.
>> 
>> We run, puppet 0.25.4.
> 
> This might be a bug. It would be good if you could test if it still
> exists on lates 2.6.1rcX an/or file a bug if there isn''t yet one.
> 
> pete
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> 
> iEYEARECAAYFAkx/x+gACgkQbwltcAfKi3/GngCgh3gI8ufV4kIdGkp8f10D97BR
> wrUAmgOoo1mnU989whu9hDoPSwk9qDk9
> =PtFf
> -----END PGP SIGNATURE-----
> 
> -- 
> 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.
> 
> 
Derek Yarnell
UNIX Systems Administrator
University of Maryland
Institute for Advanced Computer Studies



-- 
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.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> It does seem fixed in 2.6.1rc3, however 0.25.5 it is still happens.
> Has there been a convergence of opinion on how to roll out 2.6.x?
> Server first then clients?  Clients first then the server?
> Everything at once? (that is hard obviously)
always update master first.

"It is also important to note when upgrading that not all versions are
backwards compatible. Newer clients may not work with older servers and
vice-versa. Where possible backwards-compatibility is maintained but
it?s not always totally successful. The best approach is to ensure your
master and clients are the same version. When upgrading it is also
recommended that you upgrade your master first."

http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes

pete
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkyAGW4ACgkQbwltcAfKi38jMQCfdBKAE1Iwyoytcb1i5liO5ZGB
P7sAn0nwH0duT0RLJXtUUWmOkc0gAjkh
=3Ajp
-----END PGP SIGNATURE-----

-- 
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.