Issue #16250 has been updated by John Florian.
eric sorenson wrote: > pluginsync needs to be set either in the [main] or [agent] section of the > config to apply to the agent. It already is/was. > When you are running as non-root, your ~/.puppet/puppet.conf file is used for > settings instead of the system-wide /etc/puppet/puppet.conf. **I don't have a ~/.puppet/puppet.conf, so that particular quirk still seems buggy to me.** > Not sure if this is the source of your trouble but the module name should not > have a hyphen in it. `mv /etc/puppet/modules/mosen-cups-1.0.0 > /etc/puppet/cups` **That was indeed the problem!** I sure wish puppet would have given some warning about this. I've spent way too many hours trying to hunt this down. Many of my own modules have hyphens in their name, but my plugins have been limited to facts only. I've never seen this as a problem until now. Is this restriction specific to pluginsync only? > Does any of that help? Yes! THANK YOU so much. ---------------------------------------- Bug #16250: Problems with pluginsync https://projects.puppetlabs.com/issues/16250#change-70539 Author: John Florian Status: Needs More Information Priority: Normal Assignee: John Florian Category: plug-ins Target version: Affected Puppet version: Keywords: Branch: I'm trying to get a downloaded puppet module (https://github.com/mosen/puppet-cups) to work but am struggling with the pluginsync feature. Up until trying this module, I thought I had pluginsync working as I have a few self-authored modules with custom facts that do indeed get pushed out to the client nodes. However, with this cups module nothing is being synchronized that I can see. In my puppet.conf (master and clients alike), I have "pluginsync = true" in the [main] section. While trying to confirm this setting, I discovered one anomaly that may be a bug: <pre> $ puppet master --configprint pluginsync /usr/share/rubygems/rubygems/custom_require.rb:36:in `require': iconv will be deprecated in the future, use String#encode instead. true $ puppet agent --configprint pluginsync /usr/share/rubygems/rubygems/custom_require.rb:36:in `require': iconv will be deprecated in the future, use String#encode instead. false $ sudo puppet master --configprint pluginsync /usr/share/rubygems/rubygems/custom_require.rb:36:in `require': iconv will be deprecated in the future, use String#encode instead. true $ sudo puppet agent --configprint pluginsync /usr/share/rubygems/rubygems/custom_require.rb:36:in `require': iconv will be deprecated in the future, use String#encode instead. true </pre> I'm not so concerned with the deprecation warning as much as why this setting reports false for the agent, unless the query is run as root. I see the exact same behavior from the client nodes, although I suspect the query for the master mode is pointless from a client perspective. Most strange is that the master and agent modes behave differently. So I don't know if this is where my problem with pluginsync stems from or if it's elsewhere. When I run "puppet agent --test" on the master, I do see: <pre> info: Loading facts in /etc/puppet/modules/mosen-cups-1.0.0/lib/facter/printers.rb </pre> and the printer (sic print queue) get's created, but a quick check shows that nothing lands alongside with my own facts: <pre> sudo find /var/lib/puppet/lib/ /var/lib/puppet/lib/ /var/lib/puppet/lib/facter /var/lib/puppet/lib/facter/plant_number.rb /var/lib/puppet/lib/facter/selinux_simple.rb </pre> I guess I would have expected the fact containing printers.rb to land there. When I run "puppet agent --test --debug" on a typical client, I do not see any mention of "mosen-cups" or "printer" and /var/lib/puppet/lib looks identical to the server, as shown above. Shouldn't everything in modules/mosen-cups/lib get replicated here? For the record, I have puppet-2.7.18-1.fc17 on the master and puppet-2.6.17-2.fc16 on my test client. -- 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.
