Actually I am also seeing non-recursive normal files that are replaced
every time I run puppetd on the client. One example is below. Am I
doing something wrong? I've used 'stat' to ensure the file on the
puppetmaster server is not actually changing between runs.
Declaration:
file { "/etc/skel/.bashrc":
source => "puppet:///users/bashrc",
ensure => "present",
checksum => "mtime",
backup => "false",
owner => "root",
group => "root",
}
On the server:
# date
Tue Oct 28 11:33:39 PDT 2008
# stat users/files/bashrc
File: `users/files/bashrc'
Size: 2643 Blocks: 8 IO Block: 4096 regular
file
Device: 901h/2305d Inode: 134267667 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/
root)
Access: 2008-10-28 11:29:25.721960224 -0700
Modify: 2008-10-28 11:28:33.427825076 -0700
Change: 2008-10-28 11:28:33.427825076 -0700
On the client:
# date
Tue Oct 28 11:34:11 PDT 2008
# stat /etc/skel/.bashrc
File: `/etc/skel/.bashrc'
Size: 2643 Blocks: 8 IO Block: 4096 regular
file
Device: 801h/2049d Inode: 99410 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/
root)
Access: 2008-10-28 11:32:57.000000000 -0700
Modify: 2008-10-28 11:32:57.000000000 -0700
Change: 2008-10-28 11:32:57.000000000 -0700
# puppetd --server dev.robotbattle.com --test
notice: Starting catalog run
notice: //Node[default]/users/File[/etc/skel/.bashrc]/checksum:
checksum changed '{md5}6e58e17309d1352a56b45699439e1800' to
'{mtime}Tue Oct 28 11:32:57 -0700 2008'
notice: //Node[default]/users/File[/etc/skel/.bashrc]/source:
replacing from source puppet:///users/bashrc with contents
{md5}6e58e17309d1352a56b45699439e1800
# stat /etc/skel/.bashrc
File: `/etc/skel/.bashrc'
Size: 2643 Blocks: 8 IO Block: 4096 regular
file
Device: 801h/2049d Inode: 99468 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/
root)
Access: 2008-10-28 11:37:56.000000000 -0700
Modify: 2008-10-28 11:37:56.000000000 -0700
Change: 2008-10-28 11:37:56.000000000 -0700
Notice that the notice says "changed
'{md5}6e58e17309d1352a56b45699439e1800' to '{mtime}Tue Oct 28 11:32:57
-0700 2008'" (the pre-run stat time) but the actual stat says
2008-10-28 11:37:56.000000000 -0700 (post run time). The sequence is
the same each time I run puppetd.
-Brad
On Oct 25, 7:09 pm, schickb <[EMAIL PROTECTED]> wrote:
> Running two Ubuntu 8.04 machines with puppet 0.24.5 on both sides,
> when I use puppetd to pull a config with the file declaration below,
> all of the files in the directory are updated every run.
>
> file { "/etc/apache2/ssl":
> source => "puppet:///websites/ssl",
> ensure => "directory",
> recurse => "true",
> backup => "false",
> checksum => "mtime",
> owner => "root",
> group => "root",
> mode => "644",
>
> }
>
> Below is the top of the --test output for two runs (after it had been
> run 3 times previously):
>
> notice: //Node[default]/websites::all/websites::dev_robotbattle_com/
> File[/etc/apache2/ssl]/checksum: checksum changed '{mtime}Sat Oct 25
> 17:00:43 -0700 2008' to '{mtime}Sat Oct 25 17:25:38 -0700 2008'
> notice: //Node[default]/websites::all/websites::dev_robotbattle_com/
> File[/etc/apache2/ssl/rbdev.crt]/checksum: checksum changed
> '{md5}2992b94e506c01ff750e62ec0c0a1437' to '{mtime}Sat Oct 25 17:23:25
> -0700 2008'
> notice: //Node[default]/websites::all/websites::dev_robotbattle_com/
> File[/etc/apache2/ssl/rbdev.crt]/source: replacing from source
> puppet:///websites/ssl/rbdev.crt with contents
> {md5}2992b94e506c01ff750e62ec0c0a1437
>
> notice: //Node[default]/websites::all/websites::dev_robotbattle_com/
> File[/etc/apache2/ssl]/checksum: checksum changed '{mtime}Sat Oct 25
> 17:25:38 -0700 2008' to '{mtime}Sat Oct 25 17:32:40 -0700 2008'
> notice: //Node[default]/websites::all/websites::dev_robotbattle_com/
> File[/etc/apache2/ssl/rbdev.crt]/checksum: checksum changed
> '{md5}2992b94e506c01ff750e62ec0c0a1437' to '{mtime}Sat Oct 25 17:30:25
> -0700 2008'
> notice: //Node[default]/websites::all/websites::dev_robotbattle_com/
> File[/etc/apache2/ssl/rbdev.crt]/source: replacing from source
> puppet:///websites/ssl/rbdev.crt with contents
> {md5}2992b94e506c01ff750e62ec0c0a1437
>
> If I change the checksum to "md5" it works as expected (although still
> with horrible perf, but I understand the perf issue is known). Is the
> mtime checksum problem known also?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
