Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2880 facter 4 differing output from facter 3 for service_provider fact Change By: Bogdan Irimie Sprint: ready for triage ghost-2.12 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.379364.1606744776000.89327.1606895820027%40Atlassian.JIRA.
Jira (FACT-2859) [regression] External facts are loaded when using puppet lookup for a different node
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2859 [regression] External facts are loaded when using puppet lookup for a different node Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12, ready for triage ghost- 2 .12 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.378374.1605310876000.89324.1606895580031%40Atlassian.JIRA.
Jira (FACT-2843) scope6 fact should be per binding not per interface
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2843 scope6 fact should be per binding not per interface Change By: Bogdan Irimie Sprint: ghost-28.10, ghost-4.11, ghost-11.11, ghost 25.11, ghost-2.12, ready for triage ghost- 2 .12 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.375310.1603200299000.89323.1606895460192%40Atlassian.JIRA.
Jira (FACT-2871) Regression: interfaces without an ipaddress assigned are not anymore reported
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2871 Regression: interfaces without an ipaddress assigned are not anymore reported Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12, ready for triage ghost- 2 .12 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.379055.160591045.89317.1606895100041%40Atlassian.JIRA.
Jira (FACT-2869) Puppet 7.0.0 facter changes is_virtual fact to string (from boolean)
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2869 Puppet 7.0.0 facter changes is_virtual fact to string (from boolean) Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12, ready for triage ghost- 2 .12 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.378976.160585180.89318.1606895100088%40Atlassian.JIRA.
Jira (FACT-2872) Regressions: secondary interfaces are not anymore reported
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2872 Regressions: secondary interfaces are not anymore reported Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12, ready for triage ghost- 2 .12 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.379058.1605915439000.89316.1606895040025%40Atlassian.JIRA.
Jira (FACT-2874) facter 4.0.46 should load external fact files in lexicographical order
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2874 facter 4.0.46 should load external fact files in lexicographical order Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12, ready for triage ghost- 2 .12 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.379132.1606176297000.89315.1606894980035%40Atlassian.JIRA.
Jira (FACT-2881) puppet 7 treats nonexistent fact differently compared to puppet 6?
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2881 puppet 7 treats nonexistent fact differently compared to puppet 6? Change By: Bogdan Irimie Sprint: ghost-2.12, ready for triage ghost- 2 .12 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.379177.1606234679000.89314.1606894920030%40Atlassian.JIRA.
Jira (FACT-2872) Regressions: secondary interfaces are not anymore reported
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2872 Regressions: secondary interfaces are not anymore reported Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12 , ready for triage 2 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.379058.1605915439000.89311.1606894800820%40Atlassian.JIRA.
Jira (FACT-2847) Facter 4 breaks rspec on fact test
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2847 Facter 4 breaks rspec on fact test Change By: Bogdan Irimie Sprint: ghost-4.11, ghost-11.11, ghost 25.11, ghost-2.12 , ready for triage 2 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.376201.1603820546000.89307.1606894800644%40Atlassian.JIRA.
Jira (FACT-2843) scope6 fact should be per binding not per interface
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2843 scope6 fact should be per binding not per interface Change By: Bogdan Irimie Sprint: ghost-28.10, ghost-4.11, ghost-11.11, ghost 25.11, ghost-2.12 , ready for triage 2 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.375310.1603200299000.89302.1606894800463%40Atlassian.JIRA.
Jira (FACT-2868) Release Facter 4.0.47
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2868 Release Facter 4.0.47 Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12 , ready for triage 2 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.378788.1605708911000.89308.1606894800687%40Atlassian.JIRA.
Jira (FACT-2869) Puppet 7.0.0 facter changes is_virtual fact to string (from boolean)
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2869 Puppet 7.0.0 facter changes is_virtual fact to string (from boolean) Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12 , ready for triage 2 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.378976.160585180.89309.1606894800732%40Atlassian.JIRA.
Jira (FACT-2849) Move all components from LegacyFacter module to Facter module
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2849 Move all components from LegacyFacter module to Facter module Change By: Bogdan Irimie Sprint: ghost-11.11, ghost 25.11, ghost-2.12 , ready for triage 2 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.377145.1604500209000.89297.1606894800243%40Atlassian.JIRA.
Jira (FACT-2874) facter 4.0.46 should load external fact files in lexicographical order
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2874 facter 4.0.46 should load external fact files in lexicographical order Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12 , ready for triage 2 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.379132.1606176297000.89312.1606894800864%40Atlassian.JIRA.
Jira (FACT-2705) Blog post for Facter 4
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2705 Blog post for Facter 4 Change By: Bogdan Irimie Sprint: ghost-14.10, ghost-21.10, ghost-28.10, ghost-4.11, ghost-11.11, ghost 25.11, ghost-2.12 , ready for triage 2 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.365211.1594212543000.89303.1606894800507%40Atlassian.JIRA.
Jira (FACT-2881) puppet 7 treats nonexistent fact differently compared to puppet 6?
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2881 puppet 7 treats nonexistent fact differently compared to puppet 6? Change By: Bogdan Irimie Sprint: ghost-2.12 , ready for triage 2 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.379177.1606234679000.89313.1606894800907%40Atlassian.JIRA.
Jira (FACT-2848) Improve performance of cache manager
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2848 Improve performance of cache manager Change By: Bogdan Irimie Sprint: ghost-4.11, ghost-11.11, ghost 25.11, ghost-2.12 , ready for triage 2 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.376315.160389490.89300.1606894800375%40Atlassian.JIRA.
Jira (FACT-2813) Show backtrace in CI for acceptance test errors
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2813 Show backtrace in CI for acceptance test errors Change By: Bogdan Irimie Sprint: ghost-7.10, ghost-14.10, ghost-21.10, ghost-28.10, ghost-4.11, ghost-11.11, ghost 25.11, ghost-2.12 , ready for triage 2 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.372970.1600961477000.89305.1606894800596%40Atlassian.JIRA.
Jira (FACT-2871) Regression: interfaces without an ipaddress assigned are not anymore reported
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2871 Regression: interfaces without an ipaddress assigned are not anymore reported Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12 , ready for triage 2 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.379055.160591045.89310.1606894800776%40Atlassian.JIRA.
Jira (FACT-2833) Investigate performance for hypervisor fact
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2833 Investigate performance for hypervisor fact Change By: Bogdan Irimie Sprint: ghost-14.10, ghost-21.10, ghost-28.10, ghost-4.11, ghost-11.11, ghost 25.11, ghost-2.12 , ready for triage 2 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.374205.1602078248000.89304.1606894800552%40Atlassian.JIRA.
Jira (FACT-1986) Test C++ Facter with custom facts
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1986 Test C++ Facter with custom facts Change By: Bogdan Irimie Sprint: ghost-11.11, ghost 25.11, ghost-2.12 , ready for triage 2 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.320311.1565329873000.89298.1606894800288%40Atlassian.JIRA.
Jira (FACT-2838) Some facts are volatile (changes almost every fact upload)
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2838 Some facts are volatile (changes almost every fact upload) Change By: Bogdan Irimie Sprint: ghost-28.10, ghost-4.11, ghost-11.11, ghost 25.11, ghost-2.12 , ready for triage 2 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.375143.160283799.89301.1606894800420%40Atlassian.JIRA.
Jira (FACT-2846) Facter 4 fails to parse linux tun* interfaces on our openvpn server
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2846 Facter 4 fails to parse linux tun* interfaces on our openvpn server Change By: Bogdan Irimie Sprint: ghost-28.10, ghost-4.11, ghost-11.11, ghost 25.11, ghost-2.12 , ready for triage 2 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.375629.1603354499000.89306.1606894800601%40Atlassian.JIRA.
Jira (FACT-2400) Resolvers are not structured consistently
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2400 Resolvers are not structured consistently Change By: Bogdan Irimie Sprint: ghost-11.11, ghost 25.11, ghost-2.12 , ready for triage 2 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.347476.1582641357000.89299.1606894800331%40Atlassian.JIRA.
Jira (FACT-2558) Fact classes that resolve more than one fact should be split
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2558 Fact classes that resolve more than one fact should be split Change By: Bogdan Irimie Sprint: ghost-11.11, ghost 25.11, ghost-2.12 , ready for triage 2 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.355608.1586935915000.89296.1606894800199%40Atlassian.JIRA.
Jira (FACT-2421) Break Facter API in different modules
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2421 Break Facter API in different modules Change By: Bogdan Irimie Sprint: ghost-11.11, ghost 25.11, ghost-2.12 , ready for triage 2 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.347908.1582886415000.89295.1606894740383%40Atlassian.JIRA.
Jira (FACT-2306) Add support for AWS IMDSv2
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2306 Add support for AWS IMDSv2 Change By: Bogdan Irimie Sprint: ghost-11.11, ghost 25.11, ghost-2.12 , ready for triage 2 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.342859.1579626792000.89294.1606894740328%40Atlassian.JIRA.
Jira (FACT-2859) [regression] External facts are loaded when using puppet lookup for a different node
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2859 [regression] External facts are loaded when using puppet lookup for a different node Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12 , ready for triage 2 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.378374.1605310876000.89293.1606894740323%40Atlassian.JIRA.
Jira (FACT-2862) Acceptance test for custom fact with core fact in custom group
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2862 Acceptance test for custom fact with core fact in custom group Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12 , ready for triage 2 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.378486.160553229.89291.1606894740275%40Atlassian.JIRA.
Jira (FACT-2873) KDE Neon is not recognized as Ubuntu base distro
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2873 KDE Neon is not recognized as Ubuntu base distro Change By: Bogdan Irimie Sprint: ghost-2.12 , ready for triage 2 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.379068.1605969408000.89288.1606894740172%40Atlassian.JIRA.
Jira (FACT-2857) Acceptance test for cache with user query
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2857 Acceptance test for cache with user query Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12 , ready for triage 2 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.378287.1605280544000.89287.1606894740115%40Atlassian.JIRA.
Jira (FACT-2861) Acceptance test for partial cache invalidation
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2861 Acceptance test for partial cache invalidation Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12 , ready for triage 2 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.378477.160552265.89290.1606894740220%40Atlassian.JIRA.
Jira (FACT-2865) Acceptance test for consistent caching
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2865 Acceptance test for consistent caching Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12 , ready for triage 2 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.378497.1605536748000.89292.1606894740281%40Atlassian.JIRA.
Jira (FACT-2858) Acceptance test for cache migration from Facter 3 to Facter 4
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2858 Acceptance test for cache migration from Facter 3 to Facter 4 Change By: Bogdan Irimie Sprint: ghost 25.11, ghost-2.12 , ready for triage 2 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.378290.1605282375000.89289.1606894740215%40Atlassian.JIRA.
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title Oana Tanasoiu updated an issue Facter / FACT-2880 facter 4 differing output from facter 3 for service_provider fact Change By: Oana Tanasoiu Sprint: ready for triage 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.379364.1606744776000.89282.1606891200100%40Atlassian.JIRA.
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title Oana Tanasoiu updated an issue Facter / FACT-2880 facter 4 differing output from facter 3 for service_provider fact Change By: Oana Tanasoiu Sub-team: ghost Team: Night's Watch 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.379364.1606744776000.89281.1606891200045%40Atlassian.JIRA.
Jira (FACT-2882) Gem-based Facter 4.0.x does not return the complete FQDN
Title: Message Title Sanjay Tripathi commented on FACT-2882 Re: Gem-based Facter 4.0.x does not return the complete FQDN Note that the domain fact is broken – it returns empty string, which is probably the cause of this issue. 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.379598.1606874598000.89251.1606877040126%40Atlassian.JIRA.
Jira (FACT-2884) How to disable Querying Ec2 metadata
Title: Message Title Sanjay Tripathi created an issue Facter / FACT-2884 How to disable Querying Ec2 metadata Issue Type: Bug Assignee: Unassigned Created: 2020/12/01 6:39 PM Environment: In non-cloud environment, issuing the request to http://169.254.169.254/latest/meta-data causes delay in execution: Facter: Querying Ec2 metadata Facter: Trying to connect to http://169.254.169.254/latest/meta-data/ but got: execution expired How to disable this query (don't need it in a non-cloud environment)? Tried setting the environment variable FACTER_virtual=generic but that does not suppress this query in non-cloud environment. Priority: Critical Reporter: Sanjay Tripathi Add new os support on litmus modules Before to start, make sure the new platform is provided by vmpooler and it's fully equipped an image with the new os is available from puppet agent team Here you can find a list with all the converted modules to use litmus Step1: Using pdksync, check/update metadata.json, ci-job-configs/jenkii/platform/projects/modules-unified.yaml metadata.json file check for section: operatingsystem_support add new version under the intended operatingsystem and save ci-job-configs/jenkii/platform/projects/modules-unified.yaml check for the module and add new platform under smoke_platforms| pe_platforms (if this platform was released) Step2: Using pdksync, create PR with the changes on modules Step3: Create PR on ci-job-configs Step4: Deploy experimental platform intended module Step5: Run ad-hoc tests using that experimental Step6: Check testing results Step7: If failures, fix them
Jira (FACT-2883) Gem-based Facter 4.0.x does not log the facts in debug mode
Title: Message Title Sanjay Tripathi commented on FACT-2883 Re: Gem-based Facter 4.0.x does not log the facts in debug mode In debug mode, native facter logs the fact and its value - as in the following example: Facter: fact "fqdn" has resolved to "mymachine.mydomain.com". This is very helpful in debugging. But the gem-based facter does not log the value in the debug mode – instead it logs the cryptic messages, like: Facter: User query is: ["fqdn"] Facter: Query is fqdn Checking query tokens fqdn Facter: List of resolvable facts: [#] This is not helpful at all. Please change the debug logging to the previous format of logging the value. Also, it would help to avoid the unnecessary clutter, as in the above example of fqdn. 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.379599.1606874914000.89248.1606875240025%40Atlassian.JIRA.
Jira (FACT-2883) Gem-based Facter 4.0.x does not log the facts in debug mode
Title: Message Title Sanjay Tripathi updated an issue Facter / FACT-2883 Gem-based Facter 4.0.x does not log the facts in debug mode Change By: Sanjay Tripathi Priority: Normal Critical 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.379599.1606874914000.89247.1606874940108%40Atlassian.JIRA.
Jira (FACT-2883) Gem-based Facter 4.0.x does not log the facts in debug mode
Title: Message Title Sanjay Tripathi created an issue Facter / FACT-2883 Gem-based Facter 4.0.x does not log the facts in debug mode Issue Type: Bug Assignee: Unassigned Created: 2020/12/01 6:08 PM Priority: Normal Reporter: Sanjay Tripathi Add new os support on litmus modules Before to start, make sure the new platform is provided by vmpooler and it's fully equipped an image with the new os is available from puppet agent team Here you can find a list with all the converted modules to use litmus Step1: Using pdksync, check/update metadata.json, ci-job-configs/jenkii/platform/projects/modules-unified.yaml metadata.json file check for section: operatingsystem_support add new version under the intended operatingsystem and save ci-job-configs/jenkii/platform/projects/modules-unified.yaml check for the module and add new platform under smoke_platforms| pe_platforms (if this platform was released) Step2: Using pdksync, create PR with the changes on modules Step3: Create PR on ci-job-configs Step4: Deploy experimental platform intended module Step5: Run ad-hoc tests using that experimental Step6: Check testing results Step7: If failures, fix them, re-execute all the testing part until they are green Step8: Ask for review/merge check for vmpooler platform pdksync: update metadata.json pdksync: push changes, create commit create PR on ci-job-configs deploy experimental platform intended module run tests through ad-hoc jenkins using that experimental check testing report if failures, fix them, re-execute ad-hoc until they are green review/merge PR
Jira (FACT-2882) Gem-based Facter 4.0.x does not return the complete FQDN
Title: Message Title Sanjay Tripathi created an issue Facter / FACT-2882 Gem-based Facter 4.0.x does not return the complete FQDN Issue Type: Bug Affects Versions: FACT 4.0.44 Assignee: Unassigned Components: Facter 4 Created: 2020/12/01 6:03 PM Environment: The gem-based facter 4.0.x does not return the correct fqdn – it returns the hostname with dot instead of returning hostname with the domain suffix. Example: facter fqdn Output: myhostname. The correct output: myhostname.mydomain.com This breaks scripts which issue http request to the fqdn (like: http://myhostname.:1234 is not reachable). Priority: Critical Reporter: Sanjay Tripathi Add new os support on litmus modules Before to start, make sure the new platform is provided by vmpooler and it's fully equipped an image with the new os is available from puppet agent team Here you can find a list with all the converted modules to use litmus Step1: Using pdksync, check/update metadata.json, ci-job-configs/jenkii/platform/projects/modules-unified.yaml metadata.json file check for section: operatingsystem_support add new version under the intended operatingsystem and save ci-job-configs/jenkii/platform/projects/modules-unified.yaml check for the module and add new
Jira (PDB-4932) Sync summary queries can hang
Title: Message Title Zachary Kent commented on PDB-4932 Re: Sync summary queries can hang A customer recently hit an issue where it appeared that PDB sync got stuck in similar way to what's described in this ticket. In the new case the problem presented differently, but we believe the difference is due to some of the mitigations which have been recently added to address long running PDB sync queries. In the more recent case PDB was reloaded after some issues were seen with the service being intermittently unreachable. After the reload we noticed that the start up sync successfully completed but every subsequent periodic sync was reporting that it was unable to run with the following log message: [sync] Refusing to sync from ... Sync already in progress This was caused by the global currently-syncing atom being set to true and never getting reset because a periodic sync got stuck. We were able to get a thread dump from PDB when it was in this state and confirmed some of our suspicions. It appears that the shutdown of the at-at threadpool we use to schedule tasks was still waiting to gracefully shutdown a periodic sync thread which got stuck at some point before the reload. Evidence of this can be seen in the thread dump. at-at uses a future to shutdown and reset the thread pool we use to schedule sync. See at-at stop-and-reset-pool! call. PDB calls this function when stopping the PDB TK sync service seen here. Because this happens in a future in the at-at library it doesn't block and will wait until all threads running in the pool finish the job they're working on. When we look at the elapsed time of this thread (121 hrs) it roughly lines up with the reload of the PuppetDB service and when the thread dump was taken afterwards. Providing evidence that the at-at stop-and-reset-pool! call was stuck waiting on a thread in the pool to finish. at-at pool shutdown thread from dump. We also see evidence of a sync thread being stuck in the thread dump where it looks like a it's waiting to deref a promise in the puppetlabs/clj-http-client. The elapsed time of this thread (485 hrs) indicates that a periodic sync got stuck sometime before PDB was reloaded and was never cleared during the reload. Before a periodic sync being stuck like this would have caused issues with leaving a long running query held open, but due to the 2hr statement_timeout the customer had in place for the pe-puppetdb user Postgres was able to continue to function even though sync was stuck. stuck sync thread from dump. iiuc, when TK services get a SIGHUP the signal gets intercepted and the stop/start method of the service and its TK deps get called but it doesn't fully shutdown the JVM. This could have caused the behaviour we noticed where the global currently-syncing atom was never reset due to the hung sync and at-at shutdown and as a result any periodic syncs after the reload reported that another sync was already in progress. The full start/stop (SIGTERM) of the PDB service corrected this issue because it forced the stuck threads to get shutdown and reset the state in the currentl
Jira (FACT-2881) puppet 7 treats nonexistent fact differently compared to puppet 6?
Title: Message Title Josh Cooper commented on FACT-2881 Re: puppet 7 treats nonexistent fact differently compared to puppet 6? I went ahead and moved the issue to avoid confusion for new folks encountering the issue. 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.379177.1606234679000.89196.1606870800099%40Atlassian.JIRA.
Jira (FACT-2881) puppet 7 treats nonexistent fact differently compared to puppet 6?
Title: Message Title Josh Cooper moved an issue Facter / FACT-2881 puppet 7 treats nonexistent fact differently compared to puppet 6? Change By: Josh Cooper Key: PUP FACT - 10793 2881 Project: Puppet Facter 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.379177.1606234679000.89195.1606870800074%40Atlassian.JIRA.
Jira (PUP-10796) puppet filebucket fails when using non-default environment from master
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10796 puppet filebucket fails when using non-default environment from master Change By: Josh Cooper Labels: beginner help_wanted 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.379509.160685450.89154.1606868700073%40Atlassian.JIRA.
Jira (PUP-10796) puppet filebucket fails when using non-default environment from master
Title: Message Title Josh Cooper commented on PUP-10796 Re: puppet filebucket fails when using non-default environment from master This is a great beginner puppet ticket. The filebucket application needs to do the same thing as the plugin application 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.379509.160685450.89152.1606868640145%40Atlassian.JIRA.
Jira (PUP-10729) Accessing trusted facts from Ruby report processor
Title: Message Title
Albert Vaca commented on PUP-10729
Re: Accessing trusted facts from Ruby report processor
It turns out there is a way to get the trusted facts already: ``` trusted_facts = (Puppet.lookup(:trusted_information) { Hash.new } ).to_h ``` It's completely different to the code to get regular facts, which isn't the most intuitive thing, but it does the job.
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.374225.1602088494000.3.1606857000103%40Atlassian.JIRA.
Jira (PUP-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Nick commented on PUP-6739 Re: Error running puppet with non-existent and non-default environment Josh Cooper sure thing, I created PUP-10796 for filebucket command. 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.153502.1474835726000.88856.1606854600108%40Atlassian.JIRA.
Jira (PUP-10796) puppet filebucket fails when using non-default environment from master
Title: Message Title Nick created an issue Puppet / PUP-10796 puppet filebucket fails when using non-default environment from master Issue Type: Bug Affects Versions: PUP 5.5.21 Assignee: Unassigned Created: 2020/12/01 12:28 PM Priority: Normal Reporter: Nick Puppet Version: 5.5.21 Puppet Server Version: 5.3.8 OS Name/Version: RHEL 7 When using a non default environment (something other than production) on a puppet agent from the puppet master, for example testenv, running puppet filebucket -l list --bucket /opt/puppetlabs/puppet/cache/clientbucket/ fails with Puppet::Environments::EnvironmentNotFound Desired Behavior: puppet filebucket uses Puppet environment from /etc/puppetlabs/puppet/puppet.conf and runs successfully. Actual Behavior: $ sudo puppet filebucket -l list --bucket /opt/puppetlabs/puppet/cache/clientbucket/ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'testenv' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound) from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application_support.rb:34:in `push_application_context'
Jira (PUP-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Josh Cooper commented on PUP-6739 Re: Error running puppet with non-existent and non-default environment Nick this issue was resolved for config, help and a few other built-in applications. Can you file a new ticket for filebucket? The fix is relative simple, just need to add environment_mode :not_required to https://github.com/puppetlabs/puppet/blob/8bf64bb72eb48cca24d7e6e4c99e6b21e497fa86/lib/puppet/application/filebucket.rb#L4 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.153502.1474835726000.88824.1606853100052%40Atlassian.JIRA.
Jira (PUP-6739) Error running puppet with non-existent and non-default environment
Title: Message Title
Nick commented on PUP-6739
Re: Error running puppet with non-existent and non-default environment
This is happening with Puppet 5.5.21.
$ sudo puppet filebucket -l list --bucket /opt/puppetlabs/puppet/cache/clientbucket/ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'testenv' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound) from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application_support.rb:34:in `push_application_context' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:363:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:139:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:77:in `execute' from /opt/puppetlabs/puppet/bin/puppet:5:in `' $ puppet --version 5.5.21 $ ls -lhatr /etc/puppetlabs/code/environments/ total 0 drwxr-xr-x. 4 root root 41 Jul 3 07:34 .. drwxr-xr-x. 3 root root 24 Jul 3 07:34 . drwxr-xr-x. 5 root root 92 Aug 21 01:30 production ${noformat} Josh Cooper can I provide any more information to help get this resolved?
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10795) Accept multiple logdest locations in puppet.conf
Title: Message Title zendesk.jira updated an issue Puppet / PUP-10795 Accept multiple logdest locations in puppet.conf Change By: zendesk.jira Zendesk Ticket Count: 1 Zendesk Ticket IDs: 42163 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.379455.1606836974000.88493.1606845060036%40Atlassian.JIRA.
Jira (PUP-10795) Accept multiple logdest locations in puppet.conf
Title: Message Title zendesk.jira updated an issue Puppet / PUP-10795 Accept multiple logdest locations in puppet.conf Change By: zendesk.jira Labels: jira_escalated 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.379455.1606836974000.88467.1606843680223%40Atlassian.JIRA.
Jira (PUP-10732) Puppet service report next projected runtime
Title: Message Title Josh Cooper commented on PUP-10732 Re: Puppet service report next projected runtime It would be fairly straightforward to log a message prior to sleeping here: https://github.com/puppetlabs/puppet/blob/8bf64bb72eb48cca24d7e6e4c99e6b21e497fa86/lib/puppet/scheduler/timer.rb#L5 Windows services already log a message (at debug) https://github.com/puppetlabs/puppet/blob/8bf64bb72eb48cca24d7e6e4c99e6b21e497fa86/ext/windows/service/daemon.rb#L89 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.376584.1604068601000.88462.1606843620037%40Atlassian.JIRA.
Jira (PUP-10791) openbsd package provider fails for packages available in multiple versions and multiple flavors
Title: Message Title Mihai Buzgau commented on PUP-10791 Re: openbsd package provider fails for packages available in multiple versions and multiple flavors Thank you for filing this issue. We agree it is likely an improvement, but due to other issues demanding precedence, we don’t anticipate being able to address this any time soon. If you are interested in submitting a patch to the repository for this project at https://github.com/puppetlabs, please open a pull request. 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.379067.1605954148000.88412.1606842600145%40Atlassian.JIRA.
Jira (PUP-10791) openbsd package provider fails for packages available in multiple versions and multiple flavors
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10791 openbsd package provider fails for packages available in multiple versions and multiple flavors Change By: Mihai Buzgau Labels: help_wanted 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.379067.1605954148000.88408.1606842540680%40Atlassian.JIRA.
Jira (PUP-10785) eyaml_lookup_key isn't thread safe
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10785 eyaml_lookup_key isn't thread safe Change By: Mihai Buzgau Team: Froyo 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.378709.1605644458000.88394.1606842420028%40Atlassian.JIRA.
Jira (PDB-4932) Sync summary queries can hang
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-4932 Sync summary queries can hang Change By: Zachary Kent Assignee: Zachary Kent 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.375125.1602801356000.88379.1606841640235%40Atlassian.JIRA.
Jira (PDB-4932) Sync summary queries can hang
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4932 Sync summary queries can hang Change By: Zachary Kent Epic Link: PDB-4969 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.375125.1602801356000.88378.1606841640192%40Atlassian.JIRA.
Jira (PUP-10732) Puppet service report next projected runtime
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10732 Puppet service report next projected runtime Change By: Mihai Buzgau Labels: beginner help-wanted help_wanted 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.376584.1604068601000.88363.1606841160031%40Atlassian.JIRA.
Jira (PUP-10732) Puppet service report next projected runtime
Title: Message Title Mihai Buzgau commented on PUP-10732 Re: Puppet service report next projected runtime Thank you for filing this issue. We agree it is likely an improvement, but due to other issues demanding precedence, we don’t anticipate being able to address this any time soon. If you are interested in submitting a patch please open a pull request. 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.376584.1604068601000.88362.1606841100055%40Atlassian.JIRA.
Jira (PUP-10732) Puppet service report next projected runtime
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10732 Puppet service report next projected runtime Change By: Mihai Buzgau Labels: beginner help-wanted 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.376584.1604068601000.88361.1606840980137%40Atlassian.JIRA.
Jira (PUP-10728) Write transaction Store in JSON
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10728 Write transaction Store in JSON Change By: Mihai Buzgau Sprint: ghost-4.11, ghost-11.11 , Triaged tickets 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.376157.1603778598000.88358.1606840800032%40Atlassian.JIRA.
Jira (PUP-10727) Cannot define a default Timespan value for an attribute in a Ruby language data type
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10727 Cannot define a default Timespan value for an attribute in a Ruby language data type Change By: Mihai Buzgau Team: Night's Watch 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.375925.1603486678000.88353.1606840140164%40Atlassian.JIRA.
Jira (PUP-10727) Cannot define a default Timespan value for an attribute in a Ruby language data type
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10727 Cannot define a default Timespan value for an attribute in a Ruby language data type Change By: Mihai Buzgau Sprint: Triaged tickets 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.375925.1603486678000.88354.1606840140207%40Atlassian.JIRA.
Jira (PUP-10726) hiera lookup removes duplicate array elements during deep merge
Title: Message Title Mihai Buzgau commented on PUP-10726 Re: hiera lookup removes duplicate array elements during deep merge Thank you for filing this issue. We agree it is likely an improvement, but due to other issues demanding precedence, we don’t anticipate being able to address this any time soon. If you are interested in submitting a patch please open a pull request. 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.375651.1603374334000.88344.1606839960024%40Atlassian.JIRA.
Jira (PUP-10729) Accessing trusted facts from Ruby report processor
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10729 Accessing trusted facts from Ruby report processor Change By: Mihai Buzgau Labels: help-wanted 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.374225.1602088494000.88341.1606839840095%40Atlassian.JIRA.
Jira (PUP-10726) hiera lookup removes duplicate array elements during deep merge
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10726 hiera lookup removes duplicate array elements during deep merge Change By: Mihai Buzgau Labels: help-wanted 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.375651.1603374334000.88343.1606839840187%40Atlassian.JIRA.
Jira (PUP-10729) Accessing trusted facts from Ruby report processor
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10729 Accessing trusted facts from Ruby report processor Change By: Mihai Buzgau Labels: help-wanted 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.374225.1602088494000.88342.1606839840142%40Atlassian.JIRA.
Jira (PUP-10729) Accessing trusted facts from Ruby report processor
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10729 Accessing trusted facts from Ruby report processor Change By: Mihai Buzgau Sprint: Triaged tickets 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.374225.1602088494000.88326.1606839300113%40Atlassian.JIRA.
Jira (PUP-10729) Accessing trusted facts from Ruby report processor
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10729 Accessing trusted facts from Ruby report processor Change By: Mihai Buzgau Team: Night's Watch 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.374225.1602088494000.88325.1606839300044%40Atlassian.JIRA.
Jira (PUP-10666) puppet-agent config option require message for disable
Title: Message Title Mihai Buzgau commented on PUP-10666 Re: puppet-agent config option require message for disable Hi Pat Riehecky Thank you for filing this issue. We agree it is likely an improvement, but due to other issues demanding precedence, we don’t anticipate being able to address this any time soon. If you are interested in submitting a patch to the repository for this project at https://github.com/puppetlabs/puppet, please open a pull request. 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.371735.160009288.88322.1606838640023%40Atlassian.JIRA.
Jira (PUP-10666) puppet-agent config option require message for disable
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10666 puppet-agent config option require message for disable Change By: Josh Cooper Labels: beginner help-wanted help_wanted 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.371735.160009288.88306.1606838100043%40Atlassian.JIRA.
Jira (PUP-10666) puppet-agent config option require message for disable
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10666 puppet-agent config option require message for disable Change By: Mihai Buzgau Sprint: Triaged tickets 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.371735.160009288.88304.1606838040140%40Atlassian.JIRA.
Jira (PUP-10666) puppet-agent config option require message for disable
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10666 puppet-agent config option require message for disable Change By: Mihai Buzgau Labels: beginner help-wanted 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.371735.160009288.88303.1606838040098%40Atlassian.JIRA.
Jira (PUP-10666) puppet-agent config option require message for disable
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10666 puppet-agent config option require message for disable Change By: Mihai Buzgau Sprint: Triaged tickets 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.371735.160009288.88297.1606837440027%40Atlassian.JIRA.
Jira (PUP-10729) Accessing trusted facts from Ruby report processor
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10729 Accessing trusted facts from Ruby report processor Change By: Josh Cooper Summary: Accessing trusted facts from Ruby report processor 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.374225.1602088494000.88296.1606837200028%40Atlassian.JIRA.
Jira (PUP-10795) Accept multiple logdest locations in puppet.conf
Title: Message Title Elaine McCloskey updated an issue Puppet / PUP-10795 Accept multiple logdest locations in puppet.conf Change By: Elaine McCloskey When using the option --logdest on the command line it is possible to set it to multiple locations. You can also set logdest in the puppet.conf but it only accepts one location . It should accept multiple locations as the command line does. 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.379455.1606836974000.88295.1606837080030%40Atlassian.JIRA.
Jira (PUP-10795) Accept multiple logdest locations in puppet.conf
Title: Message Title Elaine McCloskey created an issue Puppet / PUP-10795 Accept multiple logdest locations in puppet.conf Issue Type: Improvement Assignee: Unassigned Created: 2020/12/01 7:36 AM Priority: Normal Reporter: Elaine McCloskey When using the option --logdest on the command line it is possible to set it to multiple locations. You can also set logdest in the puppet.conf but it only accepts one location Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title Josh Cooper commented on FACT-2880 Re: facter 4 differing output from facter 3 for service_provider fact The service_provider fact returns the default service provider: https://github.com/puppetlabs/puppetlabs-stdlib/blob/2509d17ccb2504dafae806ba616d6bfd436b44a8/lib/facter/service_provider.rb#L15. So it would seem that one of the facts used to determine if the systemd service provider is suitable (https://github.com/puppetlabs/puppet/blob/8bf64bb72eb48cca24d7e6e4c99e6b21e497fa86/lib/puppet/provider/service/systemd.rb#L12-L28) is not working as expected. 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.379364.1606744776000.88287.1606836060027%40Atlassian.JIRA.
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title Matt Darcy commented on FACT-2880 Re: facter 4 differing output from facter 3 for service_provider fact results are consistent with various versions of stdlib in place, can provide detailed breakdown if requested. 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.379364.1606744776000.88133.1606813860029%40Atlassian.JIRA.
Jira (PDB-4973) PuppetDb is not going to install on Centos 8 missing dependencies
Title: Message Title Timo Bergemann created an issue PuppetDB / PDB-4973 PuppetDb is not going to install on Centos 8 missing dependencies Issue Type: Bug Assignee: Unassigned Components: PuppetDB Created: 2020/12/01 12:54 AM Priority: Normal Reporter: Timo Bergemann This Bug has been reported already 1.5 Years ago but is still open and unassigned. I wounder why this it? Am I missing something ? https://tickets.puppetlabs.com/browse/SERVER-2500?jql=text%20~%20%22Unable%20to%20find%20a%20match%3A%20postgresql96-server%22 Add Comment
