Issue #6310 has been updated by Victor Chavez.
File check-puppet added
File puppet_md5_bug.txt added
Matt Robinson wrote:
> Could you provide us the contents of a file where you see this behavior?
> That would certainly make this easier to debug. An attachment to the ticket
> would be best.
Attached.
> What operating system are you using? md5 utilities on different platforms
> have different meanings for the -t flag, which I assume you're using to mean
> read in text mode, which is already default, so I wasn't sure why you were
> adding it in your example.
Typically we run Debian Lenny, RHEL4/5, and Ubuntu 10.10 (Maverick). I meant
the '-t' flag as just making the default explicit; sorry for the extra
confusion. I'll leave it out from now on.
> When you say this isn't consistent, does that mean it only happens for some
> files, or that it only happens sometimes? For example, if you rerun puppet,
> does it ever update the state.yml with the same md5 you get from the command
> line for /etc/cron.hourly/check-puppet, or does that file's state.yml md5
> differ from the md5 utility after every puppet run?
All clients have this output:
# md5sum /etc/cron.hourly/check-puppet
bb8ae3bd2663bbc416152b0ed88ba4c7 /etc/cron.hourly/check-puppet
# ssh yum puppetd --version
2.6.3
The yaml file is where things differ. I've also attached the yaml from a
sampling of our hosts with differing distros and architectures. Since the md5
sum I've included above is not contained in ANY of the YAML files, I'm
wondering if this even works the way I expect it to.
Please let me know if you need more info.
Ultimately, I'm just trying to find a way to update tripwire in a secure and
consistent way. If I need to get the md5 from puppet in a different way,
please let me know what that route looks like.
Thanks!
Victor
----------------------------------------
Bug #6310: md5sum reports different md5 than state.yaml
https://projects.puppetlabs.com/issues/6310
Author: Victor Chavez
Status: Needs More Information
Priority: Normal
Assignee:
Category:
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.
