Jira (PUP-7844) A Puppet report from an interrupted run can cause exit_status to throw an exception
Title: Message Title Past Haus created an issue Puppet / PUP-7844 A Puppet report from an interrupted run can cause exit_status to throw an exception Issue Type: Bug Affects Versions: PUP 4.10.6 Assignee: Unassigned Created: 2017/08/15 11:43 AM Priority: Normal Reporter: Past Haus Recently when playing around with reports in irb, I discovered that the exit_status method raises an exception when called against a report from an interrupted (ctrl + c or other) puppet run. irb(main):007:0> a.exit_status NoMethodError: undefined method `[]' for nil:NilClass from /Users/matthaus/src/puppet/lib/puppet/transaction/report.rb:380:in `exit_status'
Jira (PUP-7844) A Puppet report from an interrupted run can cause exit_status to throw an exception
Title: Message Title Past Haus commented on PUP-7844 Re: A Puppet report from an interrupted run can cause exit_status to throw an exception Karen Van der Veer Nope, not this. 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-7836) [SPIKE] Analysis of Heira 3 to 5 upgrade strategy
Title: Message Title Past Haus updated an issue Puppet / PUP-7836 [SPIKE] Analysis of Heira 3 to 5 upgrade strategy Change By: Past Haus Sprint: ETC 2017-9-5 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-7787) Module tool gives cryptic error when downloading a PE only module with no license file
Title: Message Title Past Haus commented on PUP-7787 Re: Module tool gives cryptic error when downloading a PE only module with no license file Also weird that there is a space (%20) and not a + in the module_groups query-param. 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-7787) Module tool gives cryptic error when downloading a PE only module with no license file
Title: Message Title Past Haus commented on PUP-7787 Re: Module tool gives cryptic error when downloading a PE only module with no license file --trace output puppet module install puppetlabs-sqlserver --trace Notice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ... Notice: Downloading from https://forgeapi.puppet.com ... Error: bad URI(is not URI?): /v3/releases?module=puppetlabs-sqlserver_groups=base pe_only /opt/puppetlabs/puppet/lib/ruby/2.1.0/uri/generic.rb:1203:in `rescue in merge' /opt/puppetlabs/puppet/lib/ruby/2.1.0/uri/generic.rb:1200:in `merge' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/forge.rb:105:in `fetch' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/vendor/semantic_puppet/lib/semantic_puppet/dependency.rb:81:in `block in fetch_releases' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/vendor/semantic_puppet/lib/semantic_puppet/dependency.rb:80:in `each'
Jira (PUP-7787) Module tool gives cryptic error when downloading a PE only module with no license file
Title: Message Title Past Haus created an issue Puppet / PUP-7787 Module tool gives cryptic error when downloading a PE only module with no license file Issue Type: Bug Assignee: Unassigned Components: PMT Created: 2017/07/19 10:09 AM Priority: Normal Reporter: Past Haus On a system without a license file in /etc/puppetlabs/license.key I tried to download the PE only sqlserver module. Here's what happened next: puppet module install puppetlabs-sqlserver Notice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ... Notice: Downloading from https://forgeapi.puppet.com ...
Jira (PUP-7787) Module tool gives cryptic error when downloading a PE only module with no license file
Title: Message Title Past Haus commented on PUP-7787 Re: Module tool gives cryptic error when downloading a PE only module with no license file This was definitely puppet 4. whatever is in head of glisan right now. 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-7787) Module tool gives cryptic error when downloading a PE only module with no license file
Title: Message Title Past Haus commented on PUP-7787 Re: Module tool gives cryptic error when downloading a PE only module with no license file Here is a run with --http_debug and --trace: puppet module install puppetlabs-sqlserver --trace --http_debug Notice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ... Notice: Downloading from https://forgeapi.puppet.com ... opening connection to forgeapi.puppet.com:443... opened starting SSL for forgeapi.puppet.com:443... SSL established <- "GET /v3/releases?module=puppetlabs-sqlserver_groups=base%20pe_only HTTP/1.1\r\nUser-Agent: PMT/1.1.1 (v3; Net::HTTP) Puppet/4.10.5 Ruby/2.1.9-p490 (x86_64-linux)\r\nAccept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3\r\nAccept: */*\r\nHost: forgeapi.puppet.com\r\n\r\n" -> "HTTP/1.1 403 Forbidden\r\n"
Jira (PUP-7787) Module tool gives cryptic error when downloading a PE only module with no license file
Title: Message Title
Past Haus updated an issue
Puppet / PUP-7787
Module tool gives cryptic error when downloading a PE only module with no license file
Change By:
Past Haus
Comment:
--trace output{code}puppet module install puppetlabs-sqlserver --traceNotice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ...Notice: Downloading from https://forgeapi.puppet.com ...Error: bad URI(is not URI?): /v3/releases?module=puppetlabs-sqlserver_groups=base pe_only/opt/puppetlabs/puppet/lib/ruby/2.1.0/uri/generic.rb:1203:in `rescue in merge'/opt/puppetlabs/puppet/lib/ruby/2.1.0/uri/generic.rb:1200:in `merge'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/forge.rb:105:in `fetch'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/vendor/semantic_puppet/lib/semantic_puppet/dependency.rb:81:in `block in fetch_releases'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/vendor/semantic_puppet/lib/semantic_puppet/dependency.rb:80:in `each'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/vendor/semantic_puppet/lib/semantic_puppet/dependency.rb:80:in `fetch_releases'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/vendor/semantic_puppet/lib/semantic_puppet/dependency.rb:157:in `block in fetch_dependencies'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/vendor/semantic_puppet/lib/semantic_puppet/dependency.rb:155:in `each'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/vendor/semantic_puppet/lib/semantic_puppet/dependency.rb:155:in `fetch_dependencies'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/vendor/semantic_puppet/lib/semantic_puppet/dependency.rb:55:in `query'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/module_tool/applications/installer.rb:216:in `build_dependency_graph'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/module_tool/applications/installer.rb:87:in `run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/module_tool/applications/application.rb:12:in `run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/face/module/install.rb:127:in `block (3 levels) in '/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/interface/action.rb+eval[wrapper]:242:in `install'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/face_base.rb:252:in `main'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:366:in `run_command'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:358:in `block in run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:662:in `exit_on_fail'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:358:in `run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute'/opt/puppetlabs/puppet/bin/puppet:5:in `'Error: Try 'puppet help module install' for usage{code}
Jira (PUP-7787) Module tool gives cryptic error when downloading a PE only module with no license file
Title: Message Title Past Haus commented on PUP-7787 Re: Module tool gives cryptic error when downloading a PE only module with no license file At a brief glance, it looks like the fetch method in /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/forge.rb is raising an exception based on the 403 returned by the forge. 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-7630) "Successful" puppet agent reports hide provider errors
Title: Message Title
Past Haus commented on PUP-7630
Re: "Successful" puppet agent reports hide provider errors
Something similar happens if the entire run fails due to a cycle in the graph.
For example...
matthaus@wyclef-2 #> puppet apply -e 'file {"/tmp/foo": ensure => present, require => File["/tmp/foo"],}'
Notice: Compiled catalog for localhost in environment production in 0.08 seconds
Error: Failed to apply catalog: Found 1 dependency cycle:
(File[/tmp/foo] => File[/tmp/foo])
Try the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz
matthaus@wyclef-2 #> echo $?
1
matthaus@wyclef-2 #> irb
irb(main):001:0> require 'puppet'
=> true
Jira (PUP-7977) Add a password_script attribute to user resource
Title: Message Title Past Haus moved an issue Puppet / PUP-7977 Add a password_script attribute to user resource Change By: Past Haus Affected Organization/s: Colruyt Key: PE PUP - 14398 7977 Project: Puppet Enterprise [Internal] 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-7978) PMT Should Install Modules as pe-puppet / create the modules directory as pe-puppet
Title: Message Title Past Haus moved an issue Puppet / PUP-7978 PMT Should Install Modules as pe-puppet / create the modules directory as pe-puppet Change By: Past Haus Affects Version/s: PE 2016.1.1 Key: PE PUP - 14550 7978 Project: Puppet Enterprise [Internal] 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-7844) A Puppet report from an interrupted run can cause exit_status to throw an exception
Title: Message Title Past Haus updated an issue Puppet / PUP-7844 A Puppet report from an interrupted run can cause exit_status to throw an exception Change By: Past Haus Release Notes: Not Needed 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-7844) A Puppet report from an interrupted run can cause exit_status to throw an exception
Title: Message Title Past Haus updated an issue Puppet / PUP-7844 A Puppet report from an interrupted run can cause exit_status to throw an exception Change By: Past Haus Release Notes: Bug Fix Not Needed 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-7844) A Puppet report from an interrupted run can cause exit_status to throw an exception
Title: Message Title Past Haus commented on PUP-7844 Re: A Puppet report from an interrupted run can cause exit_status to throw an exception Removed Moses Mendoza' release note because it isn't needed. 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-7844) A Puppet report from an interrupted run can cause exit_status to throw an exception
Title: Message Title Past Haus updated an issue Puppet / PUP-7844 A Puppet report from an interrupted run can cause exit_status to throw an exception Change By: Past Haus Release Notes Summary: Puppet will now exit -1 if a run is interrupted rather than raising an exception. 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-8000) Puppet lookup should be aware of node classification class parameters
Title: Message Title Past Haus commented on PUP-8000 Re: Puppet lookup should be aware of node classification class parameters Henrik Lindberg It looks like --compile doesn't get the ENC data. In PE, puppet_enterprise::pcp_broker_host is set as a class param whose value is the certname of the master. However, when I run puppet lookup --compile puppet_enterprise::pcp_broker_host I get no results. puppet lookup --compile puppet_enterprise::pcp_broker_host --explain Warning: Module 'puppet_enterprise': Value returned from data_hash function 'hocon_data', when using location '/etc/puppetlabs/enterprise/conf.d/pe.conf', must use keys qualified with the name of the module Warning: Module 'pe_repo': Value returned from data_hash function 'hocon_data', when using location '/etc/puppetlabs/enterprise/conf.d/pe.conf', must use keys qualified with the name of the module Warning: Module 'pe_repo': Value returned from data_hash function 'hocon_data', when using location '/etc/puppetlabs/enterprise/conf.d/pe.conf', must use keys qualified with the name of the module Searching for "puppet_enterprise::pcp_broker_host" Global Data Provider (hiera configuration version 5) Using configuration "/etc/puppetlabs/puppet/hiera.yaml" Hierarchy entry "Classifier Configuration Data"
Jira (PUP-8000) Puppet lookup should be aware of node classification class parameters
Title: Message Title Past Haus updated an issue Puppet / PUP-8000 Puppet lookup should be aware of node classification class parameters Change By: Past Haus Attachment: Screen Shot 2017-10-03 at 4.18.13 PM.png 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-8009) Performance regression with lots of modules and gettext
Title: Message Title Past Haus commented on PUP-8009 Re: Performance regression with lots of modules and gettext Ah awesome, I wasn't aware of that PR. Seems like it would be worth capturing some data from 4.10 puppet so we have a target to aim for with i18n enabled them? 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-8000) lookup CLI should be able to lookup (already set) class parameters
Title: Message Title Past Haus commented on PUP-8000 Re: lookup CLI should be able to lookup (already set) class parameters That's exactly it Henrik Lindberg. 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-8009) Performance regression with lots of modules and gettext
Title: Message Title Past Haus commented on PUP-8009 Re: Performance regression with lots of modules and gettext Michael Smith It seems like some investigation work to try to get a reproduction with just puppet and its dependencies might be worthwhile. That might allow us to create either a benchmark in puppet itself or some other modestly lightweight test that would prevent regressing on the issue (and also allow us to gather numbers from glisan, before the regression was introduced). There aren't any tickets around that yet are there? 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 (HI-579) Begin hardcoding hiera version into gemspec
Title: Message Title Past Haus commented on HI-579 Re: Begin hardcoding hiera version into gemspec Garrett Guillotte No. 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 (PDB-3300) Add command for deleting node data
Title: Message Title Past Haus updated an issue PuppetDB / PDB-3300 Add command for deleting node data Change By: Past Haus Labels: AWS1 backup-restore 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-1627) Puppet agent's locking is subject to race conditions
Title: Message Title Past Haus updated an issue Puppet / PUP-1627 Puppet agent's locking is subject to race conditions Change By: Past Haus Labels: AWS1 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-2189) The CRL can get corrupted if two workers revoke certs at same time
Title: Message Title Past Haus updated an issue Puppet / PUP-2189 The CRL can get corrupted if two workers revoke certs at same time Change By: Past Haus Labels: AWS1 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-8000) Puppet lookup should be aware of node classification class parameters
Title: Message Title Past Haus commented on PUP-8000 Re: Puppet lookup should be aware of node classification class parameters Thomas Hallgren Classifying class parameters in the console has been a feature since PE 3.7 (https://docs.puppet.com/pe/3.7/release_notes.html#new-features-in-370). This is not a new requirement, however this is something that seems desirable in a lookup. 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-8000) Puppet lookup should be aware of node classification class parameters
Title: Message Title Past Haus commented on PUP-8000 Re: Puppet lookup should be aware of node classification class parameters Henrik Lindberg I'm not sure if an actual compile is required, but the class parameters from the ENC will trump anything from hiera, so whenever the parameters are available they need to be merged over the hiera params. 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-8000) Puppet lookup should be aware of node classification class parameters
Title: Message Title Past Haus commented on PUP-8000 Re: Puppet lookup should be aware of node classification class parameters Thanks Henrik Lindberg. I'll give that a try today. 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-8000) Puppet lookup should be aware of node classification class parameters
Title: Message Title Past Haus commented on PUP-8000 Re: Puppet lookup should be aware of node classification class parameters Yes, it already does happen. What is new is that we need a way to be able to look up final classification results (the combination of ENC and hiera data) outside of the context of a run. It seems like this should be the default behavior of the lookup application (perhaps with flags to give hiera only or enc only results). 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-8000) Puppet lookup should be aware of node classification class parameters
Title: Message Title Past Haus commented on PUP-8000 Re: Puppet lookup should be aware of node classification class parameters I don't actually care where it happens, but if we are exposing a thing to lookup eventual parameters that a node will get in a given catalog compile, it seems like taking the ENC data into account would be super valuable, as there isn't currently a way in the command line to visualize that data. 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-8000) Puppet lookup should be aware of node classification class parameters
Title: Message Title Past Haus created an issue Puppet / PUP-8000 Puppet lookup should be aware of node classification class parameters Issue Type: Improvement Assignee: Thomas Hallgren Attachments: Screen Shot 2017-09-27 at 1.17.28 PM.png Components: Hiera & Lookup Created: 2017/09/27 1:21 PM Priority: Normal Reporter: Past Haus Currently puppet lookup will do a lookup based on hiera backends and report back what the value for a given key is. In PE, this falls short because there may be class parameters applied at the node classifier level. Puppet lookup should take the node classifier into account when returning the lookup, as it will trump any other value. For example, in the attached screenshot I have set java_args on the orchestrator profile in the classifier to include Xms of 128m. When running puppet lookup puppet_enterprise::profile::orchestrator::java_args I would expect to see a return of a hash with a key of "Xms" and a value of "128m", but lookup returns the empty string.
Jira (PUP-7999) Puppet Lookup should be easily used as a library in other applications
Title: Message Title Past Haus created an issue Puppet / PUP-7999 Puppet Lookup should be easily used as a library in other applications Issue Type: Improvement Affects Versions: PUP 5.0.0 Assignee: Thomas Hallgren Components: Hiera & Lookup Created: 2017/09/27 1:12 PM Priority: Normal Reporter: Past Haus Currently in PE, the pe_infrastructure and pe_manager modules end up recreated a large amount of the puppet lookup application logic to do lookups without shelling out to puppet (which would be expensive). It would be far better if puppet itself exposed the lookup as an easy to use method for other applications. Ideally, if I knew the node name, environment name, and a list of keys to lookup, I should be able to invoke the method to retrieve those lookups. Add Comment
Jira (HI-579) Begin hardcoding hiera version into gemspec
Title: Message Title Past Haus created an issue Hiera / HI-579 Begin hardcoding hiera version into gemspec Issue Type: Task Assignee: Unassigned Created: 2017/08/29 3:49 PM Priority: Normal Reporter: Past Haus In https://github.com/puppetlabs/r10k/issues/760, users noticed warnings indicating stack too deep when using r10k with puppet-agent and having more than one version of a dependency of r10k installed. As noted in https://github.com/puppetlabs/r10k/issues/760#issuecomment-325825267, it is because of how rubygems behaves when doing version selection, and also because of how the version of the hiera and puppet gems are declared in their gemspecs. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-7889) Begin hardcoding puppet version into gemspec
Title: Message Title Past Haus created an issue Puppet / PUP-7889 Begin hardcoding puppet version into gemspec Issue Type: Task Assignee: Unassigned Created: 2017/08/29 3:49 PM Priority: Normal Reporter: Past Haus In https://github.com/puppetlabs/r10k/issues/760, users noticed warnings indicating stack too deep when using r10k with puppet-agent and having more than one version of a dependency of r10k installed. As noted in https://github.com/puppetlabs/r10k/issues/760#issuecomment-325825267, it is because of how rubygems behaves when doing version selection, and also because of how the version of the hiera and puppet gems are declared in their gemspecs. Add Comment This message was sent by Atlassian JIRA
Jira (HI-579) Begin hardcoding hiera version into gemspec
Title: Message Title Past Haus assigned an issue to Past Haus Hiera / HI-579 Begin hardcoding hiera version into gemspec Change By: Past Haus Assignee: Past Haus 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 (HI-579) Begin hardcoding hiera version into gemspec
Title: Message Title Past Haus updated an issue Hiera / HI-579 Begin hardcoding hiera version into gemspec Change By: Past Haus Sprint: ETC 2017-9-5 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 (HI-579) Begin hardcoding hiera version into gemspec
Title: Message Title Past Haus updated an issue Hiera / HI-579 Begin hardcoding hiera version into gemspec Change By: Past Haus Team: Enterprise in the Cloud 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-7889) Begin hardcoding puppet version into gemspec
Title: Message Title Past Haus updated an issue Puppet / PUP-7889 Begin hardcoding puppet version into gemspec Change By: Past Haus Sprint: ETC 2017-9-5 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-7889) Begin hardcoding puppet version into gemspec
Title: Message Title Past Haus assigned an issue to Past Haus Puppet / PUP-7889 Begin hardcoding puppet version into gemspec Change By: Past Haus Assignee: Past Haus 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-7889) Begin hardcoding puppet version into gemspec
Title: Message Title Past Haus updated an issue Puppet / PUP-7889 Begin hardcoding puppet version into gemspec Change By: Past Haus Team: Enterprise in the Cloud 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-7889) Begin hardcoding puppet version into gemspec
Title: Message Title Past Haus updated an issue Puppet / PUP-7889 Begin hardcoding puppet version into gemspec Change By: Past Haus Labels: maintenance 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-8000) Puppet lookup should be aware of node classification class parameters
Title: Message Title Past Haus commented on PUP-8000 Re: Puppet lookup should be aware of node classification class parameters The node in question had already checked in. But I did run it again immediately after a puppet run and still got no results. Here is the output: [root@b981wybmc1qhg6a ~]# puppet agent -t Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Info: Caching catalog for b981wybmc1qhg6a.delivery.puppetlabs.net Info: Applying configuration version '1507157846' Notice: Applied catalog in 11.87 seconds [root@b981wybmc1qhg6a ~]# puppet lookup --explain --compile puppet_enterprise::pcp_broker_host Warning: Module 'puppet_enterprise': Value returned from data_hash function
Jira (PUP-8015) Refactor puppet-agent-bootstrap module into something palatable by puppet core
Title: Message Title Past Haus updated an issue Puppet / PUP-8015 Refactor puppet-agent-bootstrap module into something palatable by puppet core Change By: Past Haus Sprint: CODEMGMT To Accept, ETC 2017-10-17 , ETC 2017-10-31 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-8409) Puppet config print lists invalid default value for environment_timeout
Title: Message Title
Past Haus created an issue
Puppet / PUP-8409
Puppet config print lists invalid default value for environment_timeout
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/01/30 4:53 PM
Priority:
Normal
Reporter:
Past Haus
When running puppet config print --all on the command line, the default value for environment_timeout is listed as Infinity, which is not a valid setting (it can be an integer, 0 or unlimited). As a user if I saw this I would presume it was a valid setting.
When I try using Infinity as a setting value for environment_timeout, I get a not so helpful error message and stack trace.
puppet apply --environment_timeout=Infinity -e "notify{'foo':}"
/Users/matthaus/src/puppet/lib/puppet/settings/ttl_setting.rb:43:in `munge': Invalid 'time to live' format '"Infinity"' for parameter: environment_timeout (Puppet::Settings::ValidationError)
from /Users/matthaus/src/puppet/lib/puppet/settings/ttl_setting.rb:25:in `munge'
Jira (PUP-8409) Puppet config print lists invalid default value for environment_timeout
Title: Message Title
Past Haus commented on PUP-8409
Re: Puppet config print lists invalid default value for environment_timeout
The setting is also case sensitive, so passing Unlimited results in a similar error message.
puppet apply --environment_timeout=Unlimited -e "notify{'foo':}"
/Users/matthaus/src/puppet/lib/puppet/settings/ttl_setting.rb:43:in `munge': Invalid 'time to live' format '"Unlimited"' for parameter: environment_timeout (Puppet::Settings::ValidationError)
from /Users/matthaus/src/puppet/lib/puppet/settings/ttl_setting.rb:25:in `munge'
from /Users/matthaus/src/puppet/lib/puppet/settings.rb:1310:in `interpolate'
from /Users/matthaus/src/puppet/lib/puppet/settings.rb:1082:in `value_sym'
from /Users/matthaus/src/puppet/lib/puppet/settings.rb:1054:in `value'
from /Users/matthaus/src/puppet/lib/puppet/settings/environment_conf.rb:87:in `environment_timeout'
from /Users/matthaus/src/puppet/lib/puppet/environments.rb:414:in `entry'
from /Users/matthaus/src/puppet/lib/puppet/environments.rb:345:in `get'
Jira (PUP-8409) Puppet config print lists invalid value for environment_timeout when set to unlimited
Title: Message Title Past Haus updated an issue Puppet / PUP-8409 Puppet config print lists invalid value for environment_timeout when set to unlimited Change By: Past Haus Summary: Puppet config print lists invalid default value for environment_timeout when set to unlimited 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-8409) Puppet config print lists invalid value for environment_timeout when set to unlimited
Title: Message Title
Past Haus updated an issue
Puppet / PUP-8409
Puppet config print lists invalid value for environment_timeout when set to unlimited
Change By:
Past Haus
When running {{puppet config print --all}} on the command line with {{environment_timeout}} set to {{unlimited}} in {{puppet.conf}}, the value for {{environment_timeout}} is listed as {{Infinity}}, which is not a valid setting (it can be an integer, 0 or {{unlimited}}). As a user if I saw this I would presume it was a valid setting.When I try using {{Infinity}} as a setting value for {{environment_timeout}}, I get a not so helpful error message and stack trace.{code}puppet apply --environment_timeout=Infinity -e "notify{'foo':}"/Users/matthaus/src/puppet/lib/puppet/settings/ttl_setting.rb:43:in `munge': Invalid 'time to live' format '"Infinity"' for parameter: environment_timeout (Puppet::Settings::ValidationError) from /Users/matthaus/src/puppet/lib/puppet/settings/ttl_setting.rb:25:in `munge' from /Users/matthaus/src/puppet/lib/puppet/settings.rb:1310:in `interpolate' from /Users/matthaus/src/puppet/lib/puppet/settings.rb:1082:in `value_sym' from /Users/matthaus/src/puppet/lib/puppet/settings.rb:1054:in `value' from /Users/matthaus/src/puppet/lib/puppet/settings/environment_conf.rb:87:in `environment_timeout' from /Users/matthaus/src/puppet/lib/puppet/environments.rb:414:in `entry' from /Users/matthaus/src/puppet/lib/puppet/environments.rb:345:in `get' from /Users/matthaus/src/puppet/lib/puppet/util/autoload.rb:131:in `module_directories' from /Users/matthaus/src/puppet/lib/puppet/util/autoload.rb:166:in `search_directories' from /Users/matthaus/src/puppet/lib/puppet/util/autoload.rb:100:in `files_to_load' from /Users/matthaus/src/puppet/lib/puppet/util/autoload.rb:220:in `files_to_load' from /Users/matthaus/src/puppet/lib/puppet/application.rb:212:in `available_application_names' from /Users/matthaus/src/puppet/lib/puppet/util/command_line.rb:90:in `find_subcommand' from /Users/matthaus/src/puppet/lib/puppet/util/command_line.rb:73:in `execute' from /usr/bin/puppet:5:in `'{code} The simple reproducer here is:{code}puppet config print --environment_timeout=unlimited environment_timeoutInfinity{code}
Add Comment
Jira (PUP-8409) Puppet config print lists invalid value for environment_timeout when set to unlimited
Title: Message Title
Past Haus updated an issue
Puppet / PUP-8409
Puppet config print lists invalid value for environment_timeout when set to unlimited
Change By:
Past Haus
When running {{puppet config print --all}} on the command line with {{environment_timeout}} set to {{unlimited}} in {{puppet.conf}} , the default value for {{environment_timeout}} is listed as {{Infinity}}, which is not a valid setting (it can be an integer, 0 or {{unlimited}}). As a user if I saw this I would presume it was a valid setting.When I try using {{Infinity}} as a setting value for {{environment_timeout}}, I get a not so helpful error message and stack trace.{code}puppet apply --environment_timeout=Infinity -e "notify{'foo':}"/Users/matthaus/src/puppet/lib/puppet/settings/ttl_setting.rb:43:in `munge': Invalid 'time to live' format '"Infinity"' for parameter: environment_timeout (Puppet::Settings::ValidationError) from /Users/matthaus/src/puppet/lib/puppet/settings/ttl_setting.rb:25:in `munge' from /Users/matthaus/src/puppet/lib/puppet/settings.rb:1310:in `interpolate' from /Users/matthaus/src/puppet/lib/puppet/settings.rb:1082:in `value_sym' from /Users/matthaus/src/puppet/lib/puppet/settings.rb:1054:in `value' from /Users/matthaus/src/puppet/lib/puppet/settings/environment_conf.rb:87:in `environment_timeout' from /Users/matthaus/src/puppet/lib/puppet/environments.rb:414:in `entry' from /Users/matthaus/src/puppet/lib/puppet/environments.rb:345:in `get' from /Users/matthaus/src/puppet/lib/puppet/util/autoload.rb:131:in `module_directories' from /Users/matthaus/src/puppet/lib/puppet/util/autoload.rb:166:in `search_directories' from /Users/matthaus/src/puppet/lib/puppet/util/autoload.rb:100:in `files_to_load' from /Users/matthaus/src/puppet/lib/puppet/util/autoload.rb:220:in `files_to_load' from /Users/matthaus/src/puppet/lib/puppet/application.rb:212:in `available_application_names' from /Users/matthaus/src/puppet/lib/puppet/util/command_line.rb:90:in `find_subcommand' from /Users/matthaus/src/puppet/lib/puppet/util/command_line.rb:73:in `execute' from /usr/bin/puppet:5:in `'{code}
Add Comment
Jira (PUP-7537) Agent/Master Separation
Title: Message Title Past Haus commented on PUP-7537 Re: Agent/Master Separation Merged in tickets from PUP-4885 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-7537) Agent/Master Separation
Title: Message Title Past Haus updated an issue Puppet / PUP-7537 Agent/Master Separation Change By: Past Haus Fix Version/s: PUP 6.0.0 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-5426) config set ignores --section and can insert duplicate settings if they are in [main]
Title: Message Title
Past Haus updated an issue
Puppet / PUP-5426
config set ignores --section and can insert duplicate settings if they are in [main]
Change By:
Past Haus
Comment:
We're seeing some surprising behavior in PE with this changeset in. I guess the first odd thing is that if a setting doesn't exist anywhere (and a [main] section exists), a new [main] section is added at the bottom of {{puppet.conf}}. This happens with each invocation, so after calling {{puppet config set}} 3 times, there are 4 {{[main]}} sections in {{puppet.conf}}. Starting with a puppet.conf that looks like the following:{code}# 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]certname = r1nc1m63jxi6u3e.delivery.puppetlabs.netserver = r1nc1m63jxi6u3e.delivery.puppetlabs.netuser = pe-puppetgroup = pe-puppetenvironment_timeout = unlimitedmodule_groups = base+pe_only[agent]graph = true[master]node_terminus = classifierstoreconfigs = truestoreconfigs_backend = puppetdbreports = puppetdbcertname = r1nc1m63jxi6u3e.delivery.puppetlabs.netalways_retry_plugins = falsedisable_i18n = true{code}I then run {{puppet config set masterport 8144}}.Now {{puppet.conf}} looks like this:{code}# 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]certname = r1nc1m63jxi6u3e.delivery.puppetlabs.netserver = r1nc1m63jxi6u3e.delivery.puppetlabs.netuser = pe-puppetgroup = pe-puppetenvironment_timeout = unlimitedmodule_groups = base+pe_only[agent]graph = true[master]node_terminus = classifierstoreconfigs = truestoreconfigs_backend = puppetdbreports = puppetdbcertname = r1nc1m63jxi6u3e.delivery.puppetlabs.netalways_retry_plugins = falsedisable_i18n = true[main]masterport = 8144{code}I then run {{puppet config set ca_port 8144}}.Now {{puppet.conf}} looks like:{code}# 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]certname = r1nc1m63jxi6u3e.delivery.puppetlabs.netserver = r1nc1m63jxi6u3e.delivery.puppetlabs.netuser = pe-puppetgroup = pe-puppetenvironment_timeout = unlimitedmodule_groups = base+pe_only[agent]graph = true[master]node_terminus =
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Past Haus commented on PUP-2868 Re: `puppet config print` confusing for users We're seeing some surprising behavior in PE possibly related to this changeset. I guess the first odd thing is that if a setting doesn't exist anywhere (and a [main] section exists), a new [main] section is added at the bottom of puppet.conf. This happens with each invocation, so after calling puppet config set 3 times, there are 4 [main] sections in puppet.conf. Starting with a puppet.conf that looks like the following: # 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] certname = r1nc1m63jxi6u3e.delivery.puppetlabs.net server = r1nc1m63jxi6u3e.delivery.puppetlabs.net user = pe-puppet group = pe-puppet
Jira (PUP-5426) config set ignores --section and can insert duplicate settings if they are in [main]
Title: Message Title Past Haus commented on PUP-5426 Re: config set ignores --section and can insert duplicate settings if they are in [main] We're seeing some surprising behavior in PE with this changeset in. I guess the first odd thing is that if a setting doesn't exist anywhere (and a [main] section exists), a new [main] section is added at the bottom of puppet.conf. This happens with each invocation, so after calling puppet config set 3 times, there are 4 [main] sections in puppet.conf. Starting with a puppet.conf that looks like the following: # 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] certname = r1nc1m63jxi6u3e.delivery.puppetlabs.net server = r1nc1m63jxi6u3e.delivery.puppetlabs.net user = pe-puppet group = pe-puppet
Jira (PUP-8489) inifile no longer manages existing lines in puppet post 5.4.0
Title: Message Title
Past Haus commented on PUP-8489
Re: inifile no longer manages existing lines in puppet post 5.4.0
These are the modules where it seems to work with: {{accounts apache archive chocolatey concat dotnet epel gitlab graphite_powershell hiera iis inifile java_ks logstash memcached ntp pe_metric_curl_cron_jobs powershell reboot registry sensu stdlib vcsrepo windows_env windowsfeature wsus_client acl apt aws chocolatey_server docker elasticsearch firewall grafana haproxy hocon influxdb java jenkins logstashforwarder nginx openldap postgresql puppetserver_gem redis rsyslog staging tomcat windows_autoupdate windows_eventlog windows_firewall yum}}
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-8489) inifile no longer manages existing lines in puppet post 5.4.0
Title: Message Title
Past Haus created an issue
Puppet / PUP-8489
inifile no longer manages existing lines in puppet post 5.4.0
Issue Type:
Bug
Affects Versions:
PUP 5.5.0
Assignee:
Unassigned
Created:
2018/02/23 3:15 PM
Priority:
Normal
Reporter:
Past Haus
Puppet Version: f77e9e00efcf9bd8dac66c6622f35cbe16c8eb7a (5.5.0) Puppet Server Version: (5.2.0) OS Name/Version: Rhel 7 Describe your issue in as much detail as possible… Describe steps to reproduce… Desired Behavior: Even when using a codedir with only the inifile module installed, it should work. In this example, /tmp/configure_inifile.aPkO3n is a tmpdir with just the inifile module installed. An inifile resource such as the following should modify the existing java_args line:
[root@b3wa4ws5mg41efr ~]# puppet apply --codedir /tmp/configure_inifile.aPkO3n -e 'ini_setting \{ "JAVA_ARGS":
ensure => present,
path => "/etc/sysconfig/puppetserver",
section => "",
Jira (PUP-8489) inifile no longer manages existing lines in puppet post 5.4.0
Title: Message Title
Past Haus updated an issue
Puppet / PUP-8489
inifile no longer manages existing lines in puppet post 5.4.0
Change By:
Past Haus
*Puppet Version: f77e9e00efcf9bd8dac66c6622f35cbe16c8eb7a (5.5.0)* *Puppet Server Version: (5.2.0)* *OS Name/Version: Rhel 7*Describe your issue in as much detail as possible… Describe steps to reproduce…*Desired Behavior:*Even when using a codedir with only the inifile module installed, it should work.In this example, {{/tmp/configure_inifile.aPkO3n}} is a tmpdir with just the inifile module installed.An inifile resource such as the following should modify the existing java_args line: {code}[root@b3wa4ws5mg41efr ~]# puppet apply --codedir /tmp/configure_inifile.aPkO3n -e 'ini_setting \ { "JAVA_ARGS": ensure => present, path => "/etc/sysconfig/puppetserver", section => "", setting => "JAVA_ARGS", key_val_separator => "=", value => "\"-Xmx2g -Xms2g -XX:+PrintTenuringDistribution -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:/var/log/puppetlabs/puppetserver/gc.log\"",}'{code}In this case the value of JAVA_ARGS in the file is {{JAVA_ARGS="-Xms2g -Xmx2g -Djruby.logger.class=com.puppetlabs.jruby_utils.jruby.Slf4jLogger"}}*Actual Behavior:*It does not. inifile seems to be able to remove lines and add lines that don't already exist, but modifying existing lines does not work. Unfortunately even with --trace, --verbose and --debug there isn't anything useful coming out of the module. Note: this seems to only be the case when inifile is installed in its own codedir and {{puppet apply --codedir $codedir}} is used. When inifile is present in {{/etc/puppetlabs/code/environments/production/modules/inifile}} with other modules the resource behaves as expected.
Add Comment
Jira (PUP-8489) inifile no longer manages existing lines in puppet post 5.4.0
Title: Message Title
Past Haus commented on PUP-8489
Re: inifile no longer manages existing lines in puppet post 5.4.0
Minimal reproducer:
Make a tmpdir ($tmpdir)
Install inifile module to $tmpdir puppet module install puppetlabs-inifile --codedir $tmpdir
Make a file with SETTING="foo" in it (call it temp-file)
Make the following puppet manifest (call it test-resource.pp):
ini_setting { "JAVA_ARGS":
ensure=> present,
path => "/path/to/temp-file",
section => "",
setting=> "SETTING",
key_val_separator => "=",
value=> "BAR",
}
Run the following puppet code puppet apply --codedir $tmpdir test-resource.pp
Watch nothing happen when it should (then try it with 5.4.0 and watch it work)
Jira (PUP-8489) inifile no longer manages existing lines in puppet post 5.4.0
Title: Message Title Past Haus commented on PUP-8489 Re: inifile no longer manages existing lines in puppet post 5.4.0 A bisect showed this commit as the culprit: https://github.com/puppetlabs/puppet/commit/c98bb6787fa2ec04842a92924dd4eb8e41bddd78 Also I can't explain why having multiple modules in codedir made the problem go away but having only the one module in codedir doesn't work. 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-8489) inifile no longer manages existing lines in puppet post 5.4.0
Title: Message Title
Past Haus updated an issue
Puppet / PUP-8489
inifile no longer manages existing lines in puppet post 5.4.0
Change By:
Past Haus
.comm *Puppet Version: f77e9e00efcf9bd8dac66c6622f35cbe16c8eb7a (5.5.0)* *Puppet Server Version: (5.2.0)* *OS Name/Version: Rhel 7*Describe your issue in as much detail as possible… Describe steps to reproduce…*Desired Behavior:*Even when using a codedir with only the inifile module installed, it should work.In this example, {{/tmp/configure_inifile.aPkO3n}} is a tmpdir with just the inifile module installed.An inifile resource such as the following should modify the existing java_args line: {code}[root@b3wa4ws5mg41efr ~]# puppet apply --codedir /tmp/configure_inifile.aPkO3n -e 'ini_setting { "JAVA_ARGS": ensure => present, path => "/etc/sysconfig/puppetserver", section => "", setting => "JAVA_ARGS", key_val_separator => "=", value => "\"-Xmx2g -Xms2g -XX:+PrintTenuringDistribution -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:/var/log/puppetlabs/puppetserver/gc.log\"",}'{code}In this case the value of JAVA_ARGS in the file is {{JAVA_ARGS="-Xms2g -Xmx2g -Djruby.logger.class=com.puppetlabs.jruby_utils.jruby.Slf4jLogger"}}*Actual Behavior:*It does not. inifile seems to be able to remove lines and add lines that don't already exist, but modifying existing lines does not work. Unfortunately even with --trace, --verbose and --debug there isn't anything useful coming out of the module. Note: this seems to only be the case when inifile is installed in its own codedir and {{puppet apply --codedir $codedir}} is used. When inifile is present in {{/etc/puppetlabs/code/environments/production/modules/inifile}} with other modules the resource behaves as expected.
Add Comment
Jira (PUP-8489) inifile no longer manages existing lines in puppet post 5.4.0
Title: Message Title
Past Haus updated an issue
Puppet / PUP-8489
inifile no longer manages existing lines in puppet post 5.4.0
Change By:
Past Haus
*Puppet Version: f77e9e00efcf9bd8dac66c6622f35cbe16c8eb7a (5.5.0)* *Puppet Server Version: (5.2.0)* *OS Name/Version: Rhel 7*Describe your issue in as much detail as possible… Describe steps to reproduce…*Desired Behavior:*Even when using a codedir with only the inifile module installed, it should work.In this example, {{/tmp/configure_inifile.aPkO3n}} is a tmpdir with just the inifile module installed.An inifile resource such as the following should modify the existing java_args line: {code}[root@b3wa4ws5mg41efr ~]# puppet apply --codedir /tmp/configure_inifile.aPkO3n -e 'ini_setting \{ "JAVA_ARGS": ensure => present, path => "/etc/sysconfig/puppetserver", section => "", setting => "JAVA_ARGS", key_val_separator => "=", value => "\"-Xmx2g -Xms2g -XX:+PrintTenuringDistribution -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:/var/log/puppetlabs/puppetserver/gc.log\"",}'{code}In this case the value of JAVA_ARGS in the file is {{JAVA_ARGS="-Xms2g -Xmx2g -Djruby.logger.class=com.puppetlabs.jruby_utils.jruby.Slf4jLogger"}}*Actual Behavior:*It does not. inifile seems to be able to remove lines and add lines that don't already exist, but modifying existing lines does not work. Unfortunately even with --trace, --verbose and --debug there isn't anything useful coming out of the module. Note: this seems to only be the case when inifile is installed in its own codedir and {{puppet apply --codedir $codedir}} is used. When inifile is present in {{/etc/puppetlabs/code/environments/production/modules/inifile}} with other modules the resource behaves as expected.
Add Comment
Jira (PUP-8515) Automate and record runs of puppet benchmarks
Title: Message Title Past Haus created an issue Puppet / PUP-8515 Automate and record runs of puppet benchmarks Issue Type: Task Assignee: Unassigned Created: 2018/03/06 4:17 PM Priority: Normal Reporter: Past Haus Puppet has a series of benchmarks designed to time small portions of the puppet codebase. They live here: https://github.com/puppetlabs/puppet/tree/master/benchmarks If we were to begin running these regularly against puppet and recording the results, we could use the results of those runs to spot regressions before they ship and before they impact other components further up the stack such as puppetserver where it can be more costly to diagnose. /cc Patrick Carlisle Craig Gomes Josh Cooper Add Comment
Jira (PUP-8493) The differences between the vendored semantic_puppet and the original make it impossible to swap in the original
Title: Message Title Past Haus created an issue Puppet / PUP-8493 The differences between the vendored semantic_puppet and the original make it impossible to swap in the original Issue Type: Bug Assignee: Unassigned Created: 2018/02/26 3:32 PM Priority: Normal Reporter: Past Haus According to https://github.com/puppetlabs/puppet/blob/5.4.x/lib/puppet/vendor.rb#L20-L24 any libraries that we vendor should not be modified from the original source. The intention is that a distro can swap in a system level package supplying the library and have it just work. That is not possible with semantic_puppet. Here (https://github.com/puppetlabs/puppet/blob/5.4.x/lib/puppet/vendor/semantic_puppet/lib/semantic_puppet/version_range.rb#L65), you can see self.parse takes two arguments, one of which has a default. It has been that way since https://github.com/puppetlabs/puppet/commit/a723e23bd238ba5bf69e1d3e959b6aa93ec18211 which was released in 4.10.5. The original gem has a single arity version of self.parse (https://github.com/puppetlabs/semantic_puppet/blame/master/lib/semantic_puppet/version_range.rb#L64) in its latest release. Those methods are marked public in both cases. If a distro removed the vendored copy, as we suggest should be possible in vendor.rb, any calls that pass two arguments to self.parse will fail with an arity mismatch as the upstream version only takes one argument. If the behavior that exists in the vendored copy from puppet is desirable, it should be added to the source gem. Really we shouldn't be vendoring it at all, but if there are required changes to it they should be released in the source gem first before coming across to puppet's copy.
