-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make agent 'environment' optional #593
Comments
As a workaround I have been doing this trick:
|
Thanks for that tip Vadym. I suspect if do this, I will still get errors when I change a host's directory environment. It seems the puppet master (or agent) can't handle the fact that the agent is specifying one environment when the master is specifying another. Unfortunately I don't have the error message on hand. When I'm next in the office, I'll see if I can get it. Cheers, |
PRs welcome :) |
I'll ask my clients if they're happy for me to spend the time on it and if they are, I'll submit a PR. |
For reference, the issue I mentioned earlier in this thread is PUP-7734 (https://tickets.puppetlabs.com/browse/PUP-7734). I'd be able to work around it if I could remove the environment setting from puppet.conf. I'm still waiting for word on whether or not I can spend the time on this. I imagine the change itself would take a minute or two, but it's the associated tests that will take the time (for me). Cheers, |
In the current implementation, the default value refers to the fact |
I do change the environment by running the agent once with
|
Sorry to dig up an old issue, but I'm wondering if there's a good solution for this to make I've been running into this while trying to perform lookups from our Puppet servers. We're not specifying
All we have defined to include the class is |
Hi,
It would be great if you could make the agent's environment setting in puppet.conf be optional (see https://github.com/theforeman/puppet-puppet/blob/master/manifests/agent/config.pp#L10). Quite often when I change an agent's environment (using Foreman), puppet fails all subsequent agent runs until I manually fix the puppet.conf on the agent to remove the environment setting, or change it to be the correct environment. I imagine this is a bug in puppet (agent v5.5.1), but it would also be handy if we could drop this setting entirely from the puppet.conf.
Given that most Puppet Foreman users would be forcing the directory environment from the server side, I'm surprised to see this setting is being forced.
Many thanks,
Nick George
The text was updated successfully, but these errors were encountered: