Hm. I wonder if this is related, but I suspect if it was you would get complaints instead of catalog runs that succeed, albeit empty. I'll mention it anyway because you will come across this eventually.
We've had to symlink modules with custom types and providers in all environments to /etc/puppet/modules so that pluginsync will work. AFAIK this is a issue with Ruby's containment and namespace capabilities (part of the reason they're re-writing Puppet 4 in Clojure). Your master's /var/lib/puppet/lib is where is its agent stores all the plugins, and it's also where it distributes them from. What this means is that the Puppet master needs to run in order to sync any new plugins before it can distribute them. Your config look correct now since you've changed default_manifests to './manifests'. Try changing the modulepath value in your environment.conf to this: modulepath = modules -Riley ----- Original Message ----- | From: "Victor Danilchenko" <epistame...@gmail.com> | To: puppet-users@googlegroups.com | Sent: Tuesday, 28 October, 2014 12:25:10 | Subject: Re: [Puppet Users] Delving into Puppet code -- where should I ask? | Yes, I have. The salient portion of my puppet.conf file is: | [ main ] | environmentpath = $confdir / environments | basemodulepath = $confdir / modules : /usr/ share / puppet / modules | Puppet recognizes my environments (I only have 'production'), because when I | supply an invalid environment name, it complains; but though my environment | is correctly populated with modules and manifests (I simply copied it | wholesale from our operational production Puppet 3.4 master, so I know it's | correct), the command ' puppet module list ' only searches | /usr/share/puppet/modules , and returns the ' no modules installed ' | message. The environments/production/environment.conf file apparently gets | ignored as well; at least overriding modulepath in it doesn't work. | The gory details are in the adjacent thread . | So, since it seems nobody can see what's going wrong, I wanted to try to | trace the code and find where the error occurs; except that finding the | place where something isn't happening, is quite hard. I could use some code | pointers... | On Tuesday, October 28, 2014 3:14:45 PM UTC-4, Riley Shott wrote: | | Hi Victor, | | | Have you verified that you have the necessary options specified in your | | puppet.conf to turn on directory environments? | | | https://docs.puppetlabs.com/puppet/latest/reference/environments_configuring.html#enabling-directory-environments-in-puppet-enterprise | | | https://docs.puppetlabs.com/puppet/latest/reference/environments_configuring.html#enabling-directory-environments-in-open-source-puppet | | | Below is a snippet of what we specified (open source Puppet 3.7.0). | | | [master] | | | default_manifest = ./manifests | | | environmentpath = $confdir/environments | | | $confdir/environments expands out to be '/etc/puppet/environments'. | | | -Riley | | | | From: "Victor Danilchenko" < epist...@gmail.com > | | | | | | To: puppet...@googlegroups.com | | | | | | Sent: Tuesday, 28 October, 2014 12:08:00 | | | | | | Subject: [Puppet Users] Delving into Puppet code -- where should I ask? | | | | | | So, as I posted on the adjacent thread, I have been having a problem with | | | Puppet master 3.7 not reading the contents of my directory environments; | | | it | | | recognizes their existence, but ignores modules, manifests, and | | | environment.conf therein. | | | | | | Trying to fish this problem out, I decided to go some code spelunking, | | | and | | | I | | | quickly realized that tracing my way through that code is very hard -- | | | the | | | execution paths are weird and twisted. I have no idea where stuff is | | | SUPPOSED to happen; I can see that my environment/production/modules | | | directory isn't getting read, but I don't know where it's supposed to get | | | read. | | | | | | So, I was thinking about finding some puppet developers, and simply | | | asking | | | for some pointers -- namely, in which module/class/method is Puppet | | | supposed | | | to actually scan environment contents? I think I can take it from there, | | | and | | | figure our why my environment modules directory gets ignored. | | | | | | A quick google search turned up Puppet Developers group; however, I have | | | a | | | suspicion that such a question might be inappropriate there -- it's for | | | actual puppet coding, not use and troubleshooting. | | | | | | So, can anyone suggest a useful venue where I could ask questions related | | | to | | | Puppet source code ? | | | | | | Thanks. | | | | | | -- | | | | | | You received this message because you are subscribed to the Google Groups | | | "Puppet Users" group. | | | | | | To unsubscribe from this group and stop receiving emails from it, send an | | | email to puppet-users...@googlegroups.com . | | | | | | To view this discussion on the web visit | | | https://groups.google.com/d/msgid/puppet-users/5bdf2b86-f716-4921-a3b5-e7977947fb2b%40googlegroups.com | | | . | | | | | | For more options, visit https://groups.google.com/d/optout . | | | | -- | You received this message because you are subscribed to the Google Groups | "Puppet Users" group. | To unsubscribe from this group and stop receiving emails from it, send an | email to puppet-users+unsubscr...@googlegroups.com . | To view this discussion on the web visit | https://groups.google.com/d/msgid/puppet-users/96645f88-e8e2-4f8c-9366-2a8d999c5e06%40googlegroups.com | . | For more options, visit https://groups.google.com/d/optout . -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/1073577765.52616241.1414526431538.JavaMail.zimbra%40sfu.ca. For more options, visit https://groups.google.com/d/optout.
