Jira (FACT-2937) 'puppet facts show' logs error when stdlib is installed
Title: Message Title Maggie Dreyer commented on FACT-2937 Re: 'puppet facts show' logs error when stdlib is installed I'm also seeing this when I start the developer repl for puppetserver, even after taking up the commit that resolved this ticket. I don't see it when I start the server from a package build. It seems to happen as part of creating the settings catalog: 2021-03-23 14:37:53,963 ERROR [clojure-agent-send-pool-0] [puppetserver] Facter error while resolving custom facts in /Users/aileen/.puppetlabs/opt/puppet/cache/lib/facter/service_provider.rb Could not autoload puppet/provider/service/upstart: Could not autoload puppet/provider/service/debian: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass backtrace: /Users/aileen/code/server/puppetserver/ruby/puppet/lib/puppet/provider/service/init.rb:24:in `block in ' org/jruby/RubyModule.java:3249:in `module_eval' /Users/aileen/code/server/puppetserver/ruby/puppet/lib/puppet/util/classgen.rb:132:in `genthing' /Users/aileen/code/server/puppetserver/ruby/puppet/lib/puppet/util/classgen.rb:33:in `genclass' /Users/aileen/code/server/puppetserver/ruby/puppet/lib/puppet/type.rb:1847:in `provide' /Users/aileen/code/server/puppetserver/ruby/puppet/lib/puppet/provider/service/init.rb:3:in `' org/jruby/RubyKernel.java:1009:in `load' /Users/aileen/code/server/puppetserver/ruby/puppet/lib/puppet/util/autoload.rb:78:in
Jira (PDB-5060) Release puppetlabs-puppetdb module
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5060 Release puppetlabs-puppetdb module Change By: Austin Blatt Assignee: Austin Blatt 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.390569.1615404434000.172424.1616539140031%40Atlassian.JIRA.
Jira (PDB-5055) Add a new query param that returns EXPLAIN ANALYZE output for a given query
Title: Message Title Rob Browning commented on PDB-5055 Re: Add a new query param that returns EXPLAIN ANALYZE output for a given query We might also consider adding a code comment somewhere reasonable (perhaps in or around one of the more relevant functions) describing the hypothetical plan so anyone who comes along to make adjustments later can consider it. 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.390060.1614896952000.172392.1616537400053%40Atlassian.JIRA.
Jira (PDB-5055) Add a new query param that returns EXPLAIN ANALYZE output for a given query
Title: Message Title Rob Browning commented on PDB-5055 Re: Add a new query param that returns EXPLAIN ANALYZE output for a given query After some discussion with Austin, we'd like to suggest some API changes. In particular, perhaps change the :explain?` parameter to :explain which would match the existing pretty, side-steps any questions about whether we'd want a question-mark in the query parameter name, or would need to change the name "on the way in", and also leave a convenient opening for future enhancements. In particular, we were thinking that perhaps this first version might only allow :explain :analyze rather than :explain true, under the argument that we might eventually want to allow other options, maybe like this: https://...?explain=analyze https://...?explain=analyze,no_verbose,no_buffers https://...?explain=no_analyze We might also process the comma-separated options from left to right so that later selections override earlier ones (which can be handy when programmatically generating queries: https://...?explain=analyze,no_verbose,buffers,verbose But we don't need any of that extended syntax for now (if ever). For now, we were thinking we might just implement explain=analyze (and internally :explain :analyze) and leave anything else for a hypothetical future. Add Comment
Jira (PUP-10972) puppet facts diff produces unexpected results
Title: Message Title Vadym Chepkov created an issue Puppet / PUP-10972 puppet facts diff produces unexpected results Issue Type: Bug Assignee: Unassigned Created: 2021/03/23 12:24 PM Priority: Normal Reporter: Vadym Chepkov Puppet Version: 6.21.1 Puppet Server Version: 2019.8.2.92 OS Name/Version: RHEL8.3 Observing failures and discrepancies while running puppet facts diff Example of a failure : # puppet facts diff E, [2021-03-23T15:10:50.151056 #1607340] ERROR -- : Facter - Error while resolving custom fact fact='java_version', resolution='': undefined method `include?' for nil:NilClass The error comes from https://github.com/puppetlabs/puppetlabs-java/blob/main/lib/facter/java_version.rb#L40, which should not be evaluated on RHEL, so confine statements are ignored, it seems Example of a discrepancy: # puppet facts diff ...
Jira (PUP-10922) The fqdn_rand() function should not assume case-consistency in the fqdn fact
Title: Message Title Gareth McGrillan commented on PUP-10922 Re: The fqdn_rand() function should not assume case-consistency in the fqdn fact Hi Robert August Vincent II, Would any of Ciprian's options be suitable fixes for you? Many thanks, Gareth... 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.387597.1613401978000.171964.1616522460477%40Atlassian.JIRA.
Jira (FACT-2994) selinux fact is not properly detected by Facter 4
Title: Message Title Vadym Chepkov commented on FACT-2994 Re: selinux fact is not properly detected by Facter 4 There can be bug in `puppet facts diff` itself. puppet facts find --facterng reports correct values 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.391989.1616519382000.171928.1616521620022%40Atlassian.JIRA.
Jira (FACT-2994) selinux fact is not properly detected by Facter 4
Title: Message Title Nick Walker assigned an issue to Mihai Buzgau Facter / FACT-2994 selinux fact is not properly detected by Facter 4 Change By: Nick Walker Assignee: Mihai Buzgau 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.391989.1616519382000.171881.1616520720325%40Atlassian.JIRA.
Jira (FACT-2994) selinux fact is not properly detected by Facter 4
Title: Message Title Nick Walker updated an issue Facter / FACT-2994 selinux fact is not properly detected by Facter 4 Change By: Nick Walker Priority: Normal Critical 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.391989.1616519382000.171874.1616520660098%40Atlassian.JIRA.
Jira (FACT-2994) selinux fact is not properly detected by Facter 4
Title: Message Title Vadym Chepkov created an issue Facter / FACT-2994 selinux fact is not properly detected by Facter 4 Issue Type: Bug Assignee: Unassigned Components: Facter 4 Created: 2021/03/23 10:09 AM Priority: Normal Reporter: Vadym Chepkov While evaluating facts difference using PE2019.8.5 / puppet 6.21.1 # puppet facts diff "os.selinux.enabled": { "new_value": true, "old_value": false },
Jira (PUP-10966) Allow full-relative path references in file(), template(), related functions
Title: Message Title Reid Vandewiele commented on PUP-10966 Re: Allow full-relative path references in file(), template(), related functions Josh Cooper the Bolt team have sketched out a pretty solid adoption and deprecation plan for Bolt, with regards to the use of pseudo-relative paths pertaining to Bolt scripts—e.g. run_script()—which used to borrow the idiom. What would it take for Puppet to align with their deprecation plan, albeit with a MUCH longer (probably indefinite) deprecation period for the old pathing? 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.391231.1615913392000.171664.1616516040625%40Atlassian.JIRA.
Jira (PUP-10946) Recursive file resources generate dangerous numbers of resource events
Title: Message Title Mihai Buzgau assigned an issue to Nick Walker Puppet / PUP-10946 Recursive file resources generate dangerous numbers of resource events Change By: Mihai Buzgau Assignee: Nick Walker 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.389668.1614728039000.171538.1616513640043%40Atlassian.JIRA.
Jira (FACT-2993) Facter 4.0.52 does not provide trusted['hostname'] in Docker environments
Title: Message Title Gheorghe Popescu commented on FACT-2993 Re: Facter 4.0.52 does not provide trusted['hostname'] in Docker environments Manuel Laug i think this is the same issue as in: https://tickets.puppetlabs.com/browse/FACT-2989 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.391951.1616498838000.171428.1616506800232%40Atlassian.JIRA.
Jira (FACT-2966) Facter 4 outputs some uptime facts differently on Windows
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Facter / FACT-2966 Facter 4 outputs some uptime facts differently on Windows Change By: Gabriel Nagy Assignee: Gabriel Nagy 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.390835.1615559748000.171387.1616500140036%40Atlassian.JIRA.
Jira (FACT-2993) Facter 4.0.52 does not provide trusted['hostname'] in Docker environments
Title: Message Title Manuel Laug updated an issue Facter / FACT-2993 Facter 4.0.52 does not provide trusted['hostname'] in Docker environments Change By: Manuel Laug We du run Puppet RSpec tests in a Gitlab Pipeline and use a specific Ruby Docker Image for that (basically *ruby:2-alpine* with some additional packages).I've noticed that tests depending on *$::trusted['hostname']* start failing with *Facter 4.0.52* as the variable is *Undef*. Running the exact same test using *Facter 4.0.51* works fine (as it did with all previous versions we used).Interestingly this only happens when running the tests using the Docker Image (in Gitlab and also locally). If I execute the tests on a MacOS or Linux system directly, they successfully run throw no error .I've also tried using a different Puppet and Ruby version, but had the exact same behaviour. 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" g
Jira (FACT-2993) Facter 4.0.52 does not provide trusted['hostname'] in Docker environments
Title: Message Title Manuel Laug created an issue Facter / FACT-2993 Facter 4.0.52 does not provide trusted['hostname'] in Docker environments Issue Type: Bug Affects Versions: FACT 4.0.52 Assignee: Unassigned Components: Facter 4 Created: 2021/03/23 4:27 AM Environment: Puppet version: 6.21.0 and 7.3.0 Facter version: 4.0.52 Ruby version: 2.5.7 and 2.7.1 Priority: Normal Reporter: Manuel Laug We du run Puppet RSpec tests in a Gitlab Pipeline and use a specific Ruby Docker Image for that (basically ruby:2-alpine with some additional packages). I've noticed that tests depending on $::trusted['hostname'] start failing with Facter 4.0.52 as the variable is Undef. Running the exact same test using Facter 4.0.51 works fine (as it did with all previous versions we used). Interestingly this only happens when running the tests using the Docker Image (in Gitlab and also locally). If I execute the tests on a MacOS system, they successfully run. I've also tried using a different Puppet and Ruby version, but had the exact same behaviour.
Jira (FACT-2993) Facter 4.0.52 does not provide trusted['hostname'] in Docker environments
Title: Message Title Manuel Laug updated an issue Facter / FACT-2993 Facter 4.0.52 does not provide trusted['hostname'] in Docker environments Change By: Manuel Laug We du run Puppet RSpec tests in a Gitlab Pipeline and use a specific Ruby Docker Image for that (basically *ruby:2-alpine* with some additional packages).I've noticed that tests depending on *$::trusted['hostname']* start failing with *Facter 4.0.52* as the variable is *Undef*. Running the exact same test using *Facter 4.0.51* works fine (as it did with all previous versions we used).Interestingly this only happens when running the tests using the Docker Image (in Gitlab and also locally). If I execute the tests on a MacOS or Linux system directly , they successfully run.I've also tried using a different Puppet and Ruby version, but had the exact same behaviour. 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 unsub
Jira (PDB-5043) Collect common PDB queries used in PE console pages
Title: Message Title Florin Dragos assigned an issue to Florin Dragos PuppetDB / PDB-5043 Collect common PDB queries used in PE console pages Change By: Florin Dragos Assignee: Florin Dragos 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.388381.1614031085000.171275.1616490900048%40Atlassian.JIRA.
Jira (PDB-5025) Add unit tests with the AST queries that are present in the documentation
Title: Message Title Andrei Filipovici assigned an issue to Andrei Filipovici PuppetDB / PDB-5025 Add unit tests with the AST queries that are present in the documentation Change By: Andrei Filipovici Assignee: Andrei Filipovici 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.387681.1613494472000.171247.1616488260153%40Atlassian.JIRA.
Jira (FACT-2989) Facter 4.0.52 does not return fqdn fact
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2989 Facter 4.0.52 does not return fqdn fact Change By: Gheorghe Popescu Release Notes Summary: Update the linux/networking resolver to loadFFI if previous tries of getting the host informationfailed. 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.391442.1615994661000.171194.1616484240041%40Atlassian.JIRA.
Jira (FACT-2989) Facter 4.0.52 does not return fqdn fact
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2989 Facter 4.0.52 does not return fqdn fact Change By: Gheorghe Popescu Fix Version/s: FACT 4.0.53 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.391442.1615994661000.171195.1616484240101%40Atlassian.JIRA.
Jira (FACT-2989) Facter 4.0.52 does not return fqdn fact
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2989 Facter 4.0.52 does not return fqdn fact Change By: Gheorghe Popescu Release Notes: Bug 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.391442.1615994661000.171193.1616484120051%40Atlassian.JIRA.