Has anyone ran into this particular issue before? It seems straight forward to have multiple environments, by outlining them in puppet.conf for both server and client, but for some reason is not working. Has anyone have had experience with this particular issue?
Thanks, On Sep 10, 3:14 pm, CraftyTech <[email protected]> wrote: > puppet.conf (server): > > [main] > vardir = /var/lib/puppet > logdir = /var/log/puppet > rundir = /var/run/puppet > reports= log,foreman > clientyamldir = /var/lib/puppet/yaml/node > pluginsync = true > external_nodes = /etc/puppet/external_node.rb > node_terminus = exec > manifest = /etc/puppet/manifests/site.pp > modulepath = /etc/puppet/modules > > [development_prog] > manifest = /code/puppet/manifests/site.pp > modulepath = /code/puppet/modules > > [puppetmasterd] > ssl_client_header = SSL_CLIENT_S_DN > ssl_client_verify_header = SSL_CLIENT_VERIFY > templatedir = /etc/puppet/manifests/templates > clientyamldir = /var/lib/puppet/yaml/node > reportdir = /var/lib/puppet/reports > storeconfigs = true > dbadapter = mysql > dbuser = app_puppet > dbpassword = xxxxxxxxxxxx > dbserver = localhost > dbsocket = /sql/mysql/mysql.sock > rrddir = /var/lib/puppet/rrd > rrdinterval = $runinterval > rrdgraph = true > > [puppetd] > report = true > > Puppet.conf (client): > [puppetd] > environment = development_prog > report = true > listen = true > runinterval = 43200 > > Yet, when I run "puppetd -t" it still tries to use the external > node classifier, and it ignores the development_prog setting... What > am I missing here? Does the fact that I foreman as an external node > classifier precludes me from using an alternate dev environment > locally? Please advise. > > Cheers, -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
