Jira (FACT-2797) Facter -v has to print the version and the commit SHA of that version
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2797 Facter -v has to print the version and the commit SHA of that version Change By: Oana Tanasoiu Assignee: Oana Tanasoiu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371823.1600157075000.43017.1601012460038%40Atlassian.JIRA.
Jira (PDB-4903) Set a lock_timeout for gc partition drops
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4903 Set a lock_timeout for gc partition drops Change By: Rob Browning This may well be obviated by future work to allow the gc to kick out other queries, but for now, just make sure we don't wait indefinitely for the exclusive lock we need when dropping a partition.While we're waiting, all other queries that touch the "parent" table will be blocked, which may be able to quickly block all command processing threads, queries, etc., for the duration. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.373096.1600987362000.42833.1600988100133%40Atlassian.JIRA.
Jira (PDB-4903) Set a lock_timeout for gc partition drops
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4903 Set a lock_timeout for gc partition drops Issue Type: Improvement Assignee: Rob Browning Created: 2020/09/24 3:42 PM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (PDB-4902) Handle resource event purges in one pass when possible
Title: Message Title Rob Browning moved an issue PuppetDB / PDB-4902 Handle resource event purges in one pass when possible Change By: Rob Browning Key: PE PDB - 30156 4902 Project: Puppet Enterprise [Internal] PuppetDB Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.373095.1600987225000.42804.1600987320079%40Atlassian.JIRA.
Jira (PDB-4901) Only gc the oldest report/event partition in the normal case
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4901 Only gc the oldest report/event partition in the normal case Issue Type: Improvement Assignee: Rob Browning Created: 2020/09/24 3:35 PM Priority: Normal Reporter: Rob Browning Only drop the oldest report or events partition during the normal, periodic gc, when there's more than one candidate. This is intended to decrease the length of time we might block pdb operations since with the current arrangement, the drop will attempt to acquire an exclusive lock on the entire table (i.e. reports, not just the partition), and so will block all subsequent access to that table, until it finishes. Add Comment This message was sent by
Jira (PUP-7582) Make attempt to export or virtualize a class an error
Title: Message Title Ben Ford commented on PUP-7582 Re: Make attempt to export or virtualize a class an error I said this in slack some time ago, but I should record it on the ticket. Kill it dead. The more hidden "actually, it's not doing what you think you're doing" gotchas we can eliminate, the better. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.19.1495458026000.42092.1600964520086%40Atlassian.JIRA.
Jira (FACT-2798) Check Facter.info, Facter.log_exception and set color option default to true
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2798 Check Facter.info, Facter.log_exception and set color option default to true Change By: Andrei Filipovici Check if Facter.log_exception on Facter 3 prints empty and nil messages. If it does then remove the first message checks in logger for this methods.Facter 3 prints by default colorised log messages. Change de color option default in Facter 4 to true.Changing color to true , breaks facter on Centos 6. Colored messages are disabled on Windows. Activate them. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371835.1600163096000.42087.1600963380030%40Atlassian.JIRA.
Jira (FACT-2798) Check Facter.info, Facter.log_exception and set color option default to true
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2798 Check Facter.info, Facter.log_exception and set color option default to true Change By: Andrei Filipovici Check if Facter. info and Facter. log_exception on Facter 3 prints empty and nil messages. If it does then remove the first message checks in logger for this methods. Facter 3 prints by default colorised log messages. Change de color option default in Facter 4 to true. Changing color to true breaks facter on Centos 6. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371835.1600163096000.42086.1600963260035%40Atlassian.JIRA.
Jira (FACT-2813) Show backtrace in CI for acceptance test errors
Title: Message Title
Andrei Filipovici updated an issue
Facter / FACT-2813
Show backtrace in CI for acceptance test errors
Change By:
Andrei Filipovici
Check if backtrace is shows shown in GithuHub failed GitHub actions acceptance test and in Jenkins acceptance test tests . If the backtrace is printed only partially, print it all. Example from a failed Jenkins test: 08:37:53 system_uptime => {08:37:53 days => 0,08:37:53 hours => 2,08:37:53 seconds => 9676,08:37:53 uptime => "2:41 hours"08:37:53 }08:37:53 timezone => UTC08:37:53 virtual => vmware08:37:53 08:37:53 akin-complement.delivery.puppetlabs.net (akin-complement.delivery.puppetlabs.net) executed in 0.60 seconds08:37:53 Minitest::Assertion: Expected no errors from facter when run as user nonroot.08:37:53 Expected "[2020-09-18 05:37:53.249985 ] ERROR Facter::InternalFactManager - \e[31mPermission denied @ dir_initialize - /var/lib/NetworkManager\e[0m\n " to be empty.08:37:53 /tmp/jenkins/workspace/platform_puppet-agent_puppet-agent-integration-suite_daily-main/RMM_COMPONENT_TO_TEST_NAME/facter/SLAVE_LABEL/beaker/TEST_TARGET/fedora32-64a/acceptance/.bundle/gems/ruby/2.5.0/gems/minitest-5.14.2/lib/minitest/assertions.rb:18308:37:53 /tmp/jenkins/workspace/platform_puppet-agent_puppet-agent-integration-suite_daily-main/RMM_COMPONENT_TO_TEST_NAME/facter/SLAVE_LABEL/beaker/TEST_TARGET/fedora32-64a/acceptance/.bundle/gems/ruby/2.5.0/gems/minitest-5.14.2/lib/minitest/assertions.rb:19808:37:53 /tmp/jenkins/workspace/platform_puppet-agent_puppet-agent-integration-suite_daily-main/RMM_COMPONENT_TO_TEST_NAME/facter/SLAVE_LABEL/beaker/TEST_TARGET/fedora32-64a/acceptance/tests/facts/non_root_users_without_errors.rb:2808:37:53 /tmp/jenkins/workspace/platform_puppet-agent_puppet-agent-integration-suite_daily-main/RMM_COMPONENT_TO_TEST_NAME/facter/SLAVE_LABEL/beaker/TEST_TARGET/fedora32-64a/acceptance/.bundle/gems/ruby/2.5.0/gems/beaker-4.27.0/lib/beaker/dsl/helpers/host_helpers.rb:9308:37:53 /tmp/jenkins/workspace/platform_puppet-agent_puppet-agent-integration-suite_daily-main/RMM_COMPONENT_TO_TEST_NAME/facter/SLAVE_LABEL/beaker/TEST_TARGET/fedora32-64a/acceptance/.bundle/gems/ruby/2.5.0/gems/beaker-4.27.0/lib/beaker/shared/host_manager.rb:13008:37:53 /tmp/jenkins/workspace/platform_puppet-agent_puppet-agent-integration-suite_daily-main/RMM_COMPONENT_TO_TEST_NAME/facter/SLAVE_LABEL/beaker/TEST_TARGET/fedora32-64a/acceptance/.bundle/gems/ruby/2.5.0/gems/beaker-4.27.0/lib/beaker/dsl/patterns.rb:3708:37:53 /tmp/jenkins/workspace/platform_puppet-agent_puppet-agent-integration-suite_daily-main/RMM_COMPONENT_TO_TEST_NAME/facter/SLAVE_LABEL/beaker/TEST_TARGET/fedora32-64a/acceptance/.bundle/gems/ruby/2.5.0/gems/beaker-4.27.0/lib/beaker/dsl/helpers/host_helpers.rb:6308:37:53
Jira (FACT-2815) Timing on cached facts is inconsistent, sometime it is displayed, others it is not
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2815 Timing on cached facts is inconsistent, sometime it is displayed, others it is not Issue Type: Bug Assignee: Unassigned Created: 2020/09/24 8:45 AM Priority: Normal Reporter: Bogdan Irimie Cached facts timing is inconsistently displayedWhen running facter with `-t` option. Acceptance criteria: facter should display timing information even for cached facts Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2814) Investigate if we can run some module tests in our CI
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2814 Investigate if we can run some module tests in our CI Issue Type: Task Assignee: Unassigned Created: 2020/09/24 8:38 AM Priority: Normal Reporter: Bogdan Irimie In order to improve the confidence in our changes, we could run some module tests. This would help the IAC team as well, as we will brake them less often. Acceptance criteria: determine the feasibility of running module test in Github Actions or Jenkins. Add Comment This message was sent by
Jira (FACT-2813) Show backtrace in CI for acceptance test errors
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2813 Show backtrace in CI for acceptance test errors Issue Type: Task Assignee: Unassigned Created: 2020/09/24 8:31 AM Priority: Normal Reporter: Bogdan Irimie Check if backtrace is shows in GithuHub actions acceptance test and in Jenkins acceptance test. If the backtrace is printed only partially, print it all. Acceptance criteria: backtrace is printed in all acceptance CI jobs. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10622) Segmentation fault on start whith high-entropy ASLR
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-10622 Segmentation fault on start whith high-entropy ASLR Change By: Gabriel Nagy Assignee: Gabriel Nagy Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.369265.1597654705000.41997.1600955400026%40Atlassian.JIRA.
Jira (PUP-10658) Puppet service ps parsing using too loose regex
Title: Message Title Gabriel Nagy commented on PUP-10658 Re: Puppet service ps parsing using too loose regex Hi Tim Meusel, I investigated this issue a bit more and I was in favor of it initially. However, I think it's a bit of a grey area. The code involving getpid is quite primitive, and the fix is not as simple as enclosing the service name between ^ and $. Since we're parsing the output of ps -ef, processes can show up in a variety of ways. Here are some EL 6 examples: Service: abrtd ps output: root 6509 1 0 09:35 ? 00:00:00 /usr/sbin/abrtd Service: syslog ps output: root 1671 1 0 09:35 ? 00:00:00 /sbin/rsyslogd -i /var/run/syslogd.pid -c 5 Service: rpcbind ps output: rpc 1723 1 0 09:35 ? 00:00:00 rpcbind I think messing with the check by trying to more closely match the process name could open up a whole can of worms (some processes have arguments, others run under an absolute path). I agree that the current behavior is a bit counterintuitive, but it does work the way it's documented: As a last resort, Puppet will attempt to search the process table by calling whatever command is listed in the `ps` fact. The default search pattern is the name of the service, but you can specify it with the `pattern` attribute. https://puppet.com/docs/puppet/6.18/types/service.html#service-description Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To
Jira (PUP-7791) No useful debug output for yum/rpm provider success/failure/version information
Title: Message Title Ciprian Badescu assigned an issue to Ciprian Badescu Puppet / PUP-7791 No useful debug output for yum/rpm provider success/failure/version information Change By: Ciprian Badescu Assignee: Ciprian Badescu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.201571.150057424.41972.1600947960041%40Atlassian.JIRA.
Jira (FACT-2792) Implement facter -p
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2792 Implement facter -p Change By: Bogdan Irimie Assignee: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371407.1599655654000.41891.160092937%40Atlassian.JIRA.
