#1123: fact checksum changes
-------------------+--------------------------------------------------------
Reporter:  micah   |        Owner:  community 
    Type:  defect  |       Status:  new       
Priority:  normal  |    Component:  client    
 Version:  0.24.2  |     Severity:  normal    
Keywords:          |        Stage:  Unreviewed
   Patch:  None    |   Complexity:  Unknown   
-------------------+--------------------------------------------------------
 I changed a local fact that I had already managed via puppet, it was
 distributed as expected:

 {{{
 Mar  8 13:29:21 eider puppetd[19747]:
 (/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 puppetd[19747]:
 (/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 puppetd[19747]:
 (/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).

-- 
Ticket URL: <http://reductivelabs.com/trac/puppet/ticket/1123>
puppet <http://reductivelabs.com>
Puppet - Portable System Automation
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to