|
Michael Smith I only noticed it using 'facter -p agent_specified_environment' and in /etc/puppetlabs/mcollective/facts.yaml. With environment set in the [main] section this works. If the environment is in the [agent] section, no dice.
puppet.conf:
server = pe-201620-master.example.com
|
#environment = nothing
|
[agent]
|
certname = pe-201620-agent2
|
environment = nothing
|
Run: /opt/puppetlabs/puppet/bin/refresh-mcollective-metadata
[root@pe-201620-agent2 ~]# cat /etc/puppetlabs/mcollective/facts.yaml | grep agent_spec
[root@pe-201620-agent2 ~]#
[root@pe-201620-agent2 ~]# facter -p agent_specified_environment
(no output)
Edit puppet.conf:
[main]
|
server = pe-201620-master.example.com
|
environment = nothing
|
[agent]
|
certname = pe-201620-agent2
|
#environment = nothing
|
Run: /opt/puppetlabs/puppet/bin/refresh-mcollective-metadata
[root@pe-201620-agent2 ~]# cat /etc/puppetlabs/mcollective/facts.yaml | grep agent_spec
agent_specified_environment: nothing
[root@pe-201620-agent2 ~]#
[root@pe-201620-agent2 ~]# facter -p agent_specified_environment
nothing
|
