Bug #4390
closed
Dynamic environments broken
Description
Hello,
We use puppet dynamic environments in our platform to make changes without effecting the entire platform.
We put our 'shared/common' modules in /etc/puppet/modules and copies of some of these modules inside the environment to do dev/test.
Looking at the Foreman code for dynamic envs it should do the following, look in /etc/puppet/environments/$environment/modules add all classes then look in /etc/puppet/modules and add any additional classes. What appears to happen is it only looks in /etc/puppet/environments/$environment/modules and ignores /etc/puppet/modules
Dynamic set:
[master]
# Dynamic environments
modulepath = /etc/puppet/environments/$environment/modules:/etc/puppet/modules
If we use static envs as below it appears to work as expected and pull classes from both paths.
[dev]
modulepath = /etc/puppet/environments/dev/modules:/etc/puppet/modules
-
This is currently causing us major issues as foreman is removing classes what the puppetmaster would accept believing they do not existing in the dynamic env.
ii foreman 1.4.0-1 amd64 Systems management web interface
ii foreman-proxy 1.4.0-1 all RESTful proxies for DNS, DHCP, TFTP, and Puppet
Updated by Ohad Levy over 9 years ago
- Status changed from New to Feedback
- Priority changed from High to Normal
I assume this is already resolved, can you please confirm?
thanks
Updated by Nathan Flynn over 9 years ago
With the recent changes to puppet environments it invalidates this fault.
I don't see a way to close the ticket.
Updated by Dominic Cleal over 9 years ago
- Status changed from Feedback to Resolved
Thanks for confirming. The new dynamic environments mode makes our implementation more reliable as we simply call out to Puppet to get the env list, instead of trying to replicate its logic.