Bug 483767 - default puppet.conf does not support pluginsync
Summary: default puppet.conf does not support pluginsync
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: puppet
Version: el5
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: David Lutterkort
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: ActualBug
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-03 15:13 UTC by Kjetil T. Homme
Modified: 2013-04-30 23:40 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-07-08 02:55:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Kjetil T. Homme 2009-02-03 15:13:24 UTC
Description of problem:
The recommended method for distributing plugins and facts does not work out of the box with the EPEL packaged puppet.conf.  This complicates bootstrapping since a replacement puppet.conf must be distributed prior to the first Puppet run if the configuration relies on custom facts or providers.

Version-Release number of selected component (if applicable):
puppet-0.24.7-4.el5

Additional info:

This URL has the background:
http://reductivelabs.com/trac/puppet/wiki/PluginsInModules

The fix is pretty simple, add this to puppet.conf:

[main]
pluginsync = true
factpath = $vardir/lib/facter

Comment 1 Todd Zullinger 2009-06-01 02:21:00 UTC
This seems like something that we should follow upstream on.  I think it would be worth asking on puppet-dev or puppet-users why these settings are not enabled by default.  Kjetil, would you care to ask about this on one of those lists?

Comment 2 Todd Zullinger 2009-07-08 02:55:05 UTC
I don't think this should be considered a bug.  If this should be enabled by default, it should be something that upstream agrees with and ships in the stock configuration.


Note You need to log in before you can comment on or make changes to this bug.