Re-sending after reading your situation more carefully.
We are using PE 3.7.2 with r10k and directory environments, so I don't know
how specifically useful this will be since you're still using config
environments. Directory environments / PE use basemodulepath now (I'm not
sure about config e
We are using PE 3.7.2 with r10k, so I don't know how specifically useful
this will be, but PE requires the use of basemodulepath.
https://docs.puppetlabs.com/puppet/latest/reference/config_file_environment.html
puppet.conf on master:
[main]
basemodulepath =
/etc/puppetlabs/puppet/modules:/o
Done anyone have any thoughts on this?
On Friday, May 8, 2015 at 2:23:27 PM UTC-5, Jim Miller wrote:
>
> Hi all,
>
> Just upgraded from 3.4.something to 3.7.5 and it seems how we were doing
> environments is depreciated. I've followed a couple of docs* for how to do
> this but seem to be miss
And finally when I add back to puppet.conf my environment, everything is
found correctly:
[test]
manifest = $confdir/manifests/non-prod_site.pp
modulepath =
$confdir/environments/test/modules:$confdir/environments/test/site/modules
[ ~ ]# puppet config print --environment test |grep
Still wrestling with this. Puppet is now seeing 'part' of the module paths
but not all of them, one thing I had to change was using an absolute path
and not '$confdir' and it's not using the correct site.pp file
"non-prod_site.pp"
[ ~ ]# puppet config print --environment test |grep env
environ
I do have one update to this. The issue seems to be the modulepath, and
what comes after the ':'
modulepath = $confdir/environments/dev/modules:
$confdir/environments/dev/site/modules
Puppet is not finding catalogs/modules after the ':'
err: Could not retrieve catalog from remote server: Error
