Bug #7277
closed
Changing environment on UI does not change puppet.conf
Description
Changing a node from Development env to Prod env on the Foreman UI does not change the puppet.conf on the node and puppet classes fail
Noticed on Foreman 1.5.2
Steps :
1. Build a node in Dev
2. Change the env of the node to Prod on Foreman UI and apply classes from Prod env
3. Trigger puppet run
Updated by Dominic Cleal over 10 years ago
- Status changed from New to Feedback
Fail, how? File retrieval?
Puppet 3 will follow the ENC's (Foreman's) view of the environment and should ignore whatever is in puppet.conf. Puppet 2 is buggy in this area and may follow a bit of both.
Updated by Neeraj Harikrishnan over 10 years ago
Yes on file retrival. I am running puppet 2.7. I will upgrade puppet and check.
err: /Stage[main]/Ulimits/File[/etc/security/limits.conf]: Could not evaluate: Could not retrieve information from environment development source(s) puppet:///modules/ulimits/limits.conf at /etc/puppet/environments/production/modules/ulimits/manifests/init.pp:6
Updated by Anonymous almost 8 years ago
- Status changed from Feedback to Rejected
works as designed (by puppet).
Updated by Marek Hulán over 7 years ago
- Related to Feature #21391: Client's puppet.conf environment variable should be updated if the Web Interface changes the puppet environment for the Host Group added