Bug #1051
Modulepath not working with environments
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | - | |||
| Target version: | - | |||
| Affected Puppet version: | 0.25.4 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
I was asked to create a ticket for this weeks ago but have been away. Very sorry it took so long.
I’m testing the new environments feature in 0.24.1.
http://reductivelabs.com/trac/puppet/wiki/UsingMultipleEnvironments
But I am having a problem getting it to recognise the modulepath setting within the environment.
For this example, the environments are called “prod” and “test”.
On the puppetmaster puppet.conf has these entries related to environments:
[main]
environment = prod
environments=prod,test
modulepath = /base/default/modules
[prod]
modulepath = /base/prod/modules
manifest = /base/prod/site.pp
[test]
modulepath = /base/test/modules
manifest = /base/test/site.pp
My modules are in /base/test/modules and /base/prod/modules for each environment.
If I run puppetd on the client and specify the environment as “prod” or “test”, it will find the correct manifest file but it does not pick up any of the modules.
If set modulepath in the “main"section like this, so that the module path is set to one of the environment’s modulepaths:
[main]
environment = prod
environments=prod,test
modulepath = /base/prod/modules
[prod]
modulepath = /base/prod/modules
manifest = /base/prod/site.pp
[test]
modulepath = /base/test/modules
manifest = /base/test/site.pp
then puppetd on the client finds the modules in that directory. So it’s as if it is ignoring the modulepath setting in the environment and using the setting in the “main” section.
History
Updated by Luke Kanies over 4 years ago
- Status changed from 1 to Closed
- 7 set to duplicate
Sorry, I already filed and fixed it (to be released in 0.24.2).
Dupe of #1017.