Jira (PDB-5203) Script that runs the pdb locust load tests
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5203 Script that runs the pdb locust load tests Change By: Bogdan Irimie Sprint: ghost-25.08.2021 , ghost-08.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.408406.162704879.116154.1629877080041%40Atlassian.JIRA.
Jira (PDB-5252) Determine trigram index on facts size impact
Title: Message Title Bogdan Irimie created an issue PuppetDB / PDB-5252 Determine trigram index on facts size impact Issue Type: Task Assignee: Unassigned Created: 2021/08/25 12:52 AM Priority: Normal Reporter: Bogdan Irimie We should answer these questions: how much space does an index for a fact take? how much space do 10 indexes take? is there any performance decrease on ingestion? can we add indexes on nested fact? Add Comment
Jira (PUP-11214) Environments get ignored via node_terminus exec
Title: Message Title Sebastian commented on PUP-11214 Re: Environments get ignored via node_terminus exec tested several scenarios today again. seems to be the error goes away after updating puppetserver from puppetserver-7.2.1-1.el7.noarch to puppetserver.noarch 0:7.3.0-1.el7. thanks for your time. 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.412817.1629454367000.116158.1629878040027%40Atlassian.JIRA.
Jira (PDB-5252) Determine trigram index on facts size impact
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5252 Determine trigram index on facts size impact Change By: Bogdan Irimie We should answer these questions:* how much space does an index for a fact take (sandbox size on disk and index size obtain with SQL query) ?* how much space do 10 indexes take?* is there any performance decrease on ingestion?* can we add indexes on nested fact? 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.413371.1629877927000.116159.1629878160034%40Atlassian.JIRA.
Jira (PDB-5252) Determine trigram index on facts size impact
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5252 Determine trigram index on facts size impact Change By: Bogdan Irimie Story Points: 3 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.413371.1629877927000.116162.1629878700121%40Atlassian.JIRA.
Jira (FACT-2904) Port AWS IDMSv2 to facter 3.x
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-2904 Port AWS IDMSv2 to facter 3.x Change By: Ciprian Badescu Story Points: 3 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.381344.1608195319000.116161.1629878700071%40Atlassian.JIRA.
Jira (PDB-5253) Investigate if we can we add indexes on nested facts
Title: Message Title Bogdan Irimie created an issue PuppetDB / PDB-5253 Investigate if we can we add indexes on nested facts Issue Type: Task Assignee: Unassigned Created: 2021/08/25 1:05 AM Priority: Normal Reporter: Bogdan Irimie 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.
Jira (PDB-5252) Determine trigram index on facts size impact
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5252 Determine trigram index on facts size impact Change By: Bogdan Irimie We should answer these questions:* how much space does an index for a fact take (sandbox size on disk and index size obtain with SQL query)?* how much space do 10 indexes take?* is there any performance decrease on ingestion? * can we add indexes on nested fact? 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.413371.1629877927000.116165.1629878760161%40Atlassian.JIRA.
Jira (PDB-5253) Investigate if we can we add indexes on nested facts
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5253 Investigate if we can we add indexes on nested facts Change By: Bogdan Irimie Sprint: ghost-08.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.413374.1629878715000.116168.1629878820173%40Atlassian.JIRA.
Jira (PDB-5253) Investigate if we can we add indexes on nested facts
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5253 Investigate if we can we add indexes on nested facts Change By: Bogdan Irimie Story Points: 2 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.413374.1629878715000.116167.1629878820118%40Atlassian.JIRA.
Jira (PDB-5252) Determine trigram index on facts size impact
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5252 Determine trigram index on facts size impact Change By: Bogdan Irimie Sprint: ghost-08.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.413371.1629877927000.116169.1629878820217%40Atlassian.JIRA.
Jira (PDB-5204) Perform diff on the locust results
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5204 Perform diff on the locust results Change By: Bogdan Irimie Compare the current locust run results with those from the previous (run) week. If the difference between the times is higher than 20% write We should generate a CSV that in an alert file.One alert file entry must contain, compared commit shas, compared has the statistics for each run dates, sandbox name, with or without ingestion, users number on a row . 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.408407.1627050042000.116170.1629878940030%40Atlassian.JIRA.
Jira (PDB-5204) Perform diff on the locust results
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5204 Perform diff on the locust results Change By: Bogdan Irimie Compare the current locust run results with those from the previous (run) week.We should generate a CSV that has the statistics for each run on a row. FOr each entry the CSV should contain the SHA of the run, the timestamp, avg response time and diff to the last run. 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.408407.1627050042000.116172.1629879060125%40Atlassian.JIRA.
Jira (PDB-5204) Perform diff on the locust results
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5204 Perform diff on the locust results Change By: Bogdan Irimie Compare the current locust run results with those from the previous (run) week.We should generate a CSV that has the statistics for each run on a row. FOr For each entry the CSV should contain the SHA of the run, the timestamp, avg response time and diff to the last run. 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.408407.1627050042000.116177.1629879240032%40Atlassian.JIRA.
Jira (PDB-5204) Perform diff on the locust results
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5204 Perform diff on the locust results Change By: Bogdan Irimie Attachment: Screenshot 2021-08-25 at 11.29.54.png 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.408407.1627050042000.116184.1629880260054%40Atlassian.JIRA.
Jira (PDB-5204) Perform diff on the locust results
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5204 Perform diff on the locust results Change By: Bogdan Irimie Story Points: 2 3 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.408407.1627050042000.116186.1629880320098%40Atlassian.JIRA.
Jira (PDB-5204) Perform diff on the locust results
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5204 Perform diff on the locust results Change By: Bogdan Irimie Story Points: 2 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.408407.1627050042000.116185.1629880320051%40Atlassian.JIRA.
Jira (PUP-11193) SemanticPuppet does not solve nested dependencies
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11193 SemanticPuppet does not solve nested dependencies Change By: Ciprian Badescu Sprint: NW-2021-09-08 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.409162.1627567017000.116195.1629880440177%40Atlassian.JIRA.
Jira (PDB-4731) Misspelled query modifiers like groupy_by can result in all results being returned
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-4731 Misspelled query modifiers like groupy_by can result in all results being returned Change By: Bogdan Irimie Team: HA 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.358865.1589476358000.116196.1629880560032%40Atlassian.JIRA.
Jira (PDB-4731) Misspelled query modifiers like groupy_by can result in all results being returned
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-4731 Misspelled query modifiers like groupy_by can result in all results being returned Change By: Bogdan Irimie Sprint: ghost-08.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.358865.1589476358000.116199.1629880920152%40Atlassian.JIRA.
Jira (PDB-5205) Configure lein-nvd Jenkins job to create Jira SEC ticket
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5205 Configure lein-nvd Jenkins job to create Jira SEC ticket Change By: Bogdan Irimie Sprint: ghost- 08 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.408542.1627286812000.116200.1629881040028%40Atlassian.JIRA.
Jira (PDB-5220) Investigate query performance for "CONS - reports attributes"
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5220 Investigate query performance for "CONS - reports attributes" Change By: Bogdan Irimie Sprint: ghost- 08 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.409153.162756614.116201.1629881100032%40Atlassian.JIRA.
Jira (PDB-4731) Misspelled query modifiers like groupy_by can result in all results being returned
Title: Message Title Bogdan Irimie assigned an issue to Oana Tanasoiu PuppetDB / PDB-4731 Misspelled query modifiers like groupy_by can result in all results being returned Change By: Bogdan Irimie Assignee: Oana Tanasoiu 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.358865.1589476358000.116202.1629881160035%40Atlassian.JIRA.
Jira (PDB-5204) Perform diff on the locust results
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5204 Perform diff on the locust results Change By: Bogdan Irimie Compare the current locust run results with those from the previous (run) week.We should generate a CSV that has the statistics for each run query on a new row.For each entry the CSV should contain the SHA of the run query name , the SHA - timestamp , and avg response time and diff to the last run . 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.408407.1627050042000.116204.1629881280103%40Atlassian.JIRA.
Jira (PUP-11232) freeze string in the prime candidates files
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11232 freeze string in the prime candidates files Change By: Ciprian Badescu Story Points: 3 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.413213.1629801903000.116232.1629882480029%40Atlassian.JIRA.
Jira (PUP-11216) Add support for multiple Facter implementations
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11216 Add support for multiple Facter implementations Change By: Ciprian Badescu Sprint: NW-2021- 10 09 - 06 08 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.412975.162972246.116233.1629883200029%40Atlassian.JIRA.
Jira (PUP-11216) Add support for multiple Facter implementations
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11216 Add support for multiple Facter implementations Change By: Ciprian Badescu Story Points: 5 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.412975.162972246.116235.1629883260091%40Atlassian.JIRA.
Jira (PUP-11217) Replace `Facter.value` with the new Facter Implementation
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11217 Replace `Facter.value` with the new Facter Implementation Change By: Ciprian Badescu Sprint: NW-2021- 10 09 - 06 08 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.412976.1629722586000.116236.1629883320027%40Atlassian.JIRA.
Jira (PUP-11217) Replace `Facter.value` with the new Facter Implementation
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11217 Replace `Facter.value` with the new Facter Implementation Change By: Ciprian Badescu Story Points: 3 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.412976.1629722586000.116237.1629883380026%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-3039 Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Change By: Ciprian Badescu Sprint: NW-2021-08-25 , NW-2021-09-08 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.380977.1608048829000.116238.1629883440027%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-3039 Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Change By: Ciprian Badescu Sprint: NW-2021-08-25 , NW-2021-09-08 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.380977.1608048829000.116239.1629883500027%40Atlassian.JIRA.
Jira (PDB-5252) Determine trigram index on facts size impact
Title: Message Title Andrei Filipovici assigned an issue to Andrei Filipovici PuppetDB / PDB-5252 Determine trigram index on facts size impact Change By: Andrei Filipovici Assignee: Andrei Filipovici 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.413371.1629877927000.116250.1629885180029%40Atlassian.JIRA.
Jira (PUP-11232) freeze string in the prime candidates files
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11232 freeze string in the prime candidates files Change By: Ciprian Badescu Story Points: 3 2 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.413213.1629801903000.116260.1629887460077%40Atlassian.JIRA.
Jira (PUP-11232) freeze string in the prime candidates files
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11232 freeze string in the prime candidates files Change By: Ciprian Badescu Story Points: 2 3 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.413213.1629801903000.116261.1629888180035%40Atlassian.JIRA.
Jira (PUP-11196) puppet warns about BOM and US-ASCII encoding
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11196 puppet warns about BOM and US-ASCII encoding Change By: Ciprian Badescu Team: Night's Watch 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.409781.1628013472000.116263.1629888300075%40Atlassian.JIRA.
Jira (PUP-11196) puppet warns about BOM and US-ASCII encoding
Title: Message Title
Ciprian Badescu updated an issue
Puppet / PUP-11196
puppet warns about BOM and US-ASCII encoding
Change By:
Ciprian Badescu
The fix for PUP-8243 causes ruby to generate a warning if the default external encoding is US-ASCII: {noformat} /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/file_system/file_impl.rb:83: warning: BOM with non-UTF encoding US-ASCII is nonsense {noformat} Since ASCII characters are single bytes, there is no need for a BOM to detect byte ordering (LSB/MSB), hence the message. I had assumed ruby would just ignore the `bom` prefix.We'll need to check that the current external encoding starts with `utf-` (case-insensitively I think), and only add the `bom` prefix if it does.See [ https://github.com/puppetlabs/puppet/pull/8639#issuecomment-891939114 ] To reproduce: {noformat} $ bx ruby -e 'Encoding.default_external = "US-ASCII"; require "puppet"; Puppet::FileSystem.read_preserve_line_endings("Gemfile")'/home/josh/work/puppet/lib/puppet/file_system/file_impl.rb:83: warning: BOM with non-UTF encoding US-ASCII is nonsense{noformat}
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (FACT-2904) Port AWS IDMSv2 to facter 3.x
Title: Message Title Victor Bobosila assigned an issue to Victor Bobosila Facter / FACT-2904 Port AWS IDMSv2 to facter 3.x Change By: Victor Bobosila Assignee: Victor Bobosila 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.381344.1608195319000.116271.1629890820049%40Atlassian.JIRA.
Jira (PUP-11216) Add support for multiple Facter implementations
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-11216 Add support for multiple Facter implementations Change By: Gheorghe Popescu Assignee: Gheorghe Popescu 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.412975.162972246.116272.1629890940030%40Atlassian.JIRA.
Jira (PUP-11196) puppet warns about BOM and US-ASCII encoding
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11196 puppet warns about BOM and US-ASCII encoding Change By: Ciprian Badescu Story Points: 1 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.409781.1628013472000.116279.1629893280082%40Atlassian.JIRA.
Jira (PDB-5252) Determine trigram index on facts size impact
Title: Message Title
Andrei Filipovici commented on PDB-5252
Re: Determine trigram index on facts size impact
Run the tests on the n1 server on a 100k nodes sandbox. The initial sandbox size was 23Gb / 22804mb / 23911510356 bytes. Total indexes size on table factsets was 95 mb / 99500032 bytes and we got it by running this sql query: SELECT pg_size_pretty (pg_indexes_size('factsets')); Individual index size was: relation | size -+--- public.idx_factsets_jsonb_merged | 81 MB public.factsets | 17 MB. (don't know what that is) public.factsets_hash_expr_idx | 6648 kB public.factsets_certname_idx | 3104 kB public.factsets_pkey | 2208 kB public.idx_factsets_prod | 2208 kB public.factsets_id_seq | 8192 bytes (don't know what that is) We got this by running this: SELECT nspname || '.' || relname AS "relation", pg_size_pretty(pg_relation_size(C.oid)) AS "size" FROM pg_class C LEFT JOIN pg_namespace N ON (N.oid = C.relnamespace) WHERE nspname NOT IN ('pg_catalog', 'information_schema') AND relname LIKE '%' || 'factsets' || '%' ORDER BY pg_relation_size(C.oid) DESC;
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.413371.1629877927000.116288.1629893820027%40Atlassian.JIRA.
Jira (PUP-11196) puppet warns about BOM and US-ASCII encoding
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-11196 puppet warns about BOM and US-ASCII encoding Change By: Luchian Nemes Assignee: Luchian Nemes 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.409781.1628013472000.116300.1629895140033%40Atlassian.JIRA.
Jira (PDB-5252) Determine trigram index on facts size impact
Title: Message Title
Andrei Filipovici commented on PDB-5252
Re: Determine trigram index on facts size impact
After running the command ingestion benchmark, the sandbox grew to 25 GB. I run a vacuum full and the size got down to 22869mb / 23978720946 bytes. After creating the index on the operating system fact the sandbox size got to 22873mb / 23983677106 bytes. So it's a 4 mb size increase. Total indexes size on table factsets was 100 mb / 104816640 bytes. Individual index size was:
public.idx_factsets_jsonb_merged | 81 MB
public.factsets | 30 MB
public.factsets_hash_expr_idx| 6648 kB
public.factsets_operating_system_idx | 4840 kB
public.factsets_certname_idx | 3104 kB
public.idx_factsets_prod | 2208 kB
public.factsets_pkey | 2208 kB
public.factsets_id_seq | 8192 bytes
The command ingestion results:
Processing-seconds: {
"OneMinuteRate":309.6056417527956,
Jira (PUP-10859) Red Hat and CentOS 8.3 cannot install RPMs in FIPS mode
Title: Message Title Morgan Rhodes assigned an issue to Morgan Rhodes Puppet / PUP-10859 Red Hat and CentOS 8.3 cannot install RPMs in FIPS mode Change By: Morgan Rhodes Assignee: Morgan Rhodes 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.384622.1611426826000.116690.1629913440050%40Atlassian.JIRA.
Jira (PUP-10859) Red Hat and CentOS 8.3 cannot install RPMs in FIPS mode
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10859 Red Hat and CentOS 8.3 cannot install RPMs in FIPS mode Change By: Morgan Rhodes Team: Night's Watch Release Engineering 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.384622.1611426826000.116691.1629913500055%40Atlassian.JIRA.
Jira (PDB-5230) Add simple smoke tests for collected external queries
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5230 Add simple smoke tests for collected external queries Change By: Austin Blatt Sprint: HA 2021-08-25 , HAHA/Grooming 2 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.411384.1628624333000.116867.1629921960169%40Atlassian.JIRA.
Jira (PDB-5175) Update winston (PuppetDB 7.5.0)
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5175 Update winston (PuppetDB 7.5.0) Change By: Austin Blatt Sprint: HA 2021-07-14, HA 2021-07-28, HA 2021-08-11, HA 2021-08-25 , HAHA/Grooming 2 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.405259.162508137.116866.1629921960122%40Atlassian.JIRA.
Jira (PDB-5231) SPIKE - Investigate large structured facts using significant RAM
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5231 SPIKE - Investigate large structured facts using significant RAM Change By: Austin Blatt Sprint: HAHA/Grooming HA 2021-09-08 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.411475.1628712684000.116868.1629922200039%40Atlassian.JIRA.
Jira (FACT-3067) Facter API does not resolve custom facts that partial match legacy facts
Title: Message Title
Gheorghe Popescu created an issue
Facter / FACT-3067
Facter API does not resolve custom facts that partial match legacy facts
Issue Type:
Bug
Assignee:
Unassigned
Created:
2021/08/25 11:43 PM
Priority:
Normal
Reporter:
Gheorghe Popescu
Facter defines a couple of legacy facts using regexes, example networking: https://github.com/puppetlabs/facter/blob/main/lib/facter/facts/macosx/network_interfaces.rb#L6 Adding the following custom_fact:
Facter.add('network_nexthop_ip') do
setcode do
'custom_value'
end
end
{noformat}
*no* further _formatting_ is done here
Jira (FACT-3067) Facter API does not resolve custom facts that partial match legacy facts
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3067 Facter API does not resolve custom facts that partial match legacy facts Change By: Gheorghe Popescu Component/s: Facter 4 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.413521.1629960225000.117109.1629960300050%40Atlassian.JIRA.
Jira (FACT-3067) Facter API does not resolve custom facts that partial match legacy facts
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-3067
Facter API does not resolve custom facts that partial match legacy facts
Change By:
Gheorghe Popescu
This works on Facter 3.Facter defines a couple of legacy facts using regexes, example networking: https://github.com/puppetlabs/facter/blob/main/lib/facter/facts/macosx/network_interfaces.rb#L6Adding the following custom_fact:{code:ruby}Facter.add('network_nexthop_ip') do setcode do'custom_value' endend{noformat}*no* further _formatting_ is done here{noformat}{code}Will result in the fact being resolved on CLI but not when using Facter.value / Facter.fact{noformat}❯ bx facter network_nexthop_ip --custom-dir $custom_dir --debug[2021-08-26 09:41:40.066702 ] INFO Facter - executed with command line: network_nexthop_ip --custom-dir /Users/gheorghe.popescu/Workspace/custom_facts --debug[2021-08-26 09:41:40.066788 ] DEBUG Facter - Facter version: 4.2.4[2021-08-26 09:41:40.068471 ] DEBUG Facter::FactManager - Resolving facts sequentially[2021-08-26 09:41:40.069033 ] DEBUG Facter::FactLoader - Loading all internal facts[2021-08-26 09:41:40.069164 ] DEBUG Facter::FactLoader - Loading custom facts[2021-08-26 09:41:40.077111 ] DEBUG Facter::FactLoader - Loading external facts[2021-08-26 09:41:40.079167 ] DEBUG Facter::QueryParser - List of resolvable facts: [#, #][2021-08-26 09:41:40.079312 ] DEBUG Facter::Core::Execution::Posix - Executing command: ifconfig -a[2021-08-26 09:41:40.092197 ] DEBUG Facter::Core::Execution::Posix - Executing command: ipconfig getoption en0 server_identifier[2021-08-26 09:41:40.100080 ] DEBUG Facter::Core::Execution::Posix - Executing command: ipconfig getoption awdl0 server_identifier[2021-08-26 09:41:40.107701 ] DEBUG Facter::Core::Execution::Posix - Executing command: ipconfig getoption llw0 server_identifier[2021-08-26 09:41:40.118377 ] DEBUG Facter::Core::Execution::Posix - Executing command: route -n get default[2021-08-26 09:41:40.128626 ] DEBUG Facter::Util::Fact - custom fact network_nexthop_ip got resolved from: ["/Users/gheorghe.popescu/Workspace/custom_facts/ipaddress.rb", 25][2021-08-26 09:41:40.129107 ] DEBUG Facter::FactLoader - Loading all internal facts[2021-08-26 09:41:40.130886 ] DEBUG Facter::QueryParser - List of resolvable facts: [#][2021-08-26 09:41:40.131228 ] DEBUG Facter::FactManager - fact "network_lo0" has resolved to: 127.0.0.0[2021-08-26 09:41:40.131252 ] DEBUG Facter::FactManager - fact "network_en0" has resolved to: 192.168.100.0[2021-08-26 09:41:40.131264 ] DEBUG Facter::FactManager - fact "network_nexthop_ip" has resolved to: custom_value[2021-08-26 09:41:40.131390 ] DEBUG Facter::LegacyFactFormatter - Formatting for single user querycustom_value{noformat}{noformat}Facter.valuefroce_dot: false4.2.4D, [2021-08-26T09:43:09.389815 #44494] DEBUG -- : Facter::FactManager - Resolving facts sequentiallyD, [2021-08-26T09:43:09.389872 #44494] DEBUG -- : Facter::FactManager - resolving fact with user_query: network_nexthop_ipD, [2021-08-26T09:43:09.390443 #44494] DEBUG -
Jira (FACT-3067) Facter API does not resolve custom facts that partial match legacy facts
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-3067
Facter API does not resolve custom facts that partial match legacy facts
Change By:
Gheorghe Popescu
This works on Facter 3.Facter defines a couple of legacy facts using regexes, example networking: https://github.com/puppetlabs/facter/blob/main/lib/facter/facts/macosx/network_interfaces.rb#L6Adding the following custom_fact:{code:ruby}Facter.add('network_nexthop_ip') do setcode do'custom_value' endend{ noformat}*no* further _formatting_ is done here{noformat}{ code}Will result in the fact being resolved on CLI but not when using Facter.value / Facter.fact{noformat}❯ bx facter network_nexthop_ip --custom-dir $custom_dir --debug[2021-08-26 09:41:40.066702 ] INFO Facter - executed with command line: network_nexthop_ip --custom-dir /Users/gheorghe.popescu/Workspace/custom_facts --debug[2021-08-26 09:41:40.066788 ] DEBUG Facter - Facter version: 4.2.4[2021-08-26 09:41:40.068471 ] DEBUG Facter::FactManager - Resolving facts sequentially[2021-08-26 09:41:40.069033 ] DEBUG Facter::FactLoader - Loading all internal facts[2021-08-26 09:41:40.069164 ] DEBUG Facter::FactLoader - Loading custom facts[2021-08-26 09:41:40.077111 ] DEBUG Facter::FactLoader - Loading external facts[2021-08-26 09:41:40.079167 ] DEBUG Facter::QueryParser - List of resolvable facts: [#, #][2021-08-26 09:41:40.079312 ] DEBUG Facter::Core::Execution::Posix - Executing command: ifconfig -a[2021-08-26 09:41:40.092197 ] DEBUG Facter::Core::Execution::Posix - Executing command: ipconfig getoption en0 server_identifier[2021-08-26 09:41:40.100080 ] DEBUG Facter::Core::Execution::Posix - Executing command: ipconfig getoption awdl0 server_identifier[2021-08-26 09:41:40.107701 ] DEBUG Facter::Core::Execution::Posix - Executing command: ipconfig getoption llw0 server_identifier[2021-08-26 09:41:40.118377 ] DEBUG Facter::Core::Execution::Posix - Executing command: route -n get default[2021-08-26 09:41:40.128626 ] DEBUG Facter::Util::Fact - custom fact network_nexthop_ip got resolved from: ["/Users/gheorghe.popescu/Workspace/custom_facts/ipaddress.rb", 25][2021-08-26 09:41:40.129107 ] DEBUG Facter::FactLoader - Loading all internal facts[2021-08-26 09:41:40.130886 ] DEBUG Facter::QueryParser - List of resolvable facts: [#][2021-08-26 09:41:40.131228 ] DEBUG Facter::FactManager - fact "network_lo0" has resolved to: 127.0.0.0[2021-08-26 09:41:40.131252 ] DEBUG Facter::FactManager - fact "network_en0" has resolved to: 192.168.100.0[2021-08-26 09:41:40.131264 ] DEBUG Facter::FactManager - fact "network_nexthop_ip" has resolved to: custom_value[2021-08-26 09:41:40.131390 ] DEBUG Facter::LegacyFactFormatter - Formatting for single user querycustom_value{noformat}{noformat}Facter.valuefroce_dot: false4.2.4D, [2021-08-26T09:43:09.389815 #44494] DEBUG -- : Facter::FactManager - Resolving facts sequentiallyD, [2021-08-26T09:43:09.389872 #44494] DEBUG -- : Facter::FactManager - resolving fact with user_query: network_nexthop_ipD, [2021-08-26T09:43:09.390443 #44494] DEBUG -
Jira (FACT-3067) Facter API does not resolve custom facts that partial match legacy facts
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3067 Facter API does not resolve custom facts that partial match legacy facts Change By: Gheorghe Popescu Team: Night's Watch 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.413521.1629960225000.117112.1629960360113%40Atlassian.JIRA.
Jira (PDB-5204) Perform diff on the locust results
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea PuppetDB / PDB-5204 Perform diff on the locust results Change By: Sebastian Miclea Assignee: Sebastian Miclea 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.408407.1627050042000.117116.1629960900040%40Atlassian.JIRA.
