Jira (PUP-10679) Unable to install Ruby gem on Windows with ensure and version range
Title: Message Title
Josh Cooper commented on PUP-10679
Re: Unable to install Ruby gem on Windows with ensure and version range
It’s probably the greater than character. It’s possible to escape special chars on windows using caret {}. Maybe try '>= 2.2.0^’. The gem provider should handle that but maybe that’ll work for now?
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.373310.160130644.67931.1604035140027%40Atlassian.JIRA.
Jira (PUP-2173) puppet config set certname accepts upper-case names
Title: Message Title Josh Cooper commented on PUP-2173 Re: puppet config set certname accepts upper-case names Ran into PUP-10731. Depending on how difficult that is to resolve, I may skip validating that setting as part of this ticket. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.31150.1396893989000.67830.1604014980286%40Atlassian.JIRA.
Jira (PUP-10601) Only create pcore resource type loaders for compilation
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10601 Only create pcore resource type loaders for compilation Change By: Josh Cooper Fix Version/s: PUP 7.0.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.367414.1595884476000.67802.1604014020105%40Atlassian.JIRA.
Jira (PUP-10601) Only create pcore resource type loaders for compilation
Title: Message Title Josh Cooper commented on PUP-10601 Re: Only create pcore resource type loaders for compilation Changing the default behavior would need to be coordinated with puppetserver as well as external tools that interact with the compiler like catalog-diff and puppet-strings. So I'm going to close this as won't fix. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.367414.1595884476000.67801.1604014020060%40Atlassian.JIRA.
Jira (PUP-10730) Old report processors don't work with the new puppetserver http client
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10730 Old report processors don't work with the new puppetserver http client Change By: Josh Cooper Labels: platform_7 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.376350.1603910048000.67803.1604014020147%40Atlassian.JIRA.
Jira (PUP-10731) Setting facterng twice raises an exception
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10731
Setting facterng twice raises an exception
Change By:
Josh Cooper
Using 6.19.0, setting {{facterng}} to true twice programmatically results in a {{NameError}}:{noformat}[root@baneful-extreme ~]# /opt/puppetlabs/puppet/bin/irbirb(main):001:0> require 'puppet'=> trueirb(main):002:0> Puppet.initialize_settings=> {}irb(main):003:0> pp $LOADED_FEATURES.sort.grep /facter(-ng)?\.rb$/["/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/gems/did_you_mean-1.2.0/lib/facter.rb", "/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.rb"]=> ["/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/gems/did_you_mean-1.2.0/lib/facter.rb", "/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.rb"]irb(main):004:0> Puppet[:facterng] = true=> trueirb(main):005:0> pp $LOADED_FEATURES.sort.grep /facter(-ng)?\.rb$/["/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/gems/did_you_mean-1.2.0/lib/facter.rb", "/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/gems/facter-ng-4.0.43/agent/lib/facter-ng.rb", "/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/gems/facter-ng-4.0.43/lib/facter.rb", "/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/gems/facter-ng-4.0.43/lib/facter/custom_facts/core/legacy_facter.rb", "/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.rb"]=> ["/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/gems/did_you_mean-1.2.0/lib/facter.rb", "/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/gems/facter-ng-4.0.43/agent/lib/facter-ng.rb", "/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/gems/facter-ng-4.0.43/lib/facter.rb", "/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/gems/facter-ng-4.0.43/lib/facter/custom_facts/core/legacy_facter.rb", "/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.rb"]irb(main):006:0> Puppet[:facterng] = trueTraceback (most recent call last):7: from /opt/puppetlabs/puppet/bin/irb:11:in `'6: from (irb):65: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:108:in `[]='4: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:178:in `[]='3: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:1494:in `set'2: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/defaults.rb:87:in `block in initialize_default_settings!'1: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/logging.rb:258:in `setup_facter_logging!'NameError (uninitialized constant Puppet::Util::Logging::Facter)Did you mean? Facts{noformat}The first time {{Puppet[:facterng] = true}} is called, the hook for the setting calls {{require 'facter-ng'}} and ruby adds it to the special {{$LOADED_FEATURES}} hash. The next time {{Puppet[:facterng] = true}} is called, we remove the {{Facter}} constant and then we try to {{require 'facter-ng'}} again. But ruby "remembers" that it already required it once, and doesn't require it again. As a result, {{require 'facter-ng'}} returns false, and the {{Facter}} constant is not defined when we call into:{code:ruby} def self.setup_facter_logging!# Only recent versions of Facter
Jira (PUP-10731) Setting facterng twice raises an exception
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10731 Setting facterng twice raises an exception Change By: Josh Cooper Issue Type: Bug CI Blocker Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.376536.1604009521000.67628.1604009820028%40Atlassian.JIRA.
Jira (PUP-10731) Setting facterng twice raises an exception
Title: Message Title Josh Cooper commented on PUP-10731 Re: Setting facterng twice raises an exception puppet-agent#master CI is blocked due to this and PUP-2178. The trick is to run puppet config set facterng true once, and then try to run it again or set the value to false: * disable facterng feature flag back-logarithm.delivery.puppetlabs.net (back-logarithm.delivery.puppetlabs.net) 15:40:36$ puppet config set facterng false Error: uninitialized constant Puppet::Util::Logging::Facter Did you mean? Puppet::Face Facts Error: Try 'puppet help config set' for usage Add Comment
Jira (PUP-10731) Setting facterng twice raises an exception
Title: Message Title
Josh Cooper created an issue
Puppet / PUP-10731
Setting facterng twice raises an exception
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/10/29 3:12 PM
Priority:
Normal
Reporter:
Josh Cooper
Using 6.19.0, setting facterng to true twice programmatically results in a NameError:
[root@baneful-extreme ~]# /opt/puppetlabs/puppet/bin/irb
irb(main):001:0> require 'puppet'
=> true
irb(main):002:0> Puppet.initialize_settings
=> {}
irb(main):003:0> pp $LOADED_FEATURES.sort.grep /facter(-ng)?\.rb$/
Jira (PUP-10731) Setting facterng twice raises an exception
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10731 Setting facterng twice raises an exception Change By: Josh Cooper Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.376536.1604009521000.67625.1604009580218%40Atlassian.JIRA.
Jira (PDB-4948) Improve report/resource_event GC coordination with in flight queries
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-4948 Improve report/resource_event GC coordination with in flight queries Issue Type: Improvement Assignee: Unassigned Created: 2020/10/29 2:30 PM Priority: Normal Reporter: Zachary Kent In a hotfix targeted at 2019.8 we added an interrupter thread to help coordinate report/resource_event GC with sync queries in this PR. While we hope that this change allows PDB sync to avoid full deadlocks with GC as seen in PE-30087 it's still possible that GC could conflict with other long running queries outside of sync. It's also possible that GC could get unlucky and need multiple tries to delete a partition which could cause multiple errors in the logs while sync gets cancelled repeatedly. A more complete solution would be to allow GC to "bulldoze" other in flight queries which are blocking the AccessExclusiveLock it needs to drop an old partition. This could be accomplished by using pg_cancel_backend() in coordination with querying pg_locks to see which queries are blocking the lock GC needs. Doing something along these lines would protect against all queries and not just those being performed by the local PDB during sync. If we do this we'll want to audit the error handling /retry behavior of all queries we can think of in PDB and PE because this could cause GC to kill any inflight query. Add Comment
Jira (PDB-4892) Summary query for catalog_inputs unecessarily slow
Title: Message Title Zachary Kent assigned an issue to Unassigned PuppetDB / PDB-4892 Summary query for catalog_inputs unecessarily slow Change By: Zachary Kent Assignee: Zachary Kent Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371815.1600126491000.67569.1604005140035%40Atlassian.JIRA.
Jira (PDB-4947) Fix failing travis tests on 5.2.x with jdk 1.8.0_272
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4947 Fix failing travis tests on 5.2.x with jdk 1.8.0_272 Issue Type: Bug Assignee: Austin Blatt Created: 2020/10/29 11:34 AM Fix Versions: PDB n/a Priority: Normal Reporter: Austin Blatt After a bump of the java version we are seeing a failure in the integration tests, only on travis. We haven't been able to reproduce it locally, but it appears to be the same error that RE and Installer encountered when trying to update pe-java. The last successful 5.2.x run was https://travis-ci.com/github/puppetlabs/puppetdb/jobs/404168402 and ran with +java -version openjdk version "1.8.0_265" OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_265-b01) OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.265-b01, mixed mode)
Jira (PDB-4871) Investigate queries using two Hikari connections per request
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-4871 Investigate queries using two Hikari connections per request Change By: Zachary Kent Assignee: Zachary Kent Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.370205.1598390523000.67175.1603989780034%40Atlassian.JIRA.
Jira (PUP-10730) Old report processors don't work with the new puppetserver http client
Title: Message Title Josh Cooper commented on PUP-10730 Re: Old report processors don't work with the new puppetserver http client Merged to main in https://github.com/puppetlabs/puppet/commit/89d9333618e2d155300494924beea56cbac908f1 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.376350.1603910048000.67115.1603987320036%40Atlassian.JIRA.
Jira (FACT-2848) Improve performance of cache manager
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2848 Improve performance of cache manager Change By: Bogdan Irimie Assignee: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.376315.160389490.67045.1603980660027%40Atlassian.JIRA.
Jira (PUP-5402) systemd: Puppet agent starts before network-online.target is reached
Title: Message Title Vladimir Safronov commented on PUP-5402 Re: systemd: Puppet agent starts before network-online.target is reached Confirmed on CentOS 8.2.2004 with puppet 6.19.1 cat /etc/system-release CentOS Linux release 8.2.2004 (Core) puppet --version 6.19.1 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.102362.1445418471000.67037.1603978500028%40Atlassian.JIRA.
Jira (FACT-2847) Facter 4 breaks rspec on fact test
Title: Message Title
Sebastian Miclea commented on FACT-2847
Re: Facter 4 breaks rspec on fact test
Hi Martin Alfke, I had a look over your fact and noticed that the stub for Facter.fact('os') is defined in the after block and it's not getting stubbed before running the test. Moving it to the before block should fix it. The error occurs because Facter4 uses Facter::Core::Execution to detect the os in order to be able to confine the custom fact. It passed on previous versions of Facter because 2.x used RbConfig to detect the current os and Facter3 used CMake. Let me know if this works out.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.376201.1603820546000.67027.160397792%40Atlassian.JIRA.
Jira (FACT-2819) (experimental) Revert parallel resolution of facts
Title: Message Title Bogdan Irimie commented on FACT-2819 Re: (experimental) Revert parallel resolution of facts When running in sequential mode, Facter 4 creates a total of 142 threads. The threads are crated because execution reads stderr and stdout on separate threads and the timer used for timeouts creates a thread as well. When running Facter 4 in parallel mode, a total of 248 threads are created. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.373483.1601475251000.66969.1603966140040%40Atlassian.JIRA.
