Bug #1123
fact checksum changes
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | - | |||
| Target version: | - | |||
| Affected Puppet version: | 0.25.4 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
I changed a local fact that I had already managed via puppet, it was distributed as expected:
Mar 8 13:29:21 eider puppetdr19747: (/File[/var/lib/puppet/lib/facter/in_colo.rb]/source) replacing from source puppet://puppetmaster.riseup.net/plugins/facter/in_colo.rb with contents
{md5}0a9f5d61636b784409ffddd383da468a
But from then on I’m getting “checksum changes” notices for this fact:
Mar 8 14:01:38 eider puppetdr19747: (/File[/var/lib/puppet/lib/facter/in_colo.rb]/checksum) checksum changed '{md5}e7c006e967e92d67ba86d6529ad20409' to '{md5}0a9f5d61636b784409ffddd383da468a'
The checksums aren’t actually changing, each run the same md5 sums are reported, as the following log entry from a day later illustrates:
Mar 9 01:54:14 eider puppetdr19747: (/File[/var/lib/puppet/lib/facter/in_colo.rb]/checksum) checksum changed '{md5}e7c006e967e92d67ba86d6529ad20409' to '{md5}0a9f5d61636b784409ffddd383da468a'
This is running 0.24.x (even though I’ve selected version 0.24.2 below).
History
Updated by micah - almost 4 years ago
- Status changed from 1 to Closed
- 7 set to duplicate
I believe that this issue is the same as #1056, so I am resolving it as a duplicate.