Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Title: Message Title Jeremy Adams commented on PUP-6739 Re: If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command Eric Sorenson I'm not opposed to 'puppet module list' having that behavior, it was just something additional that I found that is related to this (uses the same underlying code). My main issue is that on an agent, I want to configure settings such as server, certname, environment during bootstrap, and the environment I specify is referring to an environment on the master, the settings in puppet.conf should not depend on the state of the agent's filesystem. A case of excessive error checking. I agree with 'puppet module' complaining about non-existent environments. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Title: Message Title Eric Sorenson commented on PUP-6739 Re: If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command Jeremy Adams if you are doing this from a script, can you also make the directory as part of your scripting? i'm not sure it's the config read/write subsystem's responsibility to manage stuff on the filesystem. Because it makes total sense to me that if you set the environment to a non existent directory and then try to run 'puppet module list' from that environment, you get an error. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6739 If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command Change By: Geoff Nichols Sprint: AP Triage Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Change By:
Jeremy Adams
If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command.See REPRO REPROs in comment below.For example, if you have an environment called 'dev' on the master, and you want to set an agent's $environment from the default of 'production' to 'dev', you might issue a {{puppet config set environment dev}} comand. When run, {{puppet config}} will look up the current environment ('production' at this point) and ensure there is a corresponding 'production' folder in the environments path. Assume this succeeds because a 'production' folder exists locally on the agent, by default, but NO OTHER environment folders exist locally on the agent (and shouldn't need to exist in my view).Now the environment is set to 'dev'.If a user issues any {{puppet config}} command at this point, the current environment ('dev' at this point) will NOT have a corresponding environment folder, so we get an error like:{code}Could not find a directory environment named 'dev' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist?{code}{code}[root@pup-vra7-0403 ~]# puppet config set environment production/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'dev' 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:132: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 `'{code}This means we're stuck and cannot issue any {{puppet config print}} or {{puppet config set}} commands even to get us back to an environment setting of 'production'!
Add Comment
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Change By:
Jeremy Adams
If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command.See REPROs in comment comments below.For example, if you have an environment called 'dev' on the master, and you want to set an agent's $environment from the default of 'production' to 'dev', you might issue a {{puppet config set environment dev}} comand. When run, {{puppet config}} will look up the current environment ('production' at this point) and ensure there is a corresponding 'production' folder in the environments path. Assume this succeeds because a 'production' folder exists locally on the agent, by default, but NO OTHER environment folders exist locally on the agent (and shouldn't need to exist in my view).Now the environment is set to 'dev'.If a user issues any {{puppet config}} command at this point, the current environment ('dev' at this point) will NOT have a corresponding environment folder, so we get an error like:{code}Could not find a directory environment named 'dev' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist?{code}{code}[root@pup-vra7-0403 ~]# puppet config set environment production/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'dev' 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:132: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 `'{code}This means we're stuck and cannot issue any {{puppet config print}} or {{puppet config set}} commands even to get us back to an environment setting of 'production'!
Add Comment
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Change By:
Jeremy Adams
If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command.See REPRO in comment below.For example, if you have an environment called 'dev' on the master, and you want to set an agent's $environment from the default of 'production' to 'dev', you might issue a {{puppet config set environment dev}} comand. When run, {{puppet config}} will look up the current environment ('production' at this point) and ensure there is a corresponding 'production' folder in the environments path. Assume this succeeds because a 'production' folder exists locally on the agent, by default, but NO OTHER environment folders exist locally on the agent (and shouldn't need to exist in my view).Now the environment is set to 'dev'.If a user issues any {{puppet config}} command at this point, the current environment ('dev' at this point) will NOT have a corresponding environment folder, so we get an error like:{code}Could not find a directory environment named 'dev' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist?{code}{code}[root@pup-vra7-0403 ~]# puppet config set environment production/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'dev' 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:132: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 `'{code}This means we're stuck and cannot issue any {{puppet config print}} or {{puppet config set}} commands even to get us back to an environment setting of 'production'!
Add Comment
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Title: Message Title Jeremy Adams commented on PUP-6739 Re: If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command Also affects puppet module command: [root@pup-vra7-0444 ~]# puppet module list /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'dev' 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:132: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 `' [root@pup-vra7-0444 ~]# puppet module install stahnma-epel
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Title: Message Title Jeremy Adams updated an issue Puppet / PUP-6739 If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command Change By: Jeremy Adams Summary: If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
