Issue #6310 has been updated by Josh Cooper. Status changed from Investigating to Closed
I believe the issue here is that state.yaml contains the previous value, not the the desired value that puppet applied. This issue is explained in more detail in ticket #7295, which is linked to the same support ticket as this one. See <http://projects.puppetlabs.com/issues/7295#note-8> for more details. ---------------------------------------- Bug #6310: md5sum reports different md5 than state.yaml https://projects.puppetlabs.com/issues/6310#change-67689 Author: Victor Chavez Status: Closed Priority: Normal Assignee: Daniel Pittman Category: file Target version: Affected Puppet version: 2.6.3 Keywords: md5sum md5 checksum different state.yaml Branch: This isn't consistent for every file, but here's one case where the checksum is different: /var/lib/puppet/state/state.yaml: "File[/etc/cron.hourly/check-puppet]": !ruby/sym checked: 2011-02-14 11:59:03.113156 -08:00 !ruby/sym synced: 2011-01-31 20:09:34.276961 -08:00 !ruby/sym checksums: !ruby/sym md5: "{md5}5e776d11721da4a5817864373bb05ec2" luckdragon:~> md5sum -t /etc/cron.hourly/check-puppet bb8ae3bd2663bbc416152b0ed88ba4c7 /etc/cron.hourly/check-puppet luckdragon:~> grep bb8ae3bd2663bbc416152b0ed88ba4c7 /var/lib/puppet/state/state.yaml luckdragon:~> echo $? 1 luckdragon:~> I was hoping to use this comparison to update tripwire directly from puppet. This checksum mismatch makes that process a bit harder. :) -- Victor -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
