Jira (PUP-11264) certificate verify failed :self certificate in certificate chain for /CN=Puppet Root
Title: Message Title zsy assigned an issue to David Caldwell Puppet / PUP-11264 certificate verify failed :self certificate in certificate chain for /CN=Puppet Root Change By: zsy Assignee: David Caldwell 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.417152.1632465702000.138805.1632465780044%40Atlassian.JIRA.
Jira (PUP-11264) certificate verify failed :self certificate in certificate chain for /CN=Puppet Root
Title: Message Title zsy assigned an issue to Unassigned Puppet / PUP-11264 certificate verify failed :self certificate in certificate chain for /CN=Puppet Root Change By: zsy Assignee: David Caldwell 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.417152.1632465702000.138806.1632465780089%40Atlassian.JIRA.
Jira (PUP-11264) certificate verify failed :self certificate in certificate chain for /CN=Puppet Root
Title: Message Title zsy created an issue Puppet / PUP-11264 certificate verify failed :self certificate in certificate chain for /CN=Puppet Root Issue Type: Bug Affects Versions: PUP 6.15.0 Assignee: Unassigned Created: 2021/09/23 11:41 PM Priority: Critical Reporter: zsy The puppet version of server is 6.15.0 The puppet version of client is 3.6.2 The client keeps reporting errors：Could not request certificate :ssl_connect returned =1 error=0 certificate verify failed:signed certificate in certificate chain for /CN=Puppet Root CA:320F52667ac69b] Add Comment
Jira (PUP-10665) Add weak dependencies to puppet resources
Title: Message Title Reid Vandewiele commented on PUP-10665 Re: Add weak dependencies to puppet resources Language check: to match existing grammar (require, subscribe, before, notify), the suggested weak dependency keywords should be singular, not plural. That is, optional_require optional_notify want wanted_by 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.371714.1599956556000.138602.1632430320084%40Atlassian.JIRA.
Jira (PUP-11212) Remove run stages
Title: Message Title Josh Cooper commented on PUP-11212 Re: Remove run stages Since we A) don't have a replacement for stages and B) need to maintain stages for a long time, I'm going to close this as won't do. We can certainly add a deprecation warning (in PUP-11211) after we've implemented a replacement. 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.138529.1632425460091%40Atlassian.JIRA.
Jira (PUP-11212) Remove run stages
Title: Message Title Josh Cooper commented on PUP-11212 Re: Remove run stages From Reid Vandewiele while we should 100% deprecate stages, it sounds like it may be necessary to continue to maintain their basic functionality for a long time, or else provide an easy replacement for them. Fully removing stages will likely break a lot of customer Puppet code in ways that are very labor-intensive to fix, which is something we would need strong justification for, or benefit from doing. 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.138527.1632425400226%40Atlassian.JIRA.
Jira (PDB-5217) Restore AST query field parser
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5217 Restore AST query field parser Change By: Austin Blatt Assignee: Austin Blatt 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.409105.1627518385000.138286.1632412860310%40Atlassian.JIRA.
Jira (FACT-3075) Windows 2022 is detected as Windows 2019
Title: Message Title Luchian Nemes commented on FACT-3075 Re: Windows 2022 is detected as Windows 2019 Tested this and got the following output: WIndows 2019 output: Windows 2022 output: This confirms the behaviour described in the ticket. Workaround suggestion: Until Windows 2022 is fully supported, to classify nodes via partial match in os.windows.product_name (which seems to be showing correct information). 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.416781.1632314698000.138212.1632410340216%40Atlassian.JIRA.
Jira (PUP-11263) Node name can be conflicted with class name
Title: Message Title Alexander Simenduev commented on PUP-11263 Re: Node name can be conflicted with class name Thanks Josh Cooper for response. So what is the suggested solution now? We are migrating to puppet 7.x from 6.x and we getting those name collisions. As for now I replaced the node definitions with `regex` and it helps, but is it the right way for handling this? 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.416777.1632311336000.138211.1632410340209%40Atlassian.JIRA.
Jira (FACT-3075) Windows 2022 is detected as Windows 2019
Title: Message Title Luchian Nemes updated an issue Facter / FACT-3075 Windows 2022 is detected as Windows 2019 Change By: Luchian Nemes Attachment: windows-2019.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.416781.1632314698000.138207.1632410160167%40Atlassian.JIRA.
Jira (FACT-3075) Windows 2022 is detected as Windows 2019
Title: Message Title Luchian Nemes updated an issue Facter / FACT-3075 Windows 2022 is detected as Windows 2019 Change By: Luchian Nemes Attachment: windows-2022.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.416781.1632314698000.138204.1632410040064%40Atlassian.JIRA.
Jira (PDB-5286) Document how to run the query performance test
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5286 Document how to run the query performance test Change By: Bogdan Irimie Summary: Document how to run the query performance test 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.416898.1632395682000.137863.1632395820069%40Atlassian.JIRA.
Jira (PDB-5286) Document how to run the query performance tests
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5286 Document how to run the query performance tests Change By: Bogdan Irimie Create a new confluence page where we detail how one might run the performance tests. The doc should contain at least: # where to find the performance test # how to run them # what do they output # how to make sens of the output # caveats (one of them might be that if we run two performance test at once, the results will be irelevant, because they will fight for resources) 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.416898.1632395682000.137865.1632395820162%40Atlassian.JIRA.
Jira (PDB-5286) Document how to run the query performance tests
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5286 Document how to run the query performance tests Change By: Bogdan Irimie Summary: Document how to run the query performance test tests 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.416898.1632395682000.137864.1632395820114%40Atlassian.JIRA.
Jira (PDB-5286) Document how to run the performance test
Title: Message Title Bogdan Irimie created an issue PuppetDB / PDB-5286 Document how to run the performance test Issue Type: Task Assignee: Unassigned Created: 2021/09/23 4:14 AM Priority: Normal Reporter: Bogdan Irimie Create a new confluence page where we detail how one might run the performance tests. The doc should contain at least: where to find the performance test how to run them what do they output make sens of the output caveats (one of them might be that if we run two performance test at once, the results will be irelevant, because they will fight for resources) Add Comment
Jira (FACT-2713) Facter fact 'disks' doesn`t display serial_number because of missed libudev-dev dependency
Title: Message Title Ciprian Badescu commented on FACT-2713 Re: Facter fact 'disks' doesn`t display serial_number because of missed libudev-dev dependency Hi Valentyna, is this ticket still an issue? If yes, please provide us more information (platform used, facter version). 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.365791.1594732505000.137755.1632387600271%40Atlassian.JIRA.
Jira (FACT-2479) Uptime facts on LXC get the uptime from the host OS and not the container.
Title: Message Title Ciprian Badescu commented on FACT-2479 Re: Uptime facts on LXC get the uptime from the host OS and not the container. Hi Atanas Stoyanov, puppet has moved on considerably from the time this issue was raised and we feel it may no longer be a valid issue. If you feel otherwise please do not hesitate to re-open this ticket and provide more information as to why this may still be a valid 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.350675.1584693591000.137751.1632387480063%40Atlassian.JIRA.
Jira (FACT-2772) Facter in puppet 6.18.0-1 fails to prevent external facts from calling facter recursively (FACT-1373)
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-2772 Facter in puppet 6.18.0-1 fails to prevent external facts from calling facter recursively (FACT-1373) Change By: Ciprian Badescu Sprint: ready for triage 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.370195.1598387754000.137682.1632384120158%40Atlassian.JIRA.
Jira (FACT-2713) Facter fact 'disks' doesn`t display serial_number because of missed libudev-dev dependency
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-2713 Facter fact 'disks' doesn`t display serial_number because of missed libudev-dev dependency Change By: Ciprian Badescu Sprint: ready for triage 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.365791.1594732505000.137673.1632383940107%40Atlassian.JIRA.
Jira (FACT-2664) Information for utun2 networking interface is incorrect
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-2664 Information for utun2 networking interface is incorrect Change By: Ciprian Badescu Sprint: ready for triage 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.363078.1592375202000.137668.1632383760036%40Atlassian.JIRA.
Jira (FACT-2250) Facter ignores signals while waiting for external commands to run
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-2250 Facter ignores signals while waiting for external commands to run Change By: Ciprian Badescu Sprint: ready for triage 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.339252.1576183486000.137660.1632383520984%40Atlassian.JIRA.
Jira (PUP-9997) Puppet must not call Dir.chdir() except in a child process
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-9997 Puppet must not call Dir.chdir() except in a child process Change By: Ciprian Badescu Sprint: ready for triage 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.323575.156763800.137636.1632383400066%40Atlassian.JIRA.
