Bug #1056

Pluginsync/factsync checksums are getting stored in the state file

Added by Martha Greenberg over 2 years ago. Updated over 1 year ago.

Status:Closed Start:
Priority:Normal Due date:
Assignee:Puppet Community % Done:

0%
Category:unknown
Target version:unplanned
Affected version:0.24.4 Branch:
Keywords:
Votes: 0

Description

Periodically, puppetd reports that it has updated the checksum for files in $libdir, but does not actually do so. It reports this on every run until state.yaml is removed.

Feb  7 22:04:22 uk4 puppetdr26029: (/File[/var/lib/puppet/lib]/checksum) checksum changed '{time}Tue Jan 29 23:11:05 +0000 2008' to '{time}Tue Jan 29 23:11:22 +0000 2008'
Feb  7 22:04:26 uk4 puppetdr26029: (/File[/var/lib/puppet/lib/puppet/provider/pgsql_database/pgsql.rb]/checksum) checksum changed '{md5}5920ff19f200eb1bc69a8f015d368887' to '{md5}e9b95e61ac7c5d35171c252adca5d0aa'
Feb  7 22:04:27 uk4 puppetdr26029: (/File[/var/lib/puppet/lib/puppet/provider/pgsql_user/pgsql.rb]/checksum) checksum changed '{md5}ef46eee45a5eabe83bd785bed5874e54' to '{md5}1a46f17482a4ae45e564c2d253af0f26'
Feb  7 22:04:32 uk4 puppetdr26029: (/File[/var/lib/puppet/lib/puppet/type/pgsql_user.rb]/checksum) checksum changed '{md5}f8e8e99195103ffd32183a7f950cc7bd' to '{md5}0ea09ba92294fc5ec1fef4f527009fa9'
Feb  7 22:04:34 uk4 puppetdr26029: (/File[/var/lib/puppet/lib/facter/virtual.rb]/checksum) checksum changed '{md5}4df11654a6eefec96afbc7298457c7eb' to '{md5}b6f239ff9554a81d73dedd8e9c5fa130'
Feb  7 22:35:14 uk4 puppetdr26029: (/File[/var/lib/puppet/lib]/checksum) checksum changed '{time}Tue Jan 29 23:11:05 +0000 2008' to '{time}Tue Jan 29 23:11:22 +0000 2008'
Feb  7 22:35:18 uk4 puppetdr26029: (/File[/var/lib/puppet/lib/puppet/provider/pgsql_database/pgsql.rb]/checksum) checksum changed '{md5}5920ff19f200eb1bc69a8f015d368887' to '{md5}e9b95e61ac7c5d35171c252adca5d0aa'
Feb  7 22:35:19 uk4 puppetdr26029: (/File[/var/lib/puppet/lib/puppet/provider/pgsql_user/pgsql.rb]/checksum) checksum changed '{md5}ef46eee45a5eabe83bd785bed5874e54' to '{md5}1a46f17482a4ae45e564c2d253af0f26'
Feb  7 22:35:24 uk4 puppetdr26029: (/File[/var/lib/puppet/lib/puppet/type/pgsql_user.rb]/checksum) checksum changed '{md5}f8e8e99195103ffd32183a7f950cc7bd' to '{md5}0ea09ba92294fc5ec1fef4f527009fa9'
Feb  7 22:35:26 uk4 puppetdr26029: (/File[/var/lib/puppet/lib/facter/virtual.rb]/checksum) checksum changed '{md5}4df11654a6eefec96afbc7298457c7eb' to '{md5}b6f239ff9554a81d73dedd8e9c5fa130'

state.yaml (148.7 KB) Martha Greenberg, 02/08/2008 12:30 am

state.yaml.new (146.5 KB) Martha Greenberg, 02/08/2008 12:31 am

Related issues

duplicated by Puppet - Bug #1127: MD5 checksums being reported as changed on each run Closed

History

#1
Updated by Luke Kanies over 2 years ago

This is during pluginsync, right?

If so, those checksums don’t currently get stored in the state.yaml file. I’m not sure whether they ever will be; does it matter to you that they are?

#2
Updated by Martha Greenberg over 2 years ago

Yes, this is during pluginsync. Those checksums are in the state.yaml now. I don’t really care if they are, but the messages on every run when this happens is annoying.

#3
Updated by Luke Kanies over 2 years ago

Strange, ok.

#4
Updated by micah - over 2 years ago

I’m also seeing this problem, I reported it in #1123 and believe that its the same problem as this one.

To make this happen I just had to update a custom local fact (I already had a facter recipe that was already distributed with 0.23

My client puppet.conf looks like this:

[main]
ssldir=/var/lib/puppet/ssl
logdir=/var/log/puppet
vardir=/var/lib/puppet
rundir=/var/run/puppet
templatedir=/etc/puppet/templates
factpath = $vardir/lib/facter
pluginsync=true

[puppetd]
# Make sure all log messages are sent to the right directory                                                                                                                                         
# This directory must be writable by the puppet user                                                                                                                                                 
pluginsync=true
factsync=false
report=true

#5
Updated by Luke Kanies over 2 years ago

Marking #1127 as a duplicate.

#6
Updated by Udo Waechter over 2 years ago

This also happenes with puppet(master) 0.24.4. Darwin Tiger and Debian Etch.

#7
Updated by Redmine Admin about 2 years ago

  • Status changed from 1 to Accepted

#8
Updated by Ohad Levy about 2 years ago

  • Affected version set to 0.24.4

This happens also with normal factsync, it seems that puppet doesn’t update the state file when syncing facts from the server.

#9
Updated by Marcin Deranek over 1 year ago

We see similar problem with 0.24.6. In our case though state.yaml file seems to be “poisoned” by one of the previous versions (0.24.4 or earlier) we used, so our plugin/fact entries ended up in state.yaml, but were never removed (I saw some obsolete entries there as well). Once the file got removed we do not see any problems (although we haven’t tested it long enough yet). After file was re-created we do not see any plugin/fact entries there anymore.

#10
Updated by Luke Kanies over 1 year ago

  • Status changed from Accepted to Closed

Yeah, the fix for this is to remove your state file and let Puppet refresh it.

This has been fixed since, apparently, at least 0.24.6. I don’t know why the ticket’s still open.

#11
Updated by Marcin Deranek over 1 year ago

This has been fixed since, apparently, at least 0.24.6. I don’t know why the ticket’s still open.

Had spoken too soon – after cleanup facts/plugins are still there. Seems like during initial “sync” state file was “cleab”, but after a few manual puppetd runs in test mode all facts/plugins ended up in there :–( Disabling stored configurations did not help either..

Also available in: Atom PDF