Jira (PDB-3171) query compilation is very slow for queries with giant arrays
Title: Message Title Ingrida Cazers commented on PDB-3171 Re: query compilation is very slow for queries with giant arrays I will plan to document this update in the PE release notes, and will leave it to the PuppetDB develoment team to document it in the PuppetDB release notes. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.159741.1478279255000.2731.1679518440086%40Atlassian.JIRA.
Jira (FACT-3170) Facter resolves facts multiple times when providers are confined based on facts, especially on Windows
Title: Message Title Ingrida Cazers commented on FACT-3170 Re: Facter resolves facts multiple times when providers are confined based on facts, especially on Windows I'm preparing to document this fix in the PE release notes. Does the fix also have to be documented in the Facter release notes? https://www.puppet.com/docs/puppet/7/release_notes_facter.html#release_notes_facter If so, does the development team handle the update in the Facter release notes? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.477181.1671137416000.2721.1679516880079%40Atlassian.JIRA.
Jira (PDB-5582) Remove metrics/v1 references
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5582 Remove metrics/v1 references Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.479640.1674756239000.2717.1679516700023%40Atlassian.JIRA.
Jira (PDB-5589) Investigate pdb upgrade times with migration 81/82
Title: Message Title Austin Blatt commented on PDB-5589 Re: Investigate pdb upgrade times with migration 81/82 Please take these results very loosely, they were produced on a laptop. Migration results running migrations 81 and 82 0 reports - 81ms 6,720 reports - 135ms 35,500 reports - 185ms 67,200 reports - 188ms There is some impact in migration time when more data is added, but it may even tail off as you get more data in a partition. Even if we ignore the final run with 67k nodes, extrapolating from the first three data points linearly puts 67.2 million reports (100k nodes with a run interval of 30 minutes and a history of 14 days) at 172 seconds — or just under 3 minutes. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.480704.1675468795000.2715.1679516400029%40Atlassian.JIRA.
Jira (PDB-5589) Investigate pdb upgrade times with migration 81/82
Title: Message Title Austin Blatt commented on PDB-5589 Re: Investigate pdb upgrade times with migration 81/82 Noticed a 2 index difference between the new and old version. Partitions have a primary key, which is expected, but there also appears to be a duplicate index being created (at least by the migration). This was run against an brand new postgres 15.2, where the bug was supposed to have been fixed. "reports_20230318z_encode_producer_timestamp_idx" UNIQUE, btree (encode(hash, 'hex'::text), producer_timestamp) "reports_hash_expr_idx_20230318z" UNIQUE, btree (encode(hash, 'hex'::text)) the id index is also not removed in the migration, but does not continue into a newly created partition. "idx_reports_id_20230318z" UNIQUE, btree (id) These issues go away for new partitions, so I don't know how big of an issue they are. Add Comment
Jira (PUP-11783) Delete pson code from puppet
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11783 Delete pson code from puppet Change By: Josh Cooper Release Notes: Enhancement Release Notes Summary: This is a breaking change in Puppet 8. Puppet will no longer support the PSON serialization format by default. The code was extracted into a separate gem, puppet-pson. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.482933.1678895719000.2697.1679511120025%40Atlassian.JIRA.
Jira (PUP-9648) Prepare Puppet for PSON removal
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9648 Prepare Puppet for PSON removal Change By: Josh Cooper Release Notes: Not Needed Release Notes Summary: Will be documented in PUP-11783 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.305621.1555690549000.2679.1679509200024%40Atlassian.JIRA.
Jira (PUP-11785) Don't fallback if catalog rendering fails
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11785 Don't fallback if catalog rendering fails Change By: Josh Cooper If puppetserver fails to serialize a catalog to JSON it will fallback to PSON, because there was a time where rich data wasn't supported end-to-end between server and agents. However, rich data is now enabled by default and supported end-to-end. And it required when using Deferred or Sensitive parameters. Therefore, if puppetserver downgrades to PSON it can lead to surprising behavior as described in PUP-10928.In Puppet 8, we will no longer fallback to PSON. If a user wants binary data in the if catalog , such as a Kerberos keytab file, then they should use `content => binary_file( rendering/serialization fails . ..)` in a file resource. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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
Jira (PUP-11785) Don't fallback if catalog rendering fails
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11785 Don't fallback if catalog rendering fails Change By: Josh Cooper Summary: Don't fallback to PSON if catalog rendering fails Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.483276.1679434736000.2674.1679508600025%40Atlassian.JIRA.
Jira (FACT-2954) Improve fact blocking mechanism in Facter 4
Title: Message Title Josh Cooper updated an issue Facter / FACT-2954 Improve fact blocking mechanism in Facter 4 Change By: Josh Cooper Priority: High Normal Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.389707.1614771236000.2646.1679506260094%40Atlassian.JIRA.
Jira (FACT-2954) Improve fact blocking mechanism in Facter 4
Title: Message Title Josh Cooper updated an issue Facter / FACT-2954 Improve fact blocking mechanism in Facter 4 Change By: Josh Cooper Facter's block list logic is O^2 (comparing every fact against every blocked fact) [https://github.com/puppetlabs/facter/blob/83aa51aa822aea7cf5ac6762039a4529f73a2a82/lib/facter/framework/core/fact_loaders/fact_loader.rb#L100-L117.]Also it creates a an interpolated regexp literal inside of the loop , which are [not frozen until ruby 3|https://github.com/ruby/ruby/commit/98ef38ada43338c073f50a0093196f0356284625] (multiple times for the same blocked fact) So we're doing a bunch of unnecessary allocations. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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
Jira (FACT-2954) Improve fact blocking mechanism in Facter 4
Title: Message Title Josh Cooper updated an issue Facter / FACT-2954 Improve fact blocking mechanism in Facter 4 Change By: Josh Cooper Facter's block list logic is O^2 (comparing every fact against every blocked fact) [https://github.com/puppetlabs/facter/blob/83aa51aa822aea7cf5ac6762039a4529f73a2a82/lib/facter/framework/core/fact_loaders/fact_loader.rb#L100-L117.]Also it creates a regexp literal inside of the loop, which are [not frozen until ruby 3| [ https://github.com/ruby/ruby/commit/98ef38ada43338c073f50a0093196f0356284625] ] So we're doing a bunch of unnecessary allocations. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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
Jira (FACT-2954) Improve fact blocking mechanism in Facter 4
Title: Message Title Josh Cooper updated an issue Facter / FACT-2954 Improve fact blocking mechanism in Facter 4 Change By: Josh Cooper Facter's block list logic is O^2 (comparing every fact against every blocked fact) [https://github.com/puppetlabs/facter/blob/83aa51aa822aea7cf5ac6762039a4529f73a2a82/lib/facter/framework/core/fact_loaders/fact_loader.rb#L100-L117.]Also it creates a regexp literal inside of the loop, which are [not frozen until ruby 3|[https://github.com/ruby/ruby/commit/98ef38ada43338c073f50a0093196f0356284625]] So we're doing a bunch of unnecessary allocations. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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
Jira (FACT-2954) Improve fact blocking mechanism in Facter 4
Title: Message Title Josh Cooper updated an issue Facter / FACT-2954 Improve fact blocking mechanism in Facter 4 Change By: Josh Cooper Epic Link: FACT PUP - 3051 11659 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.389707.1614771236000.2641.1679505840029%40Atlassian.JIRA.
Jira (FACT-3080) facter.conf facts and fact-groups sections make facter very slow.
Title: Message Title Josh Cooper commented on FACT-3080 Re: facter.conf facts and fact-groups sections make facter very slow. This seems to be a duplicate of FACT-3170, which was fixed in facter 4.3.0. Using the latest 7.x version I don't see meaningful slow down when running `facter` or `puppet facts show`: [root@theatrical-den ~]# facter --version 4.3.1 [root@theatrical-den ~]# rpm -qa puppet-agent puppet-agent-7.23.0.64.gaddb5176e-1.el7.x86_64 [root@theatrical-den ~]# cp full-facter.conf /etc/puppetlabs/facter/facter.conf [root@theatrical-den ~]# time facter > /dev/null real 0m0.940s user 0m0.796s sys 0m0.128s [root@theatrical-den ~]# time puppet facts show > /dev/null
Jira (FACT-2954) Improve fact blocking mechanism in Facter 4
Title: Message Title Josh Cooper updated an issue Facter / FACT-2954 Improve fact blocking mechanism in Facter 4 Change By: Josh Cooper Priority: Normal High Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.389707.1614771236000.2634.1679504880072%40Atlassian.JIRA.
Jira (FACT-2954) Improve fact blocking mechanism in Facter 4
Title: Message Title Josh Cooper commented on FACT-2954 Re: Improve fact blocking mechanism in Facter 4 FACT-3161 is actually a separate (but related) issue, so reopening this ticket. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.389707.1614771236000.2631.1679504820078%40Atlassian.JIRA.
Jira (FACT-2954) Improve fact blocking mechanism in Facter 4
Title: Message Title Josh Cooper updated an issue Facter / FACT-2954 Improve fact blocking mechanism in Facter 4 Change By: Josh Cooper Story Points: 5 3 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.389707.1614771236000.2632.1679504820125%40Atlassian.JIRA.
Jira (FACT-3161) "puppet facts" slow down if blocklist used and gets longer
Title: Message Title Josh Cooper updated an issue Facter / FACT-3161 "puppet facts" slow down if blocklist used and gets longer Change By: Josh Cooper Summary: Puppet facter "puppet facts" slow down if blocklist used and gets longer Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.471201.1665759172000.2627.1679504700027%40Atlassian.JIRA.
Jira (FACT-3161) Puppet facter slow down if blocklist used and gets longer
Title: Message Title
Josh Cooper commented on FACT-3161
Re: Puppet facter slow down if blocklist used and gets longer
The slowdown when running "puppet" but not facter is due to FACT-3170, which was fixed in facter 4.3.0. When testing against the latest 7.x, I don't see a slowdown so I'm going to close this as a dup. Thanks for including steps to reproduce!
# rpm -qa puppet-agent
puppet-agent-7.23.0.64.gaddb5176e-1.el7.x86_64
# for i in 0 1 2 4 8 16 32 64; do echo "Blocklist items $i"; ( echo "facts : { blocklist : [ "; for j in $(seq 1 $i); do echo "\"a$j\","; done; echo "] }"; ) > /etc/puppetlabs/facter/facter.conf; echo "Executing 'sudo /opt/puppetlabs/bin/puppet facts | wc -l'"; time sudo /opt/puppetlabs/bin/puppet facts | wc -l; done
Blocklist items 0
Executing 'sudo /opt/puppetlabs/bin/puppet facts | wc -l'
461real 0m1.200s
user 0m0.973s
sys 0m0.209s
Blocklist items 1
Executing 'sudo /opt/puppetlabs/bin/puppet facts | wc -l'
461real 0m1.197s
Jira (FACT-3080) facter.conf facts and fact-groups sections make facter very slow.
Title: Message Title Josh Cooper updated an issue Facter / FACT-3080 facter.conf facts and fact-groups sections make facter very slow. Change By: Josh Cooper Priority: Normal High Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.418654.1633538203000.2603.1679504040140%40Atlassian.JIRA.
Jira (FACT-1902) Confirm Facter 4 validates that external/custom/executable facts output proper UTF-8
Title: Message Title Josh Cooper updated an issue Facter / FACT-1902 Confirm Facter 4 validates that external/custom/executable facts output proper UTF-8 Change By: Josh Cooper Priority: Major High Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.290197.1546471789000.2600.1679503920273%40Atlassian.JIRA.
Jira (PUP-11663) max/min core functions are incorrect for Semver types
Title: Message Title Michael Hashizume assigned an issue to Michael Hashizume Puppet / PUP-11663 max/min core functions are incorrect for Semver types Change By: Michael Hashizume Assignee: Michael Hashizume Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.473277.1666723189000.2570.1679503320030%40Atlassian.JIRA.
Jira (PUP-11622) Ruby 2 EOL
Title: Message Title Josh Cooper commented on PUP-11622 Re: Ruby 2 EOL Phil Here's our statement about Ruby 2.7: https://support.puppet.com/hc/en-us/articles/12817411224215 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.466233.1662001062000.2560.1679502960021%40Atlassian.JIRA.
