Bug #4327

pluginsync is not activated when it is added to the config file, and puppetd is daemonized

Added by Oliver Hookins almost 2 years ago. Updated over 1 year ago.

Status:Closed Start date:07/22/2010
Priority:Normal Due date:
Assignee:Oliver Hookins % Done:

0%
Category:executables
Target version:2.6.1
Affected Puppet version:0.25.4 Branch:
Keywords:
Votes: 0

Description

If you are running puppetd as a daemon which starts a new run periodically, it is impossible to activate pluginsync without a restart of puppetd.

Steps: 1. Start puppetd daemonized (e.g. service puppet start) 2. Add pluginsync=true to /etc/puppet/puppet.conf 3. The running puppetd re-evaluates the changed config 4. Puppetd does not enable pluginsync

History

#1
Updated by James Turnbull almost 2 years ago

  • Category set to executables
  • Status changed from Unreviewed to Needs More Information
  • Assignee set to Oliver Hookins

I think this is fixed in 2.6.x – any chance you can test?

#2
Updated by Oliver Hookins over 1 year ago

Indeed, it does seem to be fixed in 2.6.0:

notice: Reparsing /etc/puppet/puppet.conf
info: Retrieving plugin
info: /File[/var/lib/puppet/lib]: Storing newly-audited value  for content
info: /File[/var/lib/puppet/lib/facter]: Storing newly-audited value absent for type
info: /File[/var/lib/puppet/lib/facter]: Storing newly-audited value absent for content
notice: /File[/var/lib/puppet/lib/facter]/ensure: created
info: /File[/var/lib/puppet/lib/facter/fake.rb]: Storing newly-audited value absent for type
notice: /File[/var/lib/puppet/lib/facter/fake.rb]/ensure: defined content as '{md5}f767dfec341e06b259ec5297be00834f'
info: Loading downloaded plugin /var/lib/puppet/lib/facter/fake.rb

#3
Updated by James Turnbull over 1 year ago

  • Status changed from Needs More Information to Closed
  • Target version set to 2.6.1

Thanks Oliver.

Also available in: Atom PDF