Issue #21830 has been reported by Joe Julian. ---------------------------------------- Feature #21830: Issue a warning when pluginsync is set but the modulepath module is loaded instead of the pluginpath one https://projects.puppetlabs.com/issues/21830
* Author: Joe Julian * Status: Unreviewed * Priority: Normal * Assignee: * Category: * Target version: * Affected Puppet version: * Keywords: * Branch: ---------------------------------------- When a plugin is synced to the agent using pluginsync, but the module exists in the modulepath, the synced module is not loaded and the local one is used instead. This makes debugging difficult if you have either forgotten you broke your configuration, or accidentally installed a module on an agent instead of on the master (I must have done one of those two things). According to IRC feedback, this is a fairly common occurrence. It should be fairly trivial to issue a warning when pluginsync is set but a module is loaded from the modulepath. The pluginpath should be checked before issuing the warning to ensure that if the modulepath includes the pluginpath, it is not the pluginpath version that we're loading. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
