Bug #1127
MD5 checksums being reported as changed on each run
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Puppet Community |
% Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Affected Puppet version: | 0.25.4 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
Different than #1116 I am getting this on each run:
notice: /File[/var/lib/puppet/lib/facter/in_colo.rb]/checksum: checksum changed '{md5}e7c006e967e92d67ba86d6529ad20409' to '{md5}0a9f5d61636b784409ffddd383da468a'
The fact did not change recently, but it did change a few days ago. I get that line every time the client runs, with the same MD5 sums.
I dont know if its related, but I am also seeing non-fact resources change every time as well, such as this Sshkey resource:
notice: //Node[albatross]/ssh_server/ssh_client/Sshkey[cassowary.riseup.net]/key: key changed 'ssh-rsa AAAAB3NzaC1fyc2EAAAABIwAAAIEAqF/lsrxDUpjQfy2IEqaes3lPfFkEcQnqlra3K13PcI6DRZOpEnklpzBC8h37aCZkuxfw/SXyydx98ecF5uLDsbbPrOjuKSkf+OFX7dFJT659XV992FizsStHa2DdVqIa36mF9Zoe2VHaHv5/+O4QbFgNcPbyZTFAnfS5o2II6K8= root@buffy' to 'AABBCAB3NzaC1yc2EAAAABIwAAAIEAqF/lsrxDUpjQfy2IEqaes3lPfFkEcQnqlr3hK13P1cI6DRZfOpEnklapzBC8h37aCZkuxfw/SXyydx98ecF5uLDsbbPrOjuKSkf+OFX7dFJT659XV992FizsStHa2DdVqIa36mF9Zoe2VHaHv5/+O4QbFgNcPbyZTFAnfS5o2II6K8='
This is happening with the 0.24.x branch
Related issues
History
Updated by micah - almost 4 years ago
The above is {md5}–>{md5}, but it looks like I am also seeing {mtime}–>{mtime}:
Mar 11 19:38:23 admin puppetdr16382: (/File[/var/lib/puppet/lib/facter]/checksum) checksum changed '{mtime}Mon Mar 03 21:27:53 -0800 2008' to '{mtime}Sat
Updated by AJ Christensen almost 4 years ago
that Sshkey resource looks like it actually did change. Can you confirm on the client end?
Updated by micah - almost 4 years ago
Ignore the Sshkey resource, it seems like that was coming from a system that had two puppet instances running (one older version of puppet, one HEAD). Once I corrected that, the Sshkey resource stopped changing. This also stopped the {mtime}–>{mtime} issue (as far as I can tell).
The actual bug here is that the {md5}–>{md5} keeps happening. Its not happening on all nodes. The actual md5sum of the file on a node that is doing this on each run is the one on the right hand side of this message:
notice: /File[/var/lib/puppet/lib/facter/in_colo.rb]/checksum: checksum changed '{md5}e7c006e967e92d67ba86d6529ad20409' to '{md5}0a9f5d61636b784409ffddd383da468a'
Just for laughs, I tried removing that file, and re-ran puppet. It pulled a new one, and then complained again about the md5 sum, just as above.
Updated by Luke Kanies almost 4 years ago
- Status changed from 1 to Closed
- 7 set to duplicate
This is a duplicate of #1056, basically.