Issue #4327 has been updated by Oliver Hookins.
Indeed, it does seem to be fixed in 2.6.0:
<pre>
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
</pre>
----------------------------------------
Bug #4327: pluginsync is not activated when it is added to the config file, and
puppetd is daemonized
http://projects.puppetlabs.com/issues/4327
Author: Oliver Hookins
Status: Needs more information
Priority: Normal
Assignee: Oliver Hookins
Category: executables
Target version:
Affected version: 0.25.4
Keywords:
Branch:
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
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
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.
