On Monday, April 13, 2015 at 11:44:05 AM UTC-5, Chris Cox wrote:
>
> So... I have an environment called "dev" and before I had pulled in a 
> module from puppet forge (e.g. stdlib) into "dev".  All worked fine.
>
> Now I have created a different environment called "devforge" and moved the 
> stdlib module into it.
>
> So... I thought I could then create a dev/environment.conf file with:
>
> modulepath = 
> site:dist:modules:$confdir/environments/devforge/modules:$basemodulepath
>
> And that then any "include stdlib" for the "dev" environment would find 
> the module out of "devforge" using the modulepath... but the nodes can't 
> seem to find it (stdlib)?  I have a valid site.pp in "devforge" and the 
> envionment shows up under PE as being an environment.
>
> What am I missing?
>
>
I don't immediately recognize anything wrong with the configuration you 
describe.  Moreover, I note that whether "devforge" is a valid environment 
is completely irrelevant to whether another module should be able to 
achieve the intended effect by including 
"$confdir/environments/devforge/modules" in its own modulepath.

I'm inclined to suppose that something else is happening here.  Did the 
ownership or permissions (or ACLs or SELinux labels) change on any of the 
directories or files you moved?  Is it possibly something dumb, such as 
having moved stdlib into the wrong directory (e.g. 
$confdir/environments/devforge/modules/modules/stdlib), or having reverted 
to a version where they were never moved at all?

Details of the issue aside, have you considered putting modules that are 
intended to be shared across environments somewhere outside the 
environments/ subtree?


John

-- 
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/4034469c-9caa-418e-9ca4-b0426281f33f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to