Jira (FACT-3071) macosx_productversion_major returns wrong value for Big Sur
Title: Message Title Michael Hashizume created an issue Facter / FACT-3071 macosx_productversion_major returns wrong value for Big Sur Issue Type: Task Assignee: Unassigned Created: 2021/09/01 3:21 PM Priority: Normal Reporter: Michael Hashizume I'm not sure if this is the right project to report this but: In our PE environment (2019.8.7), macOS 11 Big Sur nodes (running Puppet agent 6.23.0) report that each minor release of Big Sur as separate major release in the macosx_productversion_major fact. For example, macOS 11.1 and 11.5 are treated as separate major releases, when they're both just minor releases of the macOS 11 line. This is easy to work around using other facts, but I thought I'd file a ticket anyway. Thanks! Add Comment
Jira (PUP-10897) List "manages local users and groups" (forcelocal) provider support as "with libuser"
Title: Message Title Ciprian Badescu commented on PUP-10897 Re: List "manages local users and groups" (forcelocal) provider support as "with libuser" Valters Jansons, we plan to update the resource documentation details with the dependency, like we do for lib shadow. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.387112.1613051573000.121336.1630501920030%40Atlassian.JIRA.
Jira (PUP-11236) Reduce allocated memory in `lib/puppet/pops/parser/lexer2.rb`
Title: Message Title Luchian Nemes created an issue Puppet / PUP-11236 Reduce allocated memory in `lib/puppet/pops/parser/lexer2.rb` Issue Type: Bug Assignee: Unassigned Created: 2021/09/01 5:51 AM Priority: Normal Reporter: Luchian Nemes PUP-11232 added # frozen_string_literal: true to some high memory consumption files but even after that, lib/puppet/pops/parser/lexer2.rb still seems to have the most memory allocated. Proposed investigation direction as stated by Josh Cooper: I'm guessing the lexer2 allocations are due to the closure scope bound to each lambda? I'm thinking Ruby may be doing more work than is necessary to create the Binding as each token is scanned and the corresponding lambda is called? Or perhaps it's the byteslice calls? Add Comment
Jira (FACT-3070) Facter whitelist
Title: Message Title Vladislav Pozniak created an issue Facter / FACT-3070 Facter whitelist Issue Type: Improvement Assignee: Unassigned Created: 2021/09/01 3:31 AM Priority: Normal Reporter: Vladislav Pozniak Currently, there is feature to block groups of facts via 'blocklist' facter.conf option. But there is no feature to whitelist some facts. Practical example: I have XEN and KVM hypervisors. Networks on them are configured with network module. For bonding I need to gather macaddress_eth0 and macaddress_eth1 info to use it in config files. But with this facts, facter collects all the macaddresses of virtual servers on hypervisor, like: macaddress_dxvkvottfafeuf ac:1f:6b:bd:65:9a macaddress_eshezzolxuwgui fe:16:3e:ca:52:56 macaddress_eth0 ac:1f:6b:bd:65:98 macaddress_eth0.505 ac:1f:6b:bd:65:98
Jira (PUP-11235) versioncmp() thinks 11.0 is greater than 11
Title: Message Title
Tim Meusel created an issue
Puppet / PUP-11235
versioncmp() thinks 11.0 is greater than 11
Issue Type:
Bug
Assignee:
Unassigned
Created:
2021/09/01 1:47 AM
Priority:
Normal
Reporter:
Tim Meusel
Puppet Version: 6.24.0 Puppet Server Version: none OS Name/Version: Debian 11 while debugging https://github.com/puppetlabs/puppetlabs-apache/pull/2186 i noticed that versioncmp('11.0', '11') doesn't return 0, it returns 1. Is that expected? Desired Behavior: I think 11.0 and 11 should be treated as equal Actual Behavior: versioncmp() thinks 11.0 is greater than 11 to debug:
notify { "operatingsystemrelease compared to 11: ${versioncmp($::operatingsystemrelease, '11')}":
}
notify { "operatingsystemmajrelease compared to 11: ${versioncmp($::operatingsystemmajrelease, '11')}":
}
notify { "operatingsystemrelease: ${::operatingsystemrelease}":
Jira (PDB-4305) "null?" query of facts against the query/v4/nodes endpoint results in "Value does not match schema" errors
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-4305 "null?" query of facts against the query/v4/nodes endpoint results in "Value does not match schema" errors Change By: Bogdan Irimie Sprint: ghost-22.09.2021 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.300026.1552508578000.121179.1630483080093%40Atlassian.JIRA.
Jira (PDB-4305) "null?" query of facts against the query/v4/nodes endpoint results in "Value does not match schema" errors
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-4305 "null?" query of facts against the query/v4/nodes endpoint results in "Value does not match schema" errors Change By: Bogdan Irimie Team: PuppetDB Ghost Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.300026.1552508578000.121178.1630483080049%40Atlassian.JIRA.
Jira (PDB-4305) "null?" query of facts against the query/v4/nodes endpoint results in "Value does not match schema" errors
Title: Message Title Bogdan Irimie commented on PDB-4305 Re: "null?" query of facts against the query/v4/nodes endpoint results in "Value does not match schema" errors We should determine on what endpoints "null?" works and on which ones it errors. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.300026.1552508578000.121177.1630483020028%40Atlassian.JIRA.
Jira (PDB-4305) "null?" query of facts against the query/v4/nodes endpoint results in "Value does not match schema" errors
Title: Message Title Bogdan Irimie commented on PDB-4305 Re: "null?" query of facts against the query/v4/nodes endpoint results in "Value does not match schema" errors On the 6.x branch of PDB, when running curl -sX GET http://localhost:8080/pdb/query/v4/nodes --data-urlencode 'query=["null?", ["fact", "id"], false]' we get class clojure.lang.PersistentVector cannot be cast to class java.lang.CharSequence (clojure.lang.PersistentVector is in unnamed module of loader 'app'; java.lang.CharSequence is in module java.base of loader 'bootstrap')% if we change https://github.com/puppetlabs/puppetdb/blob/342112865bcda061269a19335f19e13d6e449559/src/puppetlabs/puppetdb/query_eng/engine.clj#L2410 to (let [maybe-dotted-path (if (vector? column-name) nil (str/split column-name #"\.")) we get Value does not match schema: (not (map? nil))
Jira (PUP-11234) ERROR -- : yaml_facts.rb:35:in `rescue in block in load_facts_from_source' Failed to load yaml facts from /etc/puppetlabs/mcollective/facts.yaml: TypeError: no implicit conversion of
Title: Message Title sonali created an issue Puppet / PUP-11234 ERROR -- : yaml_facts.rb:35:in `rescue in block in load_facts_from_source' Failed to load yaml facts from /etc/puppetlabs/mcollective/facts.yaml: TypeError: no implicit conversion of String into Hash Issue Type: Bug Affects Versions: FACT 4.0.44 Assignee: sonali Components: Hiera & Lookup Created: 2021/09/01 12:34 AM Fix Versions: PUP 6.25.0 Priority: High Reporter: sonali Puppet Version: Puppet Server Version: OS Name/Version: Describe your issue in as much detail as possible… Describe steps to reproduce… Desired Behavior: Actual Behavior: Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. Examples: Run puppet agent with --test --trace --debug Relevant sections of /var/log/puppetlabs/puppetserver/puppetserver.log or any applicable logs from the same directory. For more detailed information turn up the server logs by upping the log level in the server's logback.xml Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig) For memory issues with server heap dumps are also helpful.
