Red Hat Bugzilla – Bug 1270789
Missing environment parameter in puppet document.
Last modified: 2016-11-11 16:09:53 EST
Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/pdf/User_Guide/Red_Hat_Satellite-6.1-User_Guide-en-US.pdf
Section Number and Name: 12.6, Configuring the Puppet Agent
Describe the issue:
puppet "environment" is missing in agent section of puppet.conf configuration.
Suggestions for improvement:
For correct syntax please refer:
If environment is not set puppet agent throws warning
Local environment: "production" doesn't match server specified node environment "KT_Environment", switching agent to "KT_Environment".
Here is sample
# The file in which puppetd stores a list of the classes
# associated with the retrieved configuratiion. Can be loaded in
# the separate ``puppet`` executable using the ``--loadclasses``
# The default value is '$confdir/classes.txt'.
classfile = $vardir/classes.txt
pluginsync = true
report = true
ignoreschedules = true
daemon = false
ca_server = satellite.example.com
server = satellite.example.com
environment = KT_Example_Org_Library_RHEL6Server_3
# Where puppetd caches the local configuration. An
# extension indicating the cache format is added automatically.
# The default value is '$confdir/localconfig'.
localconfig = $vardir/localconfig
Just to confirm.
This is the case when using puppet 126.96.36.199.el5sat, I'm assuming it's the case with the RHEL5 version of the client, and RHEL6 works fine without the Environment being set.
Assigning to Brandi for review.
Brandi - looks like a quick fix to either add the 'environment' variable to the example in the documentation or a 'Note' box if it only applies to a specific version of RHEL, but we may need to raise a needinfo here to confirm this first.