Yup, I just figured out (by randomly twiddling knobs) that certname is the
culprit.
We try to run with repo-only code, so I am reluctant to patch package
binaries. When do you guys expect to have 3.7.3 out? And what terrible
thing will happen if I simply keep 'certname' disabled?
Thanks!
On Tuesday, October 28, 2014 4:01:05 PM UTC-4, Victor Danilchenko wrote:
>
> Hi all,
>
> Quick background: I am migrating my company's Puppetmaster installation
> from 3.4 to 3.7 (on Centos 6, using PuppetLabs RPM repo), and
> simultaneously migrating to directory environments; or, more accurately,
> trying to. The problem is that my Puppet installation recognizes that
> environments exist (specifying non-existent environment throws an error)
> but ignores manifests, modules, and environment.conf within it ('puppet
> module list' returns 'no modules found', it doesn't find my node
> manifests, and overriding modulepath in environment.conf has no effect). Gory
> details here
> <https://groups.google.com/forum/#!topic/puppet-users/LKiESGFnjBI>.
>
> So, trying to debug this myself, I decided to do some code spelunking,
> attempting to find why Puppet fails to read my
> environments/production/modules directory. In doing so, I quickly
> realized that the puppet code follows a pretty fancy execution path, and I
> really have no idea how to find where something *isn't* happening.
>
> Therefore, I am asking for help. Can anyone tell me where in the code
> Puppet 3.7.2 is *supposed *to read the environment contents? I am pretty
> sure that once I know where to look for failure, which module/class/method,
> I should be able to determine exactly why it fails.
>
> Thanks in advance!
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/08363354-1277-429d-b24f-c5d919366056%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
