Jira (PUP-6554) Can't run puppet resource on agent with environment specified in main section

[Paul Anderson (JIRA)]

Title: Message Title

Paul Anderson updated an issue   Puppet / PUP-6554 Can't run puppet resource on agent with environment specified in main section Change By: Paul Anderson Affects Version/s: PUP 4.5.2 Environment: RHEL 7 Master and Agent Copy default production environment to "development" Have console refresh modules Create development environment group in classifier, pin the agent Configure agent to include "environment = development" in the main section of puppet.conf Do puppet runs to everyones satisfaction CS Impact: When these three things are true, the customer can't use puppet client commands on their nodes as expected: 1. Code manager with separate environments 2. Nodes in an environment other than production 3. Mcollective in use 4. environment=[non-production] specified in [main] section of puppet.conf The have to do mental gymnastics to understand why they must add --environment production to every puppet help, puppet resource, etc. command to make it work. Component/s: Breaking Change See also https://tickets.puppetlabs.com/browse/PUP-6048 Given a traditional Prod, Dev, Test scenario, and a desire to use MCollective Given the desire to configure an environment in the agent's puppet.conf to cut down on log messages Given the need to put the environment setting in [main] and not [agent] so that MCollective also knows the environment If one manually runs puppet commands on a non-production client, such as puppet resource, one gets an error: [root@dev-node ~]# puppet resource service puppet ensure=running enable=true /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'development' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound) from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application_support.rb:29:in `push_application_context' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:337:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:128:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /usr/local/bin/puppet:5:in `<main>' However, if one lies about the environment, it works as expected: [root@dev-node ~]# puppet resource service puppet ensure=running enable=true --environment production Notice: /Service[puppet]/ensure: ensure changed 'stopped' to 'running' service { 'puppet':   ensure => 'running',   enable => 'true', } This inconsistency is frustrating to customers, regardless of the reasoning behind it. It requires retraining of their staff doing manual operations and lots of comments in their cron jobs, etc.  Add Comment   This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.