Jira (PUP-11210) package resource, allow for logging with Windows MSI
Title: Message Title Josh Cooper commented on PUP-11210 Re: package resource, allow for logging with Windows MSI Try passing them as an array of strings, [“l*v”, “C:\…”] 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.412741.1629402282000.112643.1629419400066%40Atlassian.JIRA.
Jira (PUP-11211) Deprecate run stages
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11211 Deprecate run stages Change By: Josh Cooper Fix Version/s: PUP 8.0.0 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.412778.1629411139000.112560.1629411360240%40Atlassian.JIRA.
Jira (PUP-11212) Remove run stages
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11212 Remove run stages Change By: Josh Cooper Fix Version/s: PUP 8.0.0 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.412779.1629411239000.112559.1629411360197%40Atlassian.JIRA.
Jira (PUP-11212) Remove run stages
Title: Message Title Josh Cooper created an issue Puppet / PUP-11212 Remove run stages Issue Type: Task Assignee: Unassigned Created: 2021/08/19 3:13 PM Priority: Normal Reporter: Josh Cooper This ticket is to remove the stage type and metaparameter, which were deprecated PUP-11211 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11211) Deprecate run stages
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11211 Deprecate run stages Change By: Josh Cooper Fix Version/s: PUP 8.0.0 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.412778.1629411139000.112558.1629411300101%40Atlassian.JIRA.
Jira (PUP-11211) Deprecate run stages
Title: Message Title Josh Cooper created an issue Puppet / PUP-11211 Deprecate run stages Issue Type: Task Assignee: Unassigned Created: 2021/08/19 3:12 PM Priority: Normal Reporter: Josh Cooper Run stages were implemented prior to the contain feature being added and have a number of limitations described in https://puppet.com/docs/puppet/6/lang_run_stages.html#lang_run_stages-stages-limitations I'm under the impression that everything that could be accomplished via run stages can now be accomplished by a class that contain's whatever classes were in the stage, but do so without any of the limitations above. This ticket is to deprecate the use of the stage type and metaparameter in the 6.x and 7.x streams. I'll file a separate ticket for removal in 8. See PUP-893 and commit ce522281f3ecf7681e07fc9808d48eee3422fdf1 for how we deprecated the audit metaparameter when it appeared in a manifest. Add Comment
Jira (PUP-11210) package resource, allow for logging with Windows MSI
Title: Message Title
Michael Luck updated an issue
Puppet / PUP-11210
package resource, allow for logging with Windows MSI
Change By:
Michael Luck
*Puppet Version: 6.23* *Puppet Server Version: 6.16.1* *OS Name/Version: Windows 10* I'm not able to specify logging options when using the package resource with Windows MSIs. When trying to pass the log parameter, it does not work since Puppet places quotes around it. {code:java}install_options => [ '/ qn', '/norestart', '/ l*v c:\windows\temp\msi_log.txt' ],{code} This results in:{code:java}msiexec /qn /norestart /i C:\package.msi /qn /norestart "/l*v c:\windows\temp\msi_log.txt"{code}Is there a way I can override this behavior to pass the parameter correctly?
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
Jira (PUP-11210) package resource, allow for logging with Windows MSI
Title: Message Title
Michael Luck updated an issue
Puppet / PUP-11210
package resource, allow for logging with Windows MSI
Change By:
Michael Luck
*Puppet Version: 6.23* *Puppet Server Version: 6.16.1* *OS Name/Version: Windows 10* I'm not able to specify logging options when using the package resource with Windows MSIs. When trying to pass the log parameter, it does not work since Puppet places quotes around it. {code:java} install_options => [ '/qn', '/norestart', '/l*v c:\windows\temp\msi_log.txt' ],{code} This results in:{code:java} msiexec /qn /norestart /i C:\ package.msi /qn /norestart "/l*v c:\windows\temp\msi_log.txt"{code}Is there a way I can override this behavior to pass the parameter correctly?
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
Jira (PUP-11210) package resource, allow for logging with Windows MSI
Title: Message Title
Michael Luck updated an issue
Puppet / PUP-11210
package resource, allow for logging with Windows MSI
Change By:
Michael Luck
*Puppet Version: 6.23* *Puppet Server Version: 6.16.1* *OS Name/Version: Windows 10* I'm not able to specify logging options when using the package resource with Windows MSIs. When trying to pass the log parameter, it does not work since Puppet places quotes around it. {code:java} ``` install_options => [ '/qn', '/norestart','/l*v c:\windows\temp\msi_log.txt' ], {code} ``` This results in ` :{code:java} msiexec /qn /norestart /i package.msi "/l*v c:\windows\temp\msi_log.txt" ` which is invalid. {code} Is there a way I can override this behavior to pass the parameter correctly?
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
Jira (PUP-11210) package resource, allow for logging with Windows MSI
Title: Message Title Michael Luck created an issue Puppet / PUP-11210 package resource, allow for logging with Windows MSI Issue Type: Bug Assignee: Unassigned Components: Windows Created: 2021/08/19 12:44 PM Priority: Low Reporter: Michael Luck Puppet Version: 6.23 Puppet Server Version: 6.16.1 OS Name/Version: Windows 10 I'm not able to specify logging options when using the package resource with Windows MSIs. When trying to pass the log parameter, it does not work since Puppet places quotes around it. ``` install_options => [ '/qn', '/norestart', '/l*v c:\windows\temp\msi_log.txt' ], ``` This results in `msiexec /qn /norestart /i package.msi "/l*v c:\windows\temp\msi_log.txt"` which is invalid. Is there a way I can override this behavior to pass the parameter correctly? Add Comment
Jira (PDB-5184) Add Estate Reporting queries to performance test
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5184 Add Estate Reporting queries to performance test Change By: Austin Blatt Fix Version/s: PDB n/a 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.405177.1625035211000.112325.1629396000329%40Atlassian.JIRA.
Jira (PDB-5130) Adjust the updatetime.sql script to handle partitions
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5130 Adjust the updatetime.sql script to handle partitions Change By: Austin Blatt Fix Version/s: PDB n/a 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.399615.1621018567000.112323.1629396000240%40Atlassian.JIRA.
Jira (PDB-5159) Change filenames from PDB export to be compatible with stockpile
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5159 Change filenames from PDB export to be compatible with stockpile Change By: Austin Blatt Fix Version/s: PDB n/a 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.403562.1623830393000.112324.1629396000285%40Atlassian.JIRA.
Jira (PDB-5168) Log PQL parsing time whenever it's "too long"
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5168 Log PQL parsing time whenever it's "too long" Change By: Austin Blatt Fix Version/s: PDB 7.5.2 Fix Version/s: PDB 6.18.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.405225.1625077799000.112322.1629396000193%40Atlassian.JIRA.
Jira (PDB-5114) Don't validate every query row returned against the schema
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5114 Don't validate every query row returned against the schema Change By: Austin Blatt Fix Version/s: PDB 7.5.1 Fix Version/s: PDB 6.18.1 Fix Version/s: PDB 7.5.2 Fix Version/s: PDB 6.18.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
Jira (PDB-5214) (Re)allow dotted projections with group_by
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5214 (Re)allow dotted projections with group_by Change By: Austin Blatt Fix Version/s: PDB 7.5.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.408826.1627489296000.112317.1629395820054%40Atlassian.JIRA.
Jira (PDB-5214) (Re)allow dotted projections with group_by
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5214 (Re)allow dotted projections with group_by Change By: Austin Blatt Fix Version/s: PDB 6.18.1 Fix Version/s: PDB 6.18.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.408826.1627489296000.112318.1629395820110%40Atlassian.JIRA.
Jira (PDB-5161) Specify and fully validate dotted projections
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5161 Specify and fully validate dotted projections Change By: Austin Blatt Fix Version/s: PDB 6.18.1 Fix Version/s: PDB 7.5.2 Fix Version/s: PDB 6.18.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.403713.1623862346000.112319.1629395820157%40Atlassian.JIRA.
Jira (PDB-5226) Dotted fact path group by doesn't group
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5226 Dotted fact path group by doesn't group Change By: Austin Blatt Fix Version/s: PDB 7.5.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.409525.1627947342000.112316.1629395760082%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Josh Cooper commented on FACT-3039 Re: Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 It feels weird that Puppet has a Fact indirector, but doesn't use it everywhere Yep very true. We made some progress during Facter 3 development to eliminate places where we were calling facter directly, such as https://github.com/puppetlabs/puppet/commit/f41800ab4c0a928ff4f38ad5d1f6bd1e2b5619cd. But there are still places where we need to access facter while bootstrapping puppet, such as resolving the certname -> fqdn. Also puppetserver wants the ability to load puppet without loading facter, see PUP-9686. One idea is to allow a caller to register a facter implementation, similar to how callers (like puppetserver) register an http client implementation today: facter_impl = FacterTestImpl.new Puppet.initialize_settings([], true, true, http: ..., facter: facter_impl) where FacterTestImpl implements the Facter API but always returns a canned set of values. Then modify puppet so that all calls to Facter go through the runtime: Puppet.runtime[:facter].get(:osversion) Then something like rspec-puppet-facts could register the test facter implementation based on facts in facterdb? Add Comment
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Ewoud Kohl van Wijngaarden commented on FACT-3039 Re: Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Right, I missed that since it's a fairly long discussion by now. It feels weird that Puppet has a Fact indirector, but doesn't use it everywhere. I can also appreciate that a change in Puppet itself doesn't immediately solve it since we always want to be able to test on multiple versions. We should be careful though. People do call Facter.value in their custom fact tests. Perhaps we should add first class custom fact support to rspec-puppet to provide a sane alternative. Perhaps even with let(:facts) support. 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.112029.1629381540026%40Atlassian.JIRA.
Jira (PUP-10859) Red Hat and CentOS 8.3 cannot install RPMs in FIPS mode
Title: Message Title Liz Nemsick commented on PUP-10859 Re: Red Hat and CentOS 8.3 cannot install RPMs in FIPS mode Is there a timeframe to address this issue? 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.112009.1629380280034%40Atlassian.JIRA.
Jira (PUP-6708) Agent does not save local copy of last_run_report.yaml if submission to report server fails
Title: Message Title Gabriel Nagy commented on PUP-6708 Re: Agent does not save local copy of last_run_report.yaml if submission to report server fails Merged to 6.x in https://github.com/puppetlabs/puppet/commit/6b109de27fe2861e1b21e9e36f708de387c2ac6c 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.152161.1473975634000.111991.1629377640029%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu commented on FACT-3039 Re: Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 I think the issue here is caused by direct calls to `Facter.value` which are made in compiler.rb and in the providers. So Puppet calls Facter API directly. As Josh Cooper suggested here, there is the :memory indirector that can be used for facts but this is not for `Facter.value` calls. 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.111969.1629374940028%40Atlassian.JIRA.
Jira (PUP-11208) Puppet fails to install packages on Solaris if another pkg install is running
Title: Message Title Gabriel Nagy created an issue Puppet / PUP-11208 Puppet fails to install packages on Solaris if another pkg install is running Issue Type: Bug Assignee: Unassigned Created: 2021/08/19 4:17 AM Priority: Normal Reporter: Gabriel Nagy Puppet fails hard if it tries to install a package on Solaris 11 while a pkg install command is already running in the background. pkg install fails with the following error: root@initial-holdup:~# pkg install nano pkg: The image cannot be modified as it is currently in use by another package client. root@initial-holdup:~# echo $? 7 The same error can be reproduced in a zone set up, if you execute pkg install something concurrently on global and the zone (the following output is from a puppet manifest with the nano package resource):
Jira (FACT-3065) submit facts for new facter releases to facterdb
Title: Message Title Tim Meusel created an issue Facter / FACT-3065 submit facts for new facter releases to facterdb Issue Type: Task Assignee: Unassigned Created: 2021/08/19 4:15 AM Priority: Normal Reporter: Tim Meusel Hi, https://github.com/voxpupuli/facterdb is used for unit tests in basically every module. It currently relies on community contributions for new mocked facts on each facter release. Could you consider providing them on a new facter release? That would resolve a lot of issues. facterdb does a fallback to older factsets if the correct version isn't available, so sometimes tests are executed with older fact sets which lead to false/positive errors. Add Comment This message was sent
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Ewoud Kohl van Wijngaarden commented on FACT-3039 Re: Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Would it make sense to make hooks in Puppet itself to say "use these as facts" and bypass Facter altogether? Perhaps as a fact indirector? It may need to be disabled for real fact testing, but on the other hand: that directly uses Facter APIs, not Puppet. So then we would need to modify rspec-puppet to set a fact indirector in catalog compilation. 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.111938.1629365040027%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu commented on FACT-3039 Re: Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Given that when running tests with rspec-puppet/rspec-puppet-facts/facterdb the system facts should not matter(should not be resolved), I suggest moving on with monkey patching Facter 4 to not call the resolvers in the context of running specs. This will ensure that Facter 4 does not try to resolve facts for the current system when running modules unit tests(eg. platform specific catalog compilation) 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.111914.1629363060103%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3039 Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Change By: Gheorghe Popescu Attachment: facter4_exec_api.html 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.111883.1629362100248%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu commented on FACT-3039 Re: Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Running without a dummy Facter::Core::Execution.execute: Thread: 2160, Fiber: 2140 (100.00% ~ 0.016681278008036315) facter4_no_exec.html 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.111859.1629361500099%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3039 Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Change By: Gheorghe Popescu Attachment: screenshot-1.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.380977.1608048829000.111858.1629361500047%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3039 Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Change By: Gheorghe Popescu Attachment: facter4_no_exec.html 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.111857.1629361440037%40Atlassian.JIRA.
Jira (PDB-5203) Script that runs the pdb benchmark tests
Title: Message Title Sebastian Miclea updated an issue PuppetDB / PDB-5203 Script that runs the pdb benchmark tests Change By: Sebastian Miclea The script does: - if a commit SHA is given as a parameter, than it checkouts to that and holds the SHA in a variable, needed to name the results folder. If no SHA is given, it pulls the latest changes from the 6.x branch and copies in a variable the latest commit SHA. - In the locust results folder, create a folder with -. - inside this folder create -another two named ingestion-ON and- ingestion-OFF - inside the two folders create folders -1000, 10.000,- 100.000 and -500.000- - start pdb - after pdb started, run locust in the needed results folders (the --csv parameter accepts folder paths) with all queries, with a warmup with one user, another one with -1 user, 10- -users- and 20 users. - -go to n1 server and start the benchmark with (30 min run interval, 30% data change) and the appropriate number of hosts, depending on the sandbox that's used.- - -go to the ingestion results folder and start locust again with the same settings.- - -kill the benchmark after locust is done.- - kill pdb. - inside the results folder delete the delete all files except the .html, _stats.csv and _failures.csv (not sure if we need those). Also the warmup files must be deleted. - Check the _failures.csv files, and if they are empty, delete them.-!!! For the 500.000 sandbox you need to change the main sandboxes path.- Add Comment This message was sent by Atlassian Jira
Jira (FACT-3063) Facter unable to get processor speed on macOS 11 arm64 which causes the resolver to blow up
Title: Message Title Gabriel Nagy updated an issue Facter / FACT-3063 Facter unable to get processor speed on macOS 11 arm64 which causes the resolver to blow up Change By: Gabriel Nagy Summary: Facter unable to get processor speed on OS macOS 11 arm64 which causes the resolver to blow up 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.409868.1628076333000.111841.1629356220032%40Atlassian.JIRA.
