Jira (FACT-1380) Restore --timing option to native facter
Title: Message Title Jeremy Adams commented on FACT-1380 Re: Restore --timing option to native facter +1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-7435) Add support for snap packages
Title: Message Title Jeremy Adams commented on PUP-7435 Re: Add support for snap packages snap is the preferred install method for kubectl cli per https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-snap-on-ubuntu Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-4182) add a flag to get JSON output from puppet resource
Title: Message Title Jeremy Adams commented on PUP-4182 Re: add a flag to get JSON output from puppet resource Larissa Lane FYI, we were wrestling with this earlier today, trying to get a list of ec2_instance resources with certain tags. Turns out that YAML output is somewhat broken and thus workarounds don't work. Also, modern tools are expected to have JSON output option. https://tickets.puppetlabs.com/browse/PUP-7808 https://ask.puppet.com/question/4847/can-puppet-resource-user-answer-json/ Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3375) File Diffs on Windows
Title: Message Title Jeremy Adams commented on PUP-3375 Re: File Diffs on Windows One method here: https://forge.puppet.com/jpadams/windows_diff_enable Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-5624) Properties (in resource types) should allow a read-only designation
Title: Message Title Jeremy Adams commented on PUP-5624 Re: Properties (in resource types) should allow a read-only designation The approach suggested by Adam Buxton above for ((puppet resource}} would be a huge improvement for the new user trying to learn how to write DSL as it would keep them from trying to manage readonly attributes. 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 (PDOC-161) As a developer I want to programmatically retrieve the name and short description from a puppet class
Title: Message Title Jeremy Adams commented on PDOC-161 Re: As a developer I want to programmatically retrieve the name and short description from a puppet class +1 to a tag called summary that will appear at least in the context of puppet classes, though I wouldn't be opposed to it showing up in the other types as well: "puppet_classes": [ ], "defined_types": [ ], "resource_types": [ ], "providers": [ ], "puppet_functions": [ ] }
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' 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' command Change By: Jeremy Adams Summary: If no matching local $environment folder on agent, error when running any 'puppet config' 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.
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config'
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' 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.
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
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.
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' 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' command Change By: Jeremy Adams Comment: [~paul.anderson] You're correct about 'produciton' being special. I'll amend the description. 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' 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' command The really use case that raised this is the fact that we wanted to set certname, server, and environment in puppet.conf on install. So you can't do this [root@pup-vra7-0444 ~]# puppet config set environment dev [root@pup-vra7-0444 ~]# puppet config set certname foobar /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 `'
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' 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' command SIMPLE REPRO: [root@pup-vra7-0443 ~]# puppet config set environment foo [root@pup-vra7-0443 ~]# 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 'foo' 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-0443 ~]# puppet config print
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' 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' command
Change By:
Jeremy Adams
If no matching local $environment folder on agent, error when running any 'puppet config' 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' command
Title: Message Title Jeremy Adams assigned an issue to Unassigned Puppet / PUP-6739 If no matching local $environment folder on agent, error when running any 'puppet config' command Change By: Jeremy Adams Assignee: Eric Sorenson 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' 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' command
Change By:
Jeremy Adams
If no matching local $environment folder on agent, error when running any 'puppet config' 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).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' 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' command Change By: Jeremy Adams Affects Version/s: PUP 4.7.0 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' 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' command Change By: Jeremy Adams Component/s: AIO 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' 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' command
Change By:
Jeremy Adams
If no matching local $environment folder on agent, error when running any 'puppet config' command.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) .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' command
Title: Message Title Jeremy Adams assigned an issue to Eric Sorenson Puppet / PUP-6739 If no matching local $environment folder on agent, error when running any 'puppet config' command Change By: Jeremy Adams Assignee: Eric Sorenson 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' 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' command [root@pup-vra7-0407 ~]# cat /etc/puppetlabs/puppet/puppet.conf # This file can be used to override the default puppet settings. # See the following links for more details on what settings are available: # - https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html # - https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html # - https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html # - https://docs.puppetlabs.com/puppet/latest/reference/configuration.html [main] server = tse-puppetmaster2-prod.tse.puppetlabs.net certname = pup-vra7-0407.tse.puppetlabs.net
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' 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' command Change By: Jeremy Adams Priority: Normal Major 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' 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' command
Change By:
Jeremy Adams
If no matching local $environment folder on agent, error when running any 'puppet config' command.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, by default, but NO OTHER environment folders exist.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' 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' command
Change By:
Jeremy Adams
If no matching local $environment folder on agent, error when running any 'puppet config' command.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, by default, but NO OTHER environment folders exist.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}[root@pup-vra7-0403 ~]# puppet config set environment devo 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
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' 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' command
Change By:
Jeremy Adams
If no matching local $environment folder on agent, error when running any 'puppet config' command.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, by default, but NO OTHER environment folders exist.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}[root@pup-vra7-0403 ~]# puppet config set environment devo/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
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' 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' command
Change By:
Jeremy Adams
If no matching local $environment folder on agent, error when running any 'puppet config' command.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, by default, but NO OTHER environment folders exist.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} [root@pup-vra7-0403 ~]# puppet config set environment devo/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
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' 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' command
Change By:
Jeremy Adams
If no matching local $environment folder on agent, error when running any 'puppet config' command.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, by default, but NO OTHER environment folders exist.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}{code}
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' 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' command Change By: Jeremy Adams Summary: If $environment is set in puppet.conf and no matching local $ environment folder on agent, error when running any 'puppet config' 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.
Jira (PUP-6739) If $environment is set in puppet.conf and no matching local environment folder on agent, error when running any 'puppet config' command
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If $environment is set in puppet.conf and no matching local environment folder on agent, error when running any 'puppet config' command
Change By:
Jeremy Adams
Currently when the puppet-agent package is installed on a system, and any {{puppet}} command is run, if the configuration setting of {{environment}} is set to a {{$value}} (other than {{production}}) and the config setting of {{server}} is not set, a local lookup will be made for an environment with a corresponding directory on the agent of {{/etc/puppetlabs/code/environments/$value}}. If this directory exists, the command will complete successfully. If not, this error is thrown:{panel}In this example, the setting of {{environment = dev}} was in {{puppet.conf}}.{code} from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /opt/puppetlabs/puppet/bin/puppet:5:in `'/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:128:in `run'{code}{panel}This is usually masked by the fact that {{production}} is the default environment and gets special treatment.If {{server}} is not required, everything "just works" for {{production}} even if the environment directory is missing on the agent. In fact, if the directory is missing and a {{puppet agent -t}} run is initiated, the directory will be recreated.{panel}{code}[root@centos7b ~]# rm -rf /etc/puppetlabs/code/environments/production/[root@centos7b ~]# puppet agent -tNotice: /File[/etc/puppetlabs/code/environments/production]/ensure: createdInfo: Caching certificate for caInfo: csr_attributes file loading from /etc/puppetlabs/puppet/csr_attributes.yamlInfo: Creating a new SSL certificate request for centos7b.syd.puppet.vm...{code}{panel}*Desired Behavior:*Instead of the current behavior, if a command that requires the {{server}} setting is run, commonly {{puppet agent -t}}, then an appropriate error about the lack of a puppet master server setting should be thrown. Currently the error is a little cryptic:{panel}{code}Error: Could not request certificate: getaddrinfo: No address associated with hostname{code}{panel}Other {{puppet}} commands such as {{puppet config}}, {{puppet resource}} should not care about the {{environment}} setting and shouldn't throw any error regardless of the state of the {{server}} or {{environment}} settings.If a {{puppet}} command requries {{environment}}, most commonly {{puppet apply}}, but not {{server}}, it shouldn't matter what {{server}} is set to, but throwing an error for a missing environment directory is appropriate.https://docs.puppet.com/puppet/latest/reference/services_apply.html#main-manifest*Reproduction and Workarounds:*{panel}{code}MASTER='
Jira (PUP-6739) If $environment is set in puppet.conf and no matching local environment folder on agent, error when running any 'puppet' command
Title: Message Title Jeremy Adams updated an issue Puppet / PUP-6739 If $environment is set in puppet.conf and no matching local environment folder on agent, error when running any 'puppet' command Change By: Jeremy Adams Summary: If $environment is set in puppet.conf and no matching local environment folder on agent, error when running any 'puppet' command will result in search for environment directory locally on agent 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 $environment is set in puppet.conf and no matching local environment folder on agent, error when running any 'puppet config' command
Title: Message Title Jeremy Adams updated an issue Puppet / PUP-6739 If $environment is set in puppet.conf and no matching local environment folder on agent, error when running any 'puppet config' command Change By: Jeremy Adams Summary: If $environment is set in puppet.conf and no matching local environment folder on agent, error when running any 'puppet config ' 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.
Jira (PUP-6739) If $environment is set in puppet.conf running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title Jeremy Adams updated an issue Puppet / PUP-6739 If $environment is set in puppet.conf running any 'puppet' command will result in search for environment directory locally on agent Change By: Jeremy Adams Summary: If $environment is set and $server is not set, in puppet.conf running any 'puppet' command will result in search for environment directory locally on agent 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 $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title Jeremy Adams commented on PUP-6739 Re: If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent environment was 'production' [root@pup-vra7-0403 ~]# puppet config set environment dev [root@pup-vra7-0403 ~]# puppet agent -t Info: Using configured environment 'dev' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Info: Caching catalog for pup-vra7-0403.tse.puppetlabs.net Info: Applying configuration version '1480890889' Info: Redefining firewalld_port in Puppet::Type Notice: Applied catalog in 1.52 seconds
Jira (PUP-6447) Allow UTF8 files to have a leading BOM to be more tolerant of files produced on Windows
Title: Message Title Jeremy Adams commented on PUP-6447 Re: Allow UTF8 files to have a leading BOM to be more tolerant of files produced on Windows Recently when doing an integration in _javascript_ that wrote a facter fact in JSON, I encountered this issue. Facter would not tolerate UTF-8 with a BOM for the structured JSON fact. var command = "New-Item -path '" + factsDir + "' -type directory -force \n" + "$MyPath = '" + factsFile + "' \n" + "$MyFile = " + oneLineFacts + " \n" + "$Utf8NoBomEncoding = New-Object System.Text.UTF8Encoding($False) \n" + "[System.IO.File]::WriteAllLines($MyPath, $MyFile, $Utf8NoBomEncoding)"; Add Comment
Jira (PUP-6739) If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Change By:
Jeremy Adams
Currently when the puppet-agent package is installed on a system, and any {{puppet}} command is run, if the configuration setting of {{environment}} is set to a {{$value}} (other than {{production}}) and the config setting of {{server}} is not set, a local lookup will be made for an environment with a corresponding directory on the agent of {{/etc/puppetlabs/code/environments/$value}}. If this directory exists, the command will complete successfully. If not, this error is thrown:{panel}In this example, the setting of {{environment = dev}} was in {{puppet.conf}}.{code} from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /opt/puppetlabs/puppet/bin/puppet:5:in `'/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:128:in `run'{code}{panel}This is usually masked by the fact that {{production}} is the default environment and gets special treatment.If {{server}} is not required, everything "just works" for {{production}} even if the environment directory is missing on the agent. In fact, if the directory is missing and a {{puppet agent -t}} run is initiated, the directory will be recreated.{panel}{code}[root@centos7b ~]# rm -rf /etc/puppetlabs/code/environments/production/[root@centos7b ~]# puppet agent -tNotice: /File[/etc/puppetlabs/code/environments/production]/ensure: createdInfo: Caching certificate for caInfo: csr_attributes file loading from /etc/puppetlabs/puppet/csr_attributes.yamlInfo: Creating a new SSL certificate request for centos7b.syd.puppet.vm...{code}{panel}*Desired Behavior:*Instead of the current behavior, if a command that requires the {{server}} setting is run, commonly {{puppet agent -t}}, then an appropriate error about the lack of a puppet master server setting should be thrown. Currently the error is a little cryptic:{panel}{code}Error: Could not request certificate: getaddrinfo: No address associated with hostname{code}{panel}Other {{puppet}} commands such as {{puppet config}}, {{puppet resource}} should not care about the {{environment}} setting and shouldn't throw any error regardless of the state of the {{server}} or {{environment}} settings.If a {{puppet}} command requries {{environment}}, most commonly {{puppet apply}}, but not {{server}}, it shouldn't matter what {{server}} is set to, but throwing an error for a missing environment directory is appropriate.https://docs.puppet.com/puppet/latest/reference/services_apply.html#main-manifest*Reproduction and Workarounds:*{panel}{code}MASTER='
Jira (PUP-6739) If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Change By:
Jeremy Adams
Currently when the puppet-agent package is installed on a system, and any {{puppet}} command is run, if the configuration setting of {{environment}} is set to a {{$value}} and the config setting of {{server}} is not set, a local lookup will be made for an environment with a corresponding directory on the agent of {{/etc/puppetlabs/code/environments/$value}}. If this directory exists, the command will complete successfully. If not, this error is thrown:{panel}In this example, the setting of {{environment = dev}} was in {{puppet.conf}}.{code} from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /opt/puppetlabs/puppet/bin/puppet:5:in `'/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:128:in `run'{code}{panel}This is usually masked by the fact that {{production}} is the default environment and gets special treatment.If {{server}} is not required, everything "just works" for {{production}} even if the environment directory is missing on the agent. In fact, if the directory is missing and a {{puppet agent -t}} run is initiated, the directory will be recreated.{panel}{code}[root@centos7b ~]# rm -rf /etc/puppetlabs/code/environments/production/[root@centos7b ~]# puppet agent -tNotice: /File[/etc/puppetlabs/code/environments/production]/ensure: createdInfo: Caching certificate for caInfo: csr_attributes file loading from /etc/puppetlabs/puppet/csr_attributes.yamlInfo: Creating a new SSL certificate request for centos7b.syd.puppet.vm...{code}{panel}*Desired Behavior:*Instead of the current behavior, if a command that requires the {{server}} setting is run, commonly {{puppet agent -t}}, then an appropriate error about the lack of a puppet master server setting should be thrown. Currently the error is a little cryptic:{panel}{code}Error: Could not request certificate: getaddrinfo: No address associated with hostname{code}{panel}Other {{puppet}} commands such as {{puppet config}}, {{puppet resource}} should not care about the {{environment}} setting and shouldn't throw any error regardless of the state of the {{server}} or {{environment}} settings.If a {{puppet}} command requries {{environment}}, most commonly {{puppet apply}}, but not {{server}}, it shouldn't matter what {{server}} is set to, but throwing an error for a missing environment directory is appropriate.https://docs.puppet.com/puppet/latest/reference/services_apply.html#main-manifest*Reproduction and Workarounds:*{panel}{code}MASTER=''ENVIRONMENT='dev'AGENT_PKG='puppet-agent-1.6.2-1.el7.x86_64.rpm'PLATFORM='el-7-x86_64'# uncomment the
Jira (PUP-6739) If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Change By:
Jeremy Adams
Currently when the puppet-agent package is installed on a system, and any {{puppet}} command is run, if the configuration setting of {{environment}} is set to a {{$value}} and the config setting of {{server}} is not set, a local lookup will be made for an environment with a corresponding directory on the agent of {{/etc/puppetlabs/code/environments/$value}}. If this directory exists, the command will complete successfully. If not, this error is thrown:{panel}In this example, the setting of {{environment = dev}} was in {{puppet.conf}}.{code} from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /opt/puppetlabs/puppet/bin/puppet:5:in `'/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:128:in `run'{code}{panel}This is usually masked by the fact that {{production}} is the default environment and gets special treatment.If {{server}} is not required, everything "just works" for {{production}} even if the environment directory is missing on the agent. In fact, if the directory is missing and a {{puppet agent -t}} run is initiated, the directory will be recreated.{panel}{code}[root@centos7b ~]# rm -rf /etc/puppetlabs/code/environments/production/[root@centos7b ~]# puppet agent -tNotice: /File[/etc/puppetlabs/code/environments/production]/ensure: createdInfo: Caching certificate for caInfo: csr_attributes file loading from /etc/puppetlabs/puppet/csr_attributes.yamlInfo: Creating a new SSL certificate request for centos7b.syd.puppet.vm...{code}{panel}*Desired Behavior:*Instead of the current behavior, if a command that requires the {{server}} setting is run, commonly {{puppet agent -t}}, then an appropriate error about the lack of a puppet master server setting should be thrown. Currently the error is a little cryptic:{panel}{code}Error: Could not request certificate: getaddrinfo: No address associated with hostname{code}{panel}Other {{puppet}} commands such as {{puppet config}}, {{puppet resource}} should not care about the {{environment}} setting and shouldn't throw any error regardless of the state of the {{server}} or {{environment}} settings. An exception is If a command requries {{ puppet apply environment }}, which does care about most commonly {{ environment puppet apply }} , but not {{server}} , it shouldn't matter what {{server}} is set to, but throwing an error for a missing environment directory is appropriate .https://docs.puppet.com/puppet/latest/reference/services_apply.html#main-manifest*Reproduction and Workarounds:*{panel}{code}MASTER='
Jira (PUP-6739) If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Change By:
Jeremy Adams
Currently when the puppet-agent package is installed on a system, and any {{puppet}} command is run, if the configuration setting of {{environment}} is set to a {{$value}} and the config setting of {{server}} is not set, a local lookup will be made for an environment with a corresponding directory on the agent of {{/etc/puppetlabs/code/environments/$value}}. If this directory exists, the command will complete successfully. If not, this error is thrown:{panel}In this example, the setting of {{environment = dev}} was in {{puppet.conf}}.{code} from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /opt/puppetlabs/puppet/bin/puppet:5:in `'/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:128:in `run'{code}{panel}This is usually masked by the fact that {{production}} is the default environment and gets special treatment.If {{server}} is not required, everything "just works" for {{production}} even if the environment directory is missing on the agent. In fact, if the directory is missing and a {{puppet agent -t}} run is initiated, the directory will be recreated.{panel}{code}[root@centos7b ~]# rm -rf /etc/puppetlabs/code/environments/production/[root@centos7b ~]# puppet agent -t --environment production Notice: /File[/etc/puppetlabs/code/environments/production]/ensure: created Info: Caching certificate for caInfo: csr_attributes file loading from /etc/puppetlabs/puppet/csr_attributes.yamlInfo: Creating a new SSL certificate request for centos7b.syd.puppet.vm... {code}{panel}*Desired Behavior:*Instead of the current behavior, if a command that requires the {{server}} setting is run, commonly {{puppet agent -t}}, then an appropriate error about the lack of a puppet master server setting should be thrown. Currently the error is a little cryptic:{panel}{code}Error: Could not request certificate: getaddrinfo: No address associated with hostname{code}{panel}Other {{puppet}} commands such as {{puppet config}}, {{puppet resource}} should not care about the {{environment}} setting and shouldn't throw any error regardless of the state of the {{server}} or {{environment}} settings.An exception is {{puppet apply}}, which does care about {{environment}} but not {{server}}.https://docs.puppet.com/puppet/latest/reference/services_apply.html#main-manifest*Reproduction and Workarounds:*{panel}{code}MASTER=''ENVIRONMENT='dev'AGENT_PKG='puppet-agent-1.6.2-1.el7.x86_64.rpm'PLATFORM='el-7-x86_64'# uncomment the next line and the error goes away#mkdir -p /etc/puppetlabs/code/environments/$ENVIRONMENTcurl -k -O
Jira (PUP-6739) If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Change By:
Jeremy Adams
Currently when the puppet-agent package is installed on a system, and any {{puppet}} command is run, if the configuration setting of {{environment}} is set to a {{$value}} and the config setting of {{server}} is not set, a local lookup will be made for an environment with a corresponding directory on the agent of {{/etc/puppetlabs/code/environments/$value}}. If this directory exists, the command will complete successfully. If not, this error is thrown:{panel}In this example, the setting of {{environment = dev}} was in {{puppet.conf}}.{code} from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /opt/puppetlabs/puppet/bin/puppet:5:in `'/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:128:in `run'{code}{panel}This is usually masked by the fact that a {{production}} is the default environment and gets special treatment.If {{server}} is not required, everything "just works" for {{production}} even if the environment directory exists by default is missing on the agent . In fact, if the directory is missing and a {{puppet agent -t}} run is initiated, the directory will be recreated. {panel} {code}[root@centos7b ~]# rm -rf /etc/puppetlabs/code/environments/production/[root@centos7b ~]# puppet agent -t --environment productionNotice: /File[/etc/puppetlabs/code/environments/production]/ensure: created{code}{panel} *Desired Behavior:*Instead of the current behavior, if a command that requires the {{server}} setting is run, commonly {{puppet agent -t}}, then an appropriate error about the lack of a puppet master server setting should be thrown. Currently the error is a little cryptic:{panel}{code}Error: Could not request certificate: getaddrinfo: No address associated with hostname{code}{panel}Other {{puppet}} commands such as {{puppet config}}, {{puppet resource}} should not care about the {{environment}} setting and shouldn't throw any error regardless of the state of the {{server}} or {{environment}} settings.An exception is {{puppet apply}}, which does care about {{environment}} but not {{server}}.https://docs.puppet.com/puppet/latest/reference/services_apply.html#main-manifest*Reproduction and Workarounds:*{panel}{code}MASTER=''ENVIRONMENT='dev'AGENT_PKG='puppet-agent-1.6.2-1.el7.x86_64.rpm'PLATFORM='el-7-x86_64'# uncomment the next line and the error goes away#mkdir -p /etc/puppetlabs/code/environments/$ENVIRONMENTcurl -k -O https://${MASTER}:8140/packages/current/$PLATFORM/$AGENT_PKGrpm -i ./$AGENT_PKG# switch the order of the next two lines and the error goes awaypuppet config set
Jira (PUP-6739) If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title Jeremy Adams commented on PUP-6739 Re: If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent Paul Anderson You're correct about 'produciton' being special. I'll amend the description. 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 $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Change By:
Jeremy Adams
Currently when the puppet-agent package is installed on a system, and any {{puppet}} command is run, if the configuration setting of {{environment}} is set to a {{$value}} and the config setting of {{server}} is not set, a local lookup will be made for an environment with a corresponding directory on the agent of {{/etc/puppetlabs/code/environments/$value}}. If this directory exists, the command will complete successfully. If not, this error is thrown:{panel}In this example, the setting of {{environment = dev}} was in {{puppet.conf}}.{code} from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /opt/puppetlabs/puppet/bin/puppet:5:in `'/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:128:in `run'{code}{panel}This is usually masked by the fact that a {{production}} environment directory exists by default.*Desired Behavior:*Instead of the current behavior, if a command that requires the {{server}} setting is run, commonly {{puppet agent -t}}, then an appropriate error about the lack of a puppet master server setting should be thrown. Currently the error is a little cryptic:{panel}{code}Error: Could not request certificate: getaddrinfo: No address associated with hostname{code}{panel}Other {{puppet}} commands such as {{puppet config}}, {{puppet resource}} should not care about the {{environment}} setting and shouldn't throw any error regardless of the state of the {{server}} or {{environment}} settings.An exception is {{puppet apply}}, which does care about {{environment}} but not {{server}}.https://docs.puppet.com/puppet/latest/reference/services_apply.html#main-manifest*Reproduction and Workarounds :*{panel}{code}MASTER=''ENVIRONMENT='dev'AGENT_PKG='puppet-agent-1.6.2-1.el7.x86_64.rpm'PLATFORM='el-7-x86_64'# uncomment the next line and the error goes away#mkdir -p /etc/puppetlabs/code/environments/$ENVIRONMENTcurl -k -O https://${MASTER}:8140/packages/current/$PLATFORM/$AGENT_PKGrpm -i ./$AGENT_PKG# switch the order of the next two lines and the error goes awaypuppet config set environment $ENVIRONMENT --section mainpuppet config set server $MASTER --section main#puppet config set server $MASTER --section main#puppet config set environment $ENVIRONMENT --section mainpuppet agent -t{code}{panel}{panel}{code}MASTER=''ENVIRONMENT='dev'# uncomment the next line and the error goes away#mkdir -p /etc/puppetlabs/code/environments/$ENVIRONMENTcurl -k https://${MASTER}:8140/packages/current/install.bash | bash -s \main:environment=$ENVIRONMENT# In agent installer, this invocation ensures
Jira (PUP-6739) If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Change By:
Jeremy Adams
Currently when the puppet-agent package is installed on a system, and any {{puppet}} command is run, if the configuration setting of {{environment}} is set to a {{$value}} and the config setting of {{server}} is not set, a local lookup will be made for an environment with a corresponding directory on the agent of {{/etc/puppetlabs/code/environments/$value}}. If this directory exists, the command will complete successfully. If not, this error is thrown:{panel}In this example, the setting of {{environment = dev}} was in {{puppet.conf}}.{code} from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /opt/puppetlabs/puppet/bin/puppet:5:in `'/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:128:in `run'{code}{panel} This is usually masked by the fact that a {{production}} environment directory exists by default. *Desired Behavior:*Instead of the current behavior, if a command that requires the {{server}} setting is run, commonly {{puppet agent -t}}, then an appropriate error about the lack of a puppet master server setting should be thrown. Currently the error is a little cryptic:{panel}{code}Error: Could not request certificate: getaddrinfo: No address associated with hostname{code}{panel}Other {{puppet}} commands such as {{puppet config}}, {{puppet resource}} should not care about the {{environment}} setting and shouldn't throw any error regardless of the state of the {{server}} or {{environment}} settings.An exception is {{puppet apply}}, which does care about {{environment}} but not {{server}}.https://docs.puppet.com/puppet/latest/reference/services_apply.html#main-manifest*Reproduction:*{panel}{code}MASTER=''ENVIRONMENT='dev'AGENT_PKG='puppet-agent-1.6.2-1.el7.x86_64.rpm'PLATFORM='el-7-x86_64'# uncomment the next line and the error goes away#mkdir -p /etc/puppetlabs/code/environments/$ENVIRONMENTcurl -k -O https://${MASTER}:8140/packages/current/$PLATFORM/$AGENT_PKGrpm -i ./$AGENT_PKG# switch the order of the next two lines and the error goes awaypuppet config set environment $ENVIRONMENT --section mainpuppet config set server $MASTER --section main#puppet config set server $MASTER --section main#puppet config set environment $ENVIRONMENT --section mainpuppet agent -t{code}{panel}{panel}{code}MASTER=''ENVIRONMENT='dev'# uncomment the next line and the error goes away#mkdir -p /etc/puppetlabs/code/environments/$ENVIRONMENTcurl -k https://${MASTER}:8140/packages/current/install.bash | bash -s \main:environment=$ENVIRONMENT# In agent installer, this invocation ensures 'server'
Jira (PUP-6739) If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Change By:
Jeremy Adams
Currently when the puppet-agent package is installed on a system, and any {{puppet}} command is run, if the configuration setting of {{environment}} is set to a {{$value}} and the config setting of {{server}} is not set, a local lookup will be made for an environment with a corresponding directory on the agent of {{/etc/puppetlabs/code/environments/$value}}. If this directory exists, the command will complete successfully. If not, this error is thrown:{panel}In this example, the setting of {{environment = dev}} was in {{puppet.conf}}.{code} from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /opt/puppetlabs/puppet/bin/puppet:5:in `'/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:128:in `run'{code}{panel}* Desired Behavior:*Instead of the current behavior, if a command that requires the {{server}} setting is run, commonly {{puppet agent -t}}, then an appropriate error about the lack of a puppet master server setting should be thrown. Currently the error is a little cryptic:{panel}{code}Error: Could not request certificate: getaddrinfo: No address associated with hostname{code}{panel}Other {{puppet}} commands such as {{puppet config}}, {{puppet resource}} should not care about the {{environment}} setting and shouldn't throw any error regardless of the state of the {{server}} or {{environment}} settings.An exception is {{puppet apply}}, which does care about {{environment}} but not {{server}}.https://docs.puppet.com/puppet/latest/reference/services_apply.html#main-manifest* Reproduction:*{panel}{code}MASTER=''ENVIRONMENT='dev'AGENT_PKG='puppet-agent-1.6.2-1.el7.x86_64.rpm'PLATFORM='el-7-x86_64'# uncomment the next line and the error goes away#mkdir -p /etc/puppetlabs/code/environments/$ENVIRONMENTcurl -k -O https://${MASTER}:8140/packages/current/$PLATFORM/$AGENT_PKGrpm -i ./$AGENT_PKG# switch the order of the next two lines and the error goes awaypuppet config set environment $ENVIRONMENT --section mainpuppet config set server $MASTER --section main#puppet config set server $MASTER --section main#puppet config set environment $ENVIRONMENT --section mainpuppet agent -t{code}{panel}{panel}{code}MASTER=''ENVIRONMENT='dev'# uncomment the next line and the error goes away#mkdir -p /etc/puppetlabs/code/environments/$ENVIRONMENTcurl -k https://${MASTER}:8140/packages/current/install.bash | bash -s \main:environment=$ENVIRONMENT# In agent installer, this invocation ensures 'server' setting is set before running 'puppet' commands#curl -k
Jira (PUP-6739) If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Change By:
Jeremy Adams
Currently when the puppet-agent package is installed on a system, and any {{puppet}} command is run, if the configuration setting of {{environment}} is set to a {{$value}} and the config setting of {{server}} is not set, a local lookup will be made for an environment with a corresponding directory on the agent of {{/etc/puppetlabs/code/environments/$value}}. If this directory exists, the command will complete successfully. If not, this error is thrown:{panel}In this example, the setting of {{environment = dev}} was in {{puppet.conf}}.{code} from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /opt/puppetlabs/puppet/bin/puppet:5:in `'/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:128:in `run'{code}{panel}*Reproduction:*{panel}{code}MASTER=''ENVIRONMENT='dev'AGENT_PKG='puppet-agent-1.6.2 .163.gba93fa8 -1.el7.x86_64.rpm'PLATFORM='el-7-x86_64'# uncomment the next line and the error goes away#mkdir -p /etc/puppetlabs/code/environments/$ENVIRONMENTcurl -k -O https://${MASTER}:8140/packages/current/$PLATFORM/$AGENT_PKGrpm -i ./$AGENT_PKG# switch the order of the next two lines and the error goes awaypuppet config set environment $ENVIRONMENT --section mainpuppet config set server $MASTER --section main#puppet config set server $MASTER --section main#puppet config set environment $ENVIRONMENT --section mainpuppet agent -t{code}{panel}{panel}{code}MASTER=''ENVIRONMENT='dev'# uncomment the next line and the error goes away#mkdir -p /etc/puppetlabs/code/environments/$ENVIRONMENTcurl -k https://${MASTER}:8140/packages/current/install.bash | bash -s \main:environment=$ENVIRONMENT# In agent installer, this invocation ensures 'server' setting is set before running 'puppet' commands#curl -k https://${MASTER}:8140/packages/current/install.bash | bash -s \#main:server=$MASTER main:environment=$ENVIRONMENT{code}{panel}
Add Comment
Jira (PUP-6739) If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent
Title: Message Title Jeremy Adams created an issue Puppet / PUP-6739 If $environment is set and $server is not set, running any 'puppet' command will result in search for environment directory locally on agent Issue Type: Bug Assignee: Unassigned Created: 2016/09/25 1:35 PM Priority: Normal Reporter: Jeremy Adams Currently when the puppet-agent package is installed on a system, and any puppet command is run, if the configuration setting of environment is set to a $value and the config setting of server is not set, a local lookup will be made for an environment with a corresponding directory on the agent of /etc/puppetlabs/code/environments/$value. If this directory exists, the command will complete successfully. If not, this error is thrown: In this example, the setting of environment = dev was in puppet.conf. from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute'
Jira (PUP-6587) `puppet module search --render-as json` returns non-JSON first line on STDOUT
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6587
`puppet module search --render-as json` returns non-JSON first line on STDOUT
Change By:
Jeremy Adams
As a user wanting to parse JSON returned from puppet module tool,I need puppet module tool to return only JSON on {{ stdout }} so I can pipe it to thenext tool in my pipeline such as {{jq}}.Currently two lines are returned on {{stdout}} . The second line contains the JSON output, while, the first line is:{{Notice: Searching https://forgeapi.puppetlabs.com ...}}That line should not appear on the standard output {{stdout}} .To make the JSON parseable, you need to strip off the first line, currently.Since a lot of JSON is returned to the screen, it wasn't clear at first what the problem was. A possible solution would be to return the {{Notice: Searching https://forgeapi.puppetlabs.com ...}} message on {{stderr}} instead of {{stdout}}.
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.
Jira (PUP-6587) `puppet module search --render-as json` returns non-JSON first line on stdout
Title: Message Title Jeremy Adams updated an issue Puppet / PUP-6587 `puppet module search --render-as json` returns non-JSON first line on stdout Change By: Jeremy Adams Summary: `puppet module search --render-as json` returns non-JSON first line on STDOUT stdout 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.
Jira (PUP-6587) `puppet module search --render-as json` returns non-JSON first line on STDOUT
Title: Message Title Jeremy Adams created an issue Puppet / PUP-6587 `puppet module search --render-as json` returns non-JSON first line on STDOUT Issue Type: Bug Assignee: Unassigned Created: 2016/08/04 11:04 PM Priority: Normal Reporter: Jeremy Adams As a user wanting to parse JSON returned from puppet module tool, I need puppet module tool to return only JSON on stdout so I can pipe it to the next tool in my pipeline such as jq. Currently two lines are returned. The second line contains the JSON output, while, the first line is: Notice: Searching https://forgeapi.puppetlabs.com ... That line should not appear on the standard output. To make the JSON parseable, you need to strip off the first line, currently. Since a lot of JSON is returned to the screen, it wasn't clear at first what the problem was. Add Comment
Jira (PUP-6575) Disambiguate puppet agent -t and puppet apply -t with quick feedback
Title: Message Title Jeremy Adams commented on PUP-6575 Re: Disambiguate puppet agent -t and puppet apply -t with quick feedback +1 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.
Jira (PUP-6561) PUP-6099 breaks mounted filesystem permissions
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6561
PUP-6099 breaks mounted filesystem permissions
Change By:
Jeremy Adams
Because one can only manage a file resource ONCE, PUP-6099 causes scenarios with mounted filesystems to break.Consider the following scenario:{{include lvmfile { ['/apps'] :ensure => directory,owner => nobody,group => nobody,mode => '0700',}physical_volume { '/dev/sdb':ensure => present,}volume_group { 'vg0':ensure => present,physical_volumes => '/dev/sdb',}lvm::logical_volume { 'apps':volume_group => 'vg0',size => '1G',fs_type => 'ext3',mountpath_require => false,before => File['/apps'],{}}}With the above code, the permissions on /apps are not set correctly as described in the file resource until the next puppet run, in which case /apps may be unavailable or have security issues or ??? for half an hour by default.To address the issue, the customer user may feel the need to do silly things, such as this:{{lvm::logical_volume { 'apps':volume_group => 'vg0',size => '1G',fs_type => 'ext3',mountpath_require => false,} ->exec { '/bin/chown nobody /apps' : } ->exec { '/bin/chgrp nobody /apps' : } ->exec { '/bin/chmod 0700 /apps' : }}}I would therefore suggest we come up with a solution that allows us to intelligently address this situation:create directory -> mount filesystem -> manage ownership/permissionsThe puppetlabs-lvm module avoids this by using an exec to create the directory, which would then allow a file resource to manage the directory ownership/permissions afterwards.Perhaps we could add a parameter that defaults to current behavior, that if toggled would not auto require the parent directory?
Add Comment
Jira (FACT-1356) External facts should be able to return structured data
Title: Message Title Jeremy Adams commented on FACT-1356 Re: External facts should be able to return structured data Could use a convention like facts.yaml.sh, facts.yaml.py, facts.yaml.pl facts.json.sh, facts.json.py, facts.yaml.pl 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.
Jira (FACT-1285) Docs correction. Need "$" in example.
Title: Message Title Jeremy Adams created an issue Facter / FACT-1285 Docs correction. Need "$" in example. Issue Type: Bug Assignee: Unassigned Created: 2015/12/13 12:35 PM Priority: Normal Reporter: Jeremy Adams At https://docs.puppetlabs.com/puppet/latest/reference/lang_data_number.html#converting-strings-to-numbers docs show this snippet with missing "$": Add 0 to manually convert a string to a number. (For example, $mystring = "85"; $mynum = 0 + mystring.) should be this with $ on second $mystring variable: Add 0 to manually convert a string to a number. (For example, $mystring = "85"; $mynum = 0 + $mystring.)
Jira (FACT-1285) Docs correction. Need "$" in example.
Title: Message Title Jeremy Adams updated an issue Facter / FACT-1285 Docs correction. Need "$" in example. Change By: Jeremy Adams Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5558) "--app_management" feature flag should be listed under `puppet help parser validate`
Title: Message Title Jeremy Adams commented on PUP-5558 Re: "--app_management" feature flag should be listed under `puppet help parser validate` If users run `puppet parser validate` on manifests with App Orchestration language elements they'll get cryptic errors like Error: Could not parse for environment production: This Type-Name has no effect. A value-producing _expression_ without other effect may only be placed last in a block/sequence at /Users/jeremy/src/app_orch/app_orchestration/appmgmt_blog/manifests/db.pp:15:3 and there is no hint that there is a "--app_management" feature flag that could help when running "puppet help parser validate": USAGE: puppet parser validate [] [ ...] This action validates Puppet DSL syntax without compiling a catalog or syncing any resources. If no manifest files are provided, it will validate the default site manifest. RETURNS: Nothing, or the first syntax error encountered.
Jira (FACT-1259) Option to flatten facter facts for easier command line search
Title: Message Title Jeremy Adams commented on FACT-1259 Re: Option to flatten facter facts for easier command line search The reason for the idea was that I was trying to find facts that had a "version" subkey to them and couldn't do it easily from the command line using common tools like grep, cut, etc that are line-based. So yes, the idea that both the output of facter itself which produces all of the keys and values, as well as the value of something like facter os or facter.os.release should have an option where a set of single, "self-contained"/"fully qualified" lines is returned. For example: # facter --flat os.release os.release.major => "14" os.release.minor => "5" os.release.full => "14.5.0" As an aside, among SysAdmins multi-line log files are seen as an anti-pattern largely because they are harder to search with basic tools like grep. http://juliusdavies.ca/logging.html#grep http://gojko.net/2006/12/09/logging-anti-patterns/ https://today.java.net/article/2006/04/04/exception-handling-antipatterns#multilineLogMessages http://www.masterzen.fr/2013/01/13/the-10-commandments-of-logging/ (assumed in here by examples) Imagine log lines from different services going into a master log like /var/log/messages and the problems interleaving of mult-line logs cause. Add Comment
Jira (FACT-1259) Option to flatten facter facts for easier command line search
Title: Message Title Jeremy Adams commented on FACT-1259 Re: Option to flatten facter facts for easier command line search I'm a big fan of jq, but it's much harder to find all of the facts that contain the subkey "major", for example. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1259) Option to flatten facter facts for easier command line search
Title: Message Title
Jeremy Adams updated an issue
Facter / FACT-1259
Option to flatten facter facts for easier command line search
Change By:
Jeremy Adams
If I want to find facts that have a subkey in them somewhere (like "version" or "release" or "address"), I cannot use a utility like grep easily because of structured facts' multiline output format. So instead of this:{code}# facter os{ architecture => "x86_64", family => "RedHat", hardware => "x86_64", name => "CentOS", release => {full => "6.6",major => "6",minor => "6" }, selinux => {enabled => false }}{code}I'd like something like this:{code}# facter --flat osos.architecure => "x86_64"os.family => "RedHat"os.hardware => "x86_64"os.name => "CentOS"os.release.full => "6.6"os.release.major => "6"os.release.minor => "6"os.selinux.enabled => " false " {code}Less lines of output and I can use grep!
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1259) Option to flatten facter facts for easier command line search
Title: Message Title
Jeremy Adams created an issue
Facter / FACT-1259
Option to flatten facter facts for easier command line search
Issue Type:
Story
Assignee:
Unassigned
Created:
2015/10/19 12:54 PM
Priority:
Normal
Reporter:
Jeremy Adams
If I want to find facts that have a subkey in them somewhere (like "version" or "release" or "address"), I cannot use a utility like grep easily because of structured facts' multiline output format.
So instead of this:
# facter os
{
architecture => "x86_64",
family => "RedHat",
Jira (FACT-777) Facter should not downcase fact names
Title: Message Title Jeremy Adams created an issue Facter / FACT-777 Facter should not downcase fact names Issue Type: Bug Assignee: Eric Sorenson Created: 2015/01/12 10:54 AM Priority: Normal Reporter: Jeremy Adams I cannot find a document that says that fact names must be downcase, but if you create a mixed-case fact, facter will downcase it for you: https://github.com/puppetlabs/facter/search?utf8=%E2%9C%93q=downcase Users believe that mixed-case facts can be referenced in Puppet since mixed-case variables are acceptable: https://docs.puppetlabs.com/puppet/latest/reference/lang_reserved.html If a user creates a mixed-case fact and then uses the mixed-case fact name in their Puppet code, then the fact will have no value. http://serverfault.com/questions/651995/why-arent-my-puppet-variables-getting-assigned-by-vagrants-puppet-facter-optio Add Comment
Jira (PUP-1098) Package/source should accept puppet:// files
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-1098
Package/source should accept puppet:// files
Change By:
Jeremy Adams
Sometimesyouneedtousebackportedpackagesondebian-likesystem(wecouldeasilyimagineusecasesforotherplatforms).Inwork/productionenvironments,it'squiteraretohavedirectlyaccesstotheInternetforsecurityreasons.Sopackagetypeshouldacceptasourcelocatedonthepuppetmasterfilebucket,whereasitonlyacceptslocalpackagesforthemoment.Saiddifferently,I'dliketoturnthiskindofawfulrecipe: pre code classapache2-passenger{package{libapache2-mod-passenger:ensure=installed,provider=dpkg,source=/tmp/mod-passenger.debrequire=File[tmp-passenger]}file{tmp-passenger:name=/tmp/mod-passenger.deb,owner=root,group=root,source=puppet:///files/redmine/libapache2-mod-passenger_2.2.11debian-1~bpo50+1_i386.deb}} /pre Intosomethinglikethis:preclassapache2-passenger{package{libapache2-mod-passenger:ensure=installed,provider=dpkg,source=puppet:///files/passenger/libapache2-mod-passenger_2.2.11debian-1~bpo50+1_i386.deb}}/ pre code Letmeknowyouropinionaboutthat.Thanks!
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1098) Package/source should accept puppet:// files
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-1098
Package/source should accept puppet:// files
Change By:
Jeremy Adams
Sometimesyouneedtousebackportedpackagesondebian-likesystem(wecouldeasilyimagineusecasesforotherplatforms).Inwork/productionenvironments,it'squiteraretohavedirectlyaccesstotheInternetforsecurityreasons.Sopackagetypeshouldacceptasourcelocatedonthepuppetmasterfilebucket,whereasitonlyacceptslocalpackagesforthemoment.Saiddifferently,I'dliketoturnthiskindofawfulrecipe: { code } classapache2-passenger{package{libapache2-mod-passenger:ensure=installed,provider=dpkg,source=/tmp/mod-passenger.debrequire=File[tmp-passenger]}file{tmp-passenger:name=/tmp/mod-passenger.deb,owner=root,group=root,source=puppet:///files/redmine/libapache2-mod-passenger_2.2.11debian-1~bpo50+1_i386.deb}} {code} Intosomethinglikethis: pre {code} classapache2-passenger{package{libapache2-mod-passenger:ensure=installed,provider=dpkg,source=puppet:///files/passenger/libapache2-mod-passenger_2.2.11debian-1~bpo50+1_i386.deb}} / { code } Letmeknowyouropinionaboutthat.Thanks!
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2157) CLONE - Package/source should accept puppet:// files
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-2157
CLONE - Package/source should accept puppet:// files
Issue Type:
New Feature
Assignee:
Unassigned
Created:
04/Apr/14 5:52 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
Sometimes you need to use backported packages on debian-like system (we could easily imagine use cases for other platforms). In work/production environments, it's quite rare to have directly access to the Internet for security reasons. So package type should accept a source located on the puppet master filebucket, whereas it only accepts local packages for the moment.
Said differently, I'd like to turn this kind of awful recipe :
class apache2-passenger {
package {libapache2-mod-passenger:
ensure = installed,
provider = dpkg,
source = /tmp/mod-passenger.deb
require = File[tmp-passenger]
}
file {tmp-passenger:
name = /tmp/mod-passenger.deb,
owner = root,
group = root,
source = puppet:///files/redmine/libapache2-mod-passenger_2.2.11debian-1~bpo50+1_i386.deb
}
}
Into something like this :
class apache2-passenger {
package {libapache2-mod-passenger:
ensure = installed,
provider = dpkg,
source =
Jira (PUP-1098) Package/source should accept puppet:// files
Title: Message Title Jeremy Adams updated an issue Puppet / PUP-1098 Package/source should accept puppet:// files Change By: Jeremy Adams Labels: customer redmine Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
