Jira (PUP-7516) ImportError: pycurl: libcurl link-time version (7.50.3) is older than compile-time version (7.51.0)
Title: Message Title Ethan Brown commented on PUP-7516 Re: ImportError: pycurl: libcurl link-time version (7.50.3) is older than compile-time version (7.51.0) First PR merged to stable in https://github.com/puppetlabs/puppet/commit/b691328407814929bb07782e6ebf69327549fe6a Second PR merged to stable (as PUP-7156 even though it should have been PUP-7516) in https://github.com/puppetlabs/puppet/commit/dc4e73d76db1751f5185333293d50b173a119c16 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-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-2280 If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure Change By: Geoff Nichols Team: Agent Puppet Developer Experience 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-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-2280 If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure Change By: Geoff Nichols Sprint: Puppet 5 Race to the Finish! PDE 2017-05-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-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3042 If a catalog has a dependency cycle, it does not count as failed Change By: Geoff Nichols Sprint: Agent N+1 PDE 2017-05-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-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3042 If a catalog has a dependency cycle, it does not count as failed Change By: Geoff Nichols Team: Agent Puppet Developer Experience 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-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Moses Mendoza commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters Andrey Galkin no worries, thank you!! With that info I now understand and can trace through why you are also experiencing this behavior! As mentioned above, that doesn't mean its not a bug and I hope to have this addressed in short order. 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-7506) Puppet-device looks for the transport lib in the proxy's environment, not the device's
Title: Message Title Hunter (Hunner) Haugen updated an issue Puppet / PUP-7506 Puppet-device looks for the transport lib in the proxy's environment, not the device's Change By: Hunter (Hunner) Haugen Summary: Puppet-device can't find looks for the transport lib in the device proxy 's environment , not the device's 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-3511) KahaDB GC doesn't happen, sometimes
Title: Message Title Russell Mull commented on PDB-3511 Re: KahaDB GC doesn't happen, sometimes Erik Dasher ^ for context, if you need it for anything 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-3511) KahaDB GC doesn't happen, sometimes
Title: Message Title Russell Mull commented on PDB-3511 Re: KahaDB GC doesn't happen, sometimes Erik Hansen crap wrong erik, sorry 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-3511) KahaDB GC doesn't happen, sometimes
Title: Message Title Russell Mull commented on PDB-3511 Re: KahaDB GC doesn't happen, sometimes There are a bunch of things broken here. 1) In PE-19161 and PE-20531, we can see a report was submitted with the value 'null' in a resource event status field. This is an instance of PUP-1542. The data fails schema validation inside of PuppetDB, which throws a clojure.lang.ExceptionInfo. 2) PuppetDB's wrap-with-exception-handling amq "middleware" has a catch-all for any exceptions thrown during message processing. This is broken for ExceptionInfo exceptions, due our misuse of slingshot (which as a very misleading api that's easy to misuse in this way). If we caught the exception, we'd use our internal retry mechanism. Instead, it bubbles up to AMQ. 3) ActiveMQ then starts retrying the message using its own resubmission loop. This adds an "JMSXDeliveryCount" header to the AMQ message. In the version of PuppetDB used in the linked issues, this causes a secondary schema validation error on the retried messages, concealing the actual problem. (fixed in PDB-3177 ) 4) Once AMQ runs through its retry loop and nothing succeeds, it puts the the message in its own internal DLQ. This is different from PuppetDBs DLO, which is implemented as a separate queue. In this case, it simply leaves the message in place inside a KahaDB log file and adds the message to the "ActiveMQ.DLQ" topic. This effectively retains a reference to that log file, preventing it from being GCed. If the system is under heavy load and (I think) processing particularly large commands, the ACK messages which indicate that a message was processed will often be written into a later log file from the message itself. KahaDB's GC mechanism analyses dependencies in a very course-grained way, such that the file with the ACK won't be GC'ed until the file with the original message is. Under load, this can lead to a degenerate case wherein each log file is retained by its predecessor, and the beginning of the chain can never be cleaned up because it contains a DLQ message. – solutions – 1) We're going to try to work with the customers at hand to see if they can help us get a repro to finally fix PUP-1542. In the meantime, we'll add a workaround to PuppetDB to handle this particular kind of bad data more gracefully. (maybe in the terminus) 2) By fixing the exception handling, we should prevent the message from reaching ActiveMQ's internal DLQ at all, so we don't get into this situation. 3) Already fixed in the latest LTS 4) ActiveMQ as a fix for this, in https://issues.apache.org/jira/browse/AMQ-6203. It works ok, as long as these messages are infrequent. We can get the fix by upgrading to ActiveMQ 5.13.3 and changing our KahaDB configuration.
Jira (PUP-7523) Can't gem install puppet with some versions of bundler and ruby 1.9.3
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7523 Can't gem install puppet with some versions of bundler and ruby 1.9.3 Change By: Josh Cooper Story Points: 1 Sprint: Agent 2017-05-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-7523) Can't gem install puppet with some versions of bundler and ruby 1.9.3
Title: Message Title Josh Cooper created an issue Puppet / PUP-7523 Can't gem install puppet with some versions of bundler and ruby 1.9.3 Issue Type: Bug Assignee: Unassigned Created: 2017/05/11 4:37 PM Priority: Normal Reporter: Josh Cooper Running puppet --version on ruby 1.9.3 and ubuntu 14.04 fails due to https://github.com/bundler/bundler/issues/3187 root@cb37bnfmc142c5l:~# puppet --version /usr/lib/ruby/1.9.1/rubygems/version.rb:191:in `strip!': can't modify frozen String (RuntimeError) from /usr/lib/ruby/1.9.1/rubygems/version.rb:191:in `initialize' from /var/lib/gems/1.9.1/gems/puppet-4.10.1/lib/puppet.rb:3:in `new'
Jira (PUP-7522) Add the ability to view trusted fact values from an agent
Title: Message Title Nate McCurdy updated an issue Puppet / PUP-7522 Add the ability to view trusted fact values from an agent Change By: Nate McCurdy Team: 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-7522) Add the ability to view trusted fact values from an agent
Title: Message Title
Nate McCurdy updated an issue
Puppet / PUP-7522
Add the ability to view trusted fact values from an agent
Change By:
Nate McCurdy
h2. The problemThere is no current way—at least that I could find—for an agent to be able to view its trusted fact values using a {{puppet}} command.Someone that is troubleshooting a Puppet-built node would need to do one of:* Have root access on the Puppet master to run {{puppet cert print }}* Have API access to do a PuppetDB query* Run {{openssl x509 -text -noout -in $(puppet config print hostcert)}} to view certificate extensions but not have the OID mapping for trusted facts.The values of a trusted fact are not considered secret and are only trusted in that they've been signed by the CA. Also, they are plainly visible in the x509 certificate. An admin/Puppet user shouldn't need to know the intricacies of the {{openssl}} command to view that data. It seems silly that there is not a way to view this data from a {{puppet}} command.h2. The improvementThere should be some command, {{puppet }}, that shows the values of local trusted facts and their OID mappings if using one of the named OID values .
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
Jira (PUP-7522) Add the ability to view trusted fact values from an agent
Title: Message Title
Nate McCurdy updated an issue
Puppet / PUP-7522
Add the ability to view trusted fact values from an agent
Change By:
Nate McCurdy
h2. The problem There is no current way —at least that I could find—for an agent to be able to view its trusted fact values using a {{puppet}} command.Someone that is troubleshooting a Puppet-built node would need to do one of:* Have root access on the Puppet master to run {{puppet cert print }}* Have API access to do a PuppetDB query* Run {{openssl x509 -text -noout -in $(puppet config print hostcert)}} to view certificate extensions but not have the OID mapping for trusted facts.The values of a trusted fact are not considered secret and are only trusted in that they've been signed by the CA. Also, they are plainly visible in the x509 certificate. An admin/Puppet user shouldn't need to know the intricacies of the {{openssl}} command to view that data. It seems silly that there is not a way to view this data from a {{puppet}} command.h2. The improvementThere should be some command, {{puppet }}, that shows the values of local trusted facts.
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-7522) Add the ability to view trusted fact values from an agent
Title: Message Title Nate McCurdy created an issue Puppet / PUP-7522 Add the ability to view trusted fact values from an agent Issue Type: Improvement Assignee: Unassigned Created: 2017/05/11 4:12 PM Priority: Normal Reporter: Nate McCurdy There is no current way Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Andrey Galkin commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters Hi Moses Mendoza. At the moment, I see the second master in lab environment is missing routes.yaml. So, only the primary master has one. I believe the situation was the same in the original testing as puppetdb-termini apparently does not install one automatically. Sorry for the misleading previous comment. 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-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Moses Mendoza commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters Hi Andrey Galkin - just got to pick this up again (had to delay for a bit with some other work). One question for you - can you confirm you have `/etc/puppetlabs/puppet/routes.yaml` deployed on both of your masters from the example? 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-7519) Enable rubocop security cop scan on ruby projects
Title: Message Title Jayant Sane assigned an issue to Jayant Sane Puppet / PUP-7519 Enable rubocop security cop scan on ruby projects Change By: Jayant Sane Assignee: Jayant Sane 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-7519) Enable rubocop security cop scan on ruby projects
Title: Message Title Jayant Sane commented on PUP-7519 Re: Enable rubocop security cop scan on ruby projects Submitted PR for puppet: https://github.com/puppetlabs/puppet/pull/5855 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-7521) Puppet Acceptance Test Failure in Imaging Acceptance Tests
Title: Message Title Jeremy Barlow assigned an issue to Adrien Thebo Puppet / PUP-7521 Puppet Acceptance Test Failure in Imaging Acceptance Tests Change By: Jeremy Barlow Assignee: Jeremy Barlow Adrien Thebo 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-7521) Puppet Acceptance Test Failure in Imaging Acceptance Tests
Title: Message Title John O'Connor created an issue Puppet / PUP-7521 Puppet Acceptance Test Failure in Imaging Acceptance Tests Issue Type: Bug Assignee: Jeremy Barlow Components: Test Infrastructure Created: 2017/05/11 10:02 AM Priority: Normal Reporter: John O'Connor The new Packer/Imaging acceptance tests are consistently failing with the following test failures: tests/reports/corrective_change_new_resource.rb tests/reports/corrective_change_outside_puppet.rb tests/reports/corrective_change_via_puppet.rb tests/resource/file/ticket_6448_file_with_utf8_source.rb These tests are a copy of the existing Puppet Acceptance Tests from the Puppet Agent Suite remodelled to run on the Jenkins Imaging Server as part the vmpooler image creation pipeline. An example of a failing test is available at: https://jenkins-imaging.delivery.puppetlabs.net/view/Windows/job/imaging_windows-2012r2-wmf5_x86_64_vmware_vsphere.cygwin_acceptance_packer/5/consoleF
Jira (PUP-7515) data-in-modules: lookup() and automatic class parameter lookup result in different values
Title: Message Title Thomas Hallgren commented on PUP-7515 Re: data-in-modules: lookup() and automatic class parameter lookup result in different values Yes, you can specify merge behavior for specific keys (or keys that matches a specific pattern) using lookup_options in the hiera data files. 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-7149) Puppet should include job id in reports and catalogs
Title: Message Title Alex Dreyer commented on PUP-7149 Re: Puppet should include job id in reports and catalogs it's stored with the catalog in puppetdb which is what we really want here too. 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-7149) Puppet should include job id in reports and catalogs
Title: Message Title Michael Smith commented on PUP-7149 Re: Puppet should include job id in reports and catalogs I'm not sure the transaction_uuid is included in the catalog. Not actually sure why we send it as part of the compile request. 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-3512) Facts wire format docs for package_inventory are incomplete
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3512 Facts wire format docs for package_inventory are incomplete Issue Type: Bug Assignee: Unassigned Created: 2017/05/11 9:39 AM Priority: Normal Reporter: Russell Mull "The "package_inventory" keys is optional, if present, must be an array of ." Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7520) Puppet profiling timers do not use a monotonic clock
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-7520
Puppet profiling timers do not use a monotonic clock
Change By:
Charlie Sharpsteen
Puppet has support for timing and profiling execution through the {{Puppet::Util::Profiler::WallClock}} class, used for profiling Puppet Server operations, and the {{Puppet::Util.thinmark}} method, used for measuring things like resource application. Historically these methods have measured time by calling {{Time.now}}. However, this method returns a value from the OS REALTIME clock, which can be affected by events like NTP updates. Since the puppet agent often initiates a NTP update, these jumps can create confusing profile resullts results .In 2.1.0, Ruby added methods to access a monotonic clock which isn't affected by things like NTP updates. We should prefer this clock for profiling timers when it is available:https://ruby-doc.org/core-2.1.0/Process.html
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 (FACT-1624) Consolidate `is_fixednum` and `is_bignum` into `is_integer` for Ruby 2.4
Title: Message Title Eric Thompson updated an issue Facter / FACT-1624 Consolidate `is_fixednum` and `is_bignum` into `is_integer` for Ruby 2.4 Change By: Eric Thompson 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-7520) Puppet profiling timers do not use a monotonic clock
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-7520
Puppet profiling timers do not use a monotonic clock
Change By:
Charlie Sharpsteen
Puppet has support for timing and profiling execution through the {{Puppet::Util::Profiler::WallClock}} class, used for profiling Puppet Server operations, and the {{Puppet::Util.thinmark}} method, used for measuring things like resource application. Historically these methods have measured time by calling {{Time.now}}. However, this method returns a value from the OS REALTIME clock, which can be affected by thinks events like NTP updates. Since the puppet agent often initiates a NTP update, these jumps can create confusing profile resullts.In 2.1.0, Ruby added methods to access a monotonic clock which isn't affected by things like NTP updates. We should prefer this clock for profiling timers when it is available:https://ruby-doc.org/core-2.1.0/Process.html
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-7520) Puppet profiling timers do not use a monotonic clock
Title: Message Title Charlie Sharpsteen created an issue Puppet / PUP-7520 Puppet profiling timers do not use a monotonic clock Issue Type: Bug Affects Versions: PUP 4.10.1 Assignee: Unassigned Created: 2017/05/11 9:17 AM Priority: Normal Reporter: Charlie Sharpsteen Puppet has support for timing and profiling execution through the Puppet::Util::Profiler::WallClock class, used for profiling Puppet Server operations, and the Puppet::Util.thinmark method, used for measuring things like resource application. Historically these methods have measured time by calling Time.now. However, this method returns a value from the OS REALTIME clock, which can be affected by thinks like NTP updates. Since the puppet agent often initiates a NTP update, these jumps can create confusing profile resullts. In 2.1.0, Ruby added methods to access a monotonic clock which isn't affected by things like NTP updates. We should prefer this clock for profiling timers when it is available: https://ruby-doc.org/core-2.1.0/Process.html
Jira (PDB-3511) KahaDB GC doesn't happen, sometimes
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3511 KahaDB GC doesn't happen, sometimes Change By: Russell Mull Story Points: 3 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-3511) KahaDB GC doesn't happen, sometimes
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3511 KahaDB GC doesn't happen, sometimes Change By: Russell Mull Sprint: PuppetDB 2017-05-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 (PDB-3511) KahaDB GC doesn't happen, sometimes
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3511 KahaDB GC doesn't happen, sometimes Change By: Russell Mull Labels: escalation 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-677) user type accepts numeric usernames, but ssh_authorized_key does not
Title: Message Title Bowie Bartels commented on PUP-677 Re: user type accepts numeric usernames, but ssh_authorized_key does not Hi everyone, I also just ran into the same problem. Everything works fine (creating user and home folder based on numeric value). However, when using ssh_authorized_key it complains the user does not exist. Issue seems to be open for a while. Any chance its status will change any time soon? Thanks for the response! 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-7187) PUP-6538 deprecation documentation should provide examples for legacy hiera function
Title: Message Title Henrik Lindberg commented on PUP-7187 Re: PUP-6538 deprecation documentation should provide examples for legacy hiera function Curtis Ruck You can add those yourself if you want to - simple to write them in puppet even. The reason we did not simply relay the old hiera_xxx functions to lookup is that everything is not supported exactly the same way, and overlay hash is not supported with the lookup function. That raised more problems than what we thought we were going to solve by doing that, and probably confusing already complex things. If you for instance are not using overlays, then it should be easy to add the functions you suggested yourself. Over time you may benefit from using APL more and using less explicit calls to lookup - that seems to be the trend. The reason for APL to not be used in the past was typically because of the need to deep merge and similar things - now you can get all of that in APL. 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-7515) data-in-modules: lookup() and automatic class parameter lookup result in different values
Title: Message Title Robert Heinzmann commented on PUP-7515 Re: data-in-modules: lookup() and automatic class parameter lookup result in different values Can the behaviour 2. be changed with lookup_options in the yaml files ? 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-6692) Improve access to "master" settings
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-6692 Improve access to "master" settings Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-6692) Improve access to "master" settings
Title: Message Title Thomas Hallgren commented on PUP-6692 Re: Improve access to "master" settings Merged to master at 1d0607e. 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-7187) PUP-6538 deprecation documentation should provide examples for legacy hiera function
Title: Message Title Curtis Ruck commented on PUP-7187 Re: PUP-6538 deprecation documentation should provide examples for legacy hiera function Maybe an enhancement could be added to add lookup_hash, lookup_array, and lookup_include to provide backwards compatible shims that don't log the depreciation statements? 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-7187) PUP-6538 deprecation documentation should provide examples for legacy hiera function
Title: Message Title Curtis Ruck commented on PUP-7187 Re: PUP-6538 deprecation documentation should provide examples for legacy hiera function The link is here for ticket completion sake... https://docs.puppet.com/puppet/4.10/hiera_migrate_functions.html I'm fine with closing it. Though I despise how the replacements require significantly more characters and introduce errors in translation, especially for my 641 usages of the legacy functions. 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-7514) reduce does not work with break()
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7514 reduce does not work with break() Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-7514) reduce does not work with break()
Title: Message Title Thomas Hallgren commented on PUP-7514 Re: reduce does not work with break() Merged to master at 2580b1e. 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-7187) PUP-6538 deprecation documentation should provide examples for legacy hiera function
Title: Message Title Henrik Lindberg commented on PUP-7187 Re: PUP-6538 deprecation documentation should provide examples for legacy hiera function We do have docs now, can this be closed? 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-6692) Improve access to "master" settings
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-6692 Improve access to "master" settings Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren 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-6692) Improve access to "master" settings
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6692
Improve access to "master" settings
Change By:
Henrik Lindberg
Release Notes Summary:
All individual variables in the {{$settings}} namespace are now available as a Hash of => in the variable {{$settings::all_local}}. This makes it easy to lookup a setting that may be missing when {{\--strict_variables}} is in effect.
Release Notes:
New Feature
Fix Version/s:
PUP 5.0.0
Component/s:
Language
Component/s:
DOCS
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6692) Improve access to "master" settings
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-6692 Improve access to "master" settings Change By: Henrik Lindberg Assignee: 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-6692) Improve access to "master" settings
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6692 Improve access to "master" settings Change By: Henrik Lindberg Sprint: PDE Triage 2017-05-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-6692) Improve access to "master" settings
Title: Message Title Henrik Lindberg commented on PUP-6692 Re: Improve access to "master" settings In PUP-5635 the handling of qualified variables was changed, it is now very easy to add additional values in the $settings namespace without having to also create scopes in that/those namespaces. The solution to use $settings::all_local as a hash of all settings is thus possible with minimal effort. It would also be easy to later (when available from a node) also set those. 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-7514) reduce does not work with break()
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-7514 reduce does not work with break() Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren 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-7515) data-in-modules: lookup() and automatic class parameter lookup result in different values
Title: Message Title
Thomas Hallgren commented on PUP-7515
Re: data-in-modules: lookup() and automatic class parameter lookup result in different values
There are a couple of things to consider:
hiera_xxx are not expected to work unless you specifically enable Hiera 5 in the environment layer. Unless that's done, the described behavior is expected. These functions are deprecated and the default is to limit all such lookups to global layer.
The deep merge strategy is used for the explicit lookup call. In contrast, the Automatic Parameter Lookup (henceforth referred to as APL) will use the default strategy which is to return the entry that is first found. This explains the "strange" class parameter when using ENC or FACT. Both returns '{"plugin_role1"=>{"ensure"=>"present"}}' which is the first entry found. This is the expected behavior.
The lookup command and the APL for the $plugins parameter does not use the same scope when evaluating. When the lookup function evaluates, all parameters have a value. The APL for $plugins uses a special parameter scope where parameters that are positioned before the parameter to evaluate are visible. That means that $role should have a value but from the looks of it, Hiera doesn't see that value. This is not the expected behavior and needs to be investigated further.
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
Jira (PUP-7508) Failing mapped_paths don't get explained by lookup --explain
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-7508
Failing mapped_paths don't get explained by lookup --explain
Change By:
Henrik Lindberg
Story Points:
1
Release Notes Summary:
The --explain output for {{mapped_paths}} have been improved when there are errors in the input. Earlier, the explain output simply did not output anything if something was wrong.
Sprint:
PDE 2017-05-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-7508) Failing mapped_paths don't get explained by lookup --explain
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7508 Failing mapped_paths don't get explained by lookup --explain Change By: Henrik Lindberg Labels: Hiera Language 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-7508) Failing mapped_paths don't get explained by lookup --explain
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7508 Failing mapped_paths don't get explained by lookup --explain Change By: Henrik Lindberg Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 4.10.z 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-7508) Failing mapped_paths don't get explained by lookup --explain
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7508 Failing mapped_paths don't get explained by lookup --explain Change By: Henrik Lindberg Issue Type: Bug Improvement 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-7515) data-in-modules: lookup() and automatic class parameter lookup result in different values
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7515 data-in-modules: lookup() and automatic class parameter lookup result in different values Thanks for the excellent report Robert Heinzmann ! Ping Thomas Hallgren Change By: Henrik Lindberg Team: Puppet Developer Experience Sprint: PDE Triage 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.
