Jira (PUP-10536) Puppet windows package provider fails if there are garbage characters after an embedded NULL
Title: Message Title Austin Boyd updated an issue Puppet / PUP-10536 Puppet windows package provider fails if there are garbage characters after an embedded NULL Change By: Austin Boyd Zendesk Ticket Count: 1 Zendesk Ticket IDs: 38573 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.360365.1590695652000.73263.1590724200043%40Atlassian.JIRA.
Jira (PUP-10536) Puppet windows package provider fails if there are garbage characters after an embedded NULL
Title: Message Title Austin Boyd updated an issue Puppet / PUP-10536 Puppet windows package provider fails if there are garbage characters after an embedded NULL Change By: Austin Boyd 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.360365.1590695652000.73264.1590724200099%40Atlassian.JIRA.
Jira (PUP-10518) Prepare release announcement (Puppet Platform 6.16.0)
Title: Message Title Nirupama Mantha commented on PUP-10518 Re: Prepare release announcement (Puppet Platform 6.16.0) The next release in the Puppet 6 series, Puppet 6.16.0, is now available! The release contains security and bug fixes and minor improvements, including: For the full list of changes, check out the release notes: https://puppet.com/docs/puppet/latest/release_notes_puppet.html 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.359064.1589813759000.73086.1590704160025%40Atlassian.JIRA.
Jira (PDB-4758) Remove ubuntu-16.04-amd64 from pe-puppetdb for PE 2019.8
Title: Message Title Sara Meisburger updated an issue PuppetDB / PDB-4758 Remove ubuntu-16.04-amd64 from pe-puppetdb for PE 2019.8 Change By: Sara Meisburger Epic Link: RE-13515 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.360436.1590701472000.73023.1590701522727%40Atlassian.JIRA.
Jira (PDB-4758) Remove ubuntu-16.04-amd64 from pe-puppetdb for PE 2019.8
Title: Message Title Sara Meisburger created an issue PuppetDB / PDB-4758 Remove ubuntu-16.04-amd64 from pe-puppetdb for PE 2019.8 Issue Type: Task Assignee: Unassigned Created: 2020/05/28 2:31 PM Priority: Normal Reporter: Sara Meisburger Remove ubuntu-16.04-amd64 for pe-puppetdb For Clojure projects, change the puppetlabs/lein-ezbake version in the project.clj file to a version that no longer includes the platform. This can be retrieved from the ezbake changelog. For Vanagon projects, remove the configuration file in configs/platforms for ubuntu-16.04-amd64 and remove ubuntu-16.04-amd64 from ext/build_defaults.yaml Add Comment
Jira (BOLT-1552) Remove ubuntu-16.04-amd64 from pe-bolt-server for PE 2019.8
Title: Message Title Sara Meisburger created an issue Puppet Task Runner / BOLT-1552 Remove ubuntu-16.04-amd64 from pe-bolt-server for PE 2019.8 Issue Type: Task Assignee: Unassigned Created: 2020/05/28 2:30 PM Priority: Normal Reporter: Sara Meisburger Remove ubuntu-16.04-amd64 for pe-bolt-server For Clojure projects, change the puppetlabs/lein-ezbake version in the project.clj file to a version that no longer includes the platform. This can be retrieved from the ezbake changelog. For Vanagon projects, remove the configuration file in configs/platforms for ubuntu-16.04-amd64 and remove ubuntu-16.04-amd64 from ext/build_defaults.yaml Add Comment
Jira (PDB-4756) Disable ubuntu-16.04-amd64 builds for puppetdb
Title: Message Title Sara Meisburger created an issue PuppetDB / PDB-4756 Disable ubuntu-16.04-amd64 builds for puppetdb Issue Type: Task Assignee: Unassigned Created: 2020/05/28 2:30 PM Priority: Normal Reporter: Sara Meisburger 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-4757) Disable ubuntu-16.04-amd64 test pipeline for puppetdb
Title: Message Title Sara Meisburger created an issue PuppetDB / PDB-4757 Disable ubuntu-16.04-amd64 test pipeline for puppetdb Issue Type: Task Assignee: Unassigned Created: 2020/05/28 2:30 PM Priority: Normal Reporter: Sara Meisburger Remove ubuntu-16.04-amd64 from puppetdb test matrices in ci-job-configs. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2645) Remove Facter for JRuby on ubuntu-16.04-amd64
Title: Message Title Sara Meisburger updated an issue Facter / FACT-2645 Remove Facter for JRuby on ubuntu-16.04-amd64 Change By: Sara Meisburger Epic Link: RE-13515 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.360412.1590701406000.73014.1590701460171%40Atlassian.JIRA.
Jira (PDB-4756) Disable ubuntu-16.04-amd64 builds for puppetdb
Title: Message Title Sara Meisburger updated an issue PuppetDB / PDB-4756 Disable ubuntu-16.04-amd64 builds for puppetdb Change By: Sara Meisburger Epic Link: RE-13515 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.360416.1590701416000.73016.1590701460259%40Atlassian.JIRA.
Jira (PDB-4757) Disable ubuntu-16.04-amd64 test pipeline for puppetdb
Title: Message Title Sara Meisburger updated an issue PuppetDB / PDB-4757 Disable ubuntu-16.04-amd64 test pipeline for puppetdb Change By: Sara Meisburger Epic Link: RE-13515 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.360417.1590701418000.73018.1590701460347%40Atlassian.JIRA.
Jira (FACT-2645) Remove Facter for JRuby on ubuntu-16.04-amd64
Title: Message Title Sara Meisburger created an issue Facter / FACT-2645 Remove Facter for JRuby on ubuntu-16.04-amd64 Issue Type: Task Assignee: Unassigned Created: 2020/05/28 2:30 PM Priority: Normal Reporter: Sara Meisburger The Facter configurations in puppet-agent needs to be updated to no longer build Facter for JRuby on ubuntu-16.04-amd64. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (BOLT-1552) Remove ubuntu-16.04-amd64 from pe-bolt-server for PE 2019.8
Title: Message Title Sara Meisburger updated an issue Puppet Task Runner / BOLT-1552 Remove ubuntu-16.04-amd64 from pe-bolt-server for PE 2019.8 Change By: Sara Meisburger Epic Link: RE-13515 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.360425.1590701442000.73020.1590701460434%40Atlassian.JIRA.
Jira (PDB-4755) Remove el-6-x86_64 from pe-puppetdb for PE 2019.8
Title: Message Title Sara Meisburger updated an issue PuppetDB / PDB-4755 Remove el-6-x86_64 from pe-puppetdb for PE 2019.8 Change By: Sara Meisburger Epic Link: RE-13500 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.360398.1590701285000.73002.1590701340103%40Atlassian.JIRA.
Jira (PDB-4755) Remove el-6-x86_64 from pe-puppetdb for PE 2019.8
Title: Message Title Sara Meisburger created an issue PuppetDB / PDB-4755 Remove el-6-x86_64 from pe-puppetdb for PE 2019.8 Issue Type: Task Assignee: Unassigned Created: 2020/05/28 2:28 PM Priority: Normal Reporter: Sara Meisburger Remove el-6-x86_64 for pe-puppetdb For Clojure projects, change the puppetlabs/lein-ezbake version in the project.clj file to a version that no longer includes the platform. This can be retrieved from the ezbake changelog. For Vanagon projects, remove the configuration file in configs/platforms for el-6-x86_64 and remove el-6-x86_64 from ext/build_defaults.yaml Add Comment
Jira (PDB-4754) Disable el-6-x86_64 test pipeline for puppetdb
Title: Message Title Sara Meisburger created an issue PuppetDB / PDB-4754 Disable el-6-x86_64 test pipeline for puppetdb Issue Type: Task Assignee: Unassigned Created: 2020/05/28 2:27 PM Priority: Normal Reporter: Sara Meisburger Remove el-6-x86_64 from puppetdb test matrices in ci-job-configs. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4754) Disable el-6-x86_64 test pipeline for puppetdb
Title: Message Title Sara Meisburger updated an issue PuppetDB / PDB-4754 Disable el-6-x86_64 test pipeline for puppetdb Change By: Sara Meisburger Epic Link: RE-13500 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.360379.1590701231000.72998.1590701280301%40Atlassian.JIRA.
Jira (PDB-4753) Disable el-6-x86_64 builds for puppetdb
Title: Message Title Sara Meisburger created an issue PuppetDB / PDB-4753 Disable el-6-x86_64 builds for puppetdb Issue Type: Task Assignee: Unassigned Created: 2020/05/28 2:27 PM Priority: Normal Reporter: Sara Meisburger 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-4753) Disable el-6-x86_64 builds for puppetdb
Title: Message Title Sara Meisburger updated an issue PuppetDB / PDB-4753 Disable el-6-x86_64 builds for puppetdb Change By: Sara Meisburger Epic Link: RE-13500 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.360378.1590701229000.72996.1590701280211%40Atlassian.JIRA.
Jira (BOLT-1551) Remove el-6-x86_64 from pe-bolt-server for PE 2019.8
Title: Message Title Sara Meisburger created an issue Puppet Task Runner / BOLT-1551 Remove el-6-x86_64 from pe-bolt-server for PE 2019.8 Issue Type: Task Assignee: Unassigned Created: 2020/05/28 2:27 PM Priority: Normal Reporter: Sara Meisburger Remove el-6-x86_64 for pe-bolt-server For Clojure projects, change the puppetlabs/lein-ezbake version in the project.clj file to a version that no longer includes the platform. This can be retrieved from the ezbake changelog. For Vanagon projects, remove the configuration file in configs/platforms for el-6-x86_64 and remove el-6-x86_64 from ext/build_defaults.yaml Add Comment
Jira (BOLT-1551) Remove el-6-x86_64 from pe-bolt-server for PE 2019.8
Title: Message Title Sara Meisburger updated an issue Puppet Task Runner / BOLT-1551 Remove el-6-x86_64 from pe-bolt-server for PE 2019.8 Change By: Sara Meisburger Epic Link: RE-13500 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.360387.1590701255000.73000.1590701280387%40Atlassian.JIRA.
Jira (FACT-2644) Remove Facter for JRuby on el-6-x86_64
Title: Message Title Sara Meisburger created an issue Facter / FACT-2644 Remove Facter for JRuby on el-6-x86_64 Issue Type: Task Assignee: Unassigned Created: 2020/05/28 2:26 PM Priority: Normal Reporter: Sara Meisburger The Facter configurations in puppet-agent needs to be updated to no longer build Facter for JRuby on el-6-x86_64. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2644) Remove Facter for JRuby on el-6-x86_64
Title: Message Title Sara Meisburger updated an issue Facter / FACT-2644 Remove Facter for JRuby on el-6-x86_64 Change By: Sara Meisburger Epic Link: RE-13500 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.360374.1590701217000.72993.1590701220115%40Atlassian.JIRA.
Jira (PUP-10536) Puppet windows package provider fails if there is garbage characters after an embedded NULL
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10536 Puppet windows package provider fails if there is garbage characters after an embedded NULL Change By: Josh Cooper Issue Type: Task Bug 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.360365.1590695652000.72886.1590696660120%40Atlassian.JIRA.
Jira (PUP-10536) Puppet windows package provider fails if there is garbage characters after an embedded NULL
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10536
Puppet windows package provider fails if there is garbage characters after an embedded NULL
Change By:
Josh Cooper
Puppet scans the registry when retrieving the list of currently installed packages. If one of the registry values it scans contains an embedded null followed by garbage, then puppet will try to transcode from UTF-16LE to UTF-8 and may fail.A fix for the embedded NULL problem was made in PUP-9639. However, the problem is that it only works if transcoding fails before the value can be sanitized succeeds .When reading package names, versions, etc from the registry puppet should read up to the first wide null or the length of the string, whichever comes first, and remove the sanitize method. If there is a problem reading one of the whitelisted keys, it should print the name of the key in the error message.To reproduce, import the following registry file whose {{DisplayVersion}} is corrupt and try to run puppet: {noformat} C:\ProgramData\PuppetLabs>type C:\Users\Administrator\Documents\test.regWindows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\PUP10536]"DisplayName"="PUP10536""DisplayVersion"=hex(2):31,0,36,0,2e,0,30,0,2e,0,31,0,30,0,33,0,35,0,37,0,2e,0,32,0,30,0,30,0,30,0,32,0,0,0,0,0,0,0,0,0,f3,23,8a,bc,fa,7f,0,0,10,65,74,b9,fa,7f,0,0,90,d8,55,6f,59,0,0,0C:\ProgramData\PuppetLabs>reg import C:\Users\Administrator\Documents\test.regThe operation completed successfully.C:\ProgramData\PuppetLabs>puppet resource package --traceError: Could not run: "\x90\xD8" followed by "Uo" on UTF-16LEC:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:59:in `encode'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:59:in `read_wide_string'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:237:in `block in read'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:281:in `block (3 levels) in query_value_ex'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:268:in `initialize'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:268:in `new'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:268:in `block (2 levels) in query_value_ex'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:263:in `initialize'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:263:in `new'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:263:in `block in query_value_ex'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:262:in `initialize'C:/Program Files/Puppet
Jira (PUP-10536) Puppet windows package provider fails if there are garbage characters after an embedded NULL
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10536 Puppet windows package provider fails if there are garbage characters after an embedded NULL Change By: Josh Cooper Summary: Puppet windows package provider fails if there is are garbage characters after an embedded NULL 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.360365.1590695652000.72887.1590696660164%40Atlassian.JIRA.
Jira (PUP-10536) Puppet windows package provider fails if there is garbage characters after an embedded NULL
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10536 Puppet windows package provider fails if there is garbage characters after an embedded NULL Change By: Josh Cooper 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.360365.1590695652000.72883.1590696540033%40Atlassian.JIRA.
Jira (PUP-10536) Puppet windows package provider fails if there is garbage characters after an embedded NULL
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10536
Puppet windows package provider fails if there is garbage characters after an embedded NULL
Change By:
Josh Cooper
Puppet scans the registry when retrieving the list of currently installed packages. If one of the registry values it scans contains an embedded null followed by garbage, then puppet will try to transcode from UTF-16LE to UTF-8 and fail.A fix for the embedded NULL problem was made in PUP-9639. However, the problem is that transcoding fails before the value can be sanitized.When reading package names, versions, etc from the registry puppet should read up to the first wide null or the length of the string, whichever comes first, and remove the sanitize method. If there is a problem reading one of the whitelisted keys, it should print the name of the key in the error message. To reproduce, import the following registry file whose {{DisplayVersion}} is corrupt and try to run puppet:{noformat}C:\ProgramData\PuppetLabs>type C:\Users\Administrator\Documents\test.regWindows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\PUP10536]"DisplayName"="PUP10536""DisplayVersion"=hex(2):31,0,36,0,2e,0,30,0,2e,0,31,0,30,0,33,0,35,0,37,0,2e,0,32,0,30,0,30,0,30,0,32,0,0,0,0,0,0,0,0,0,f3,23,8a,bc,fa,7f,0,0,10,65,74,b9,fa,7f,0,0,90,d8,55,6f,59,0,0,0C:\ProgramData\PuppetLabs>reg import C:\Users\Administrator\Documents\test.regThe operation completed successfully.C:\ProgramData\PuppetLabs>puppet resource package --traceError: Could not run: "\x90\xD8" followed by "Uo" on UTF-16LEC:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:59:in `encode'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:59:in `read_wide_string'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:237:in `block in read'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:281:in `block (3 levels) in query_value_ex'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:268:in `initialize'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:268:in `new'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:268:in `block (2 levels) in query_value_ex'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:263:in `initialize'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:263:in `new'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:263:in `block in query_value_ex'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:262:in `initialize'C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:262:in
Jira (PUP-10536) Puppet windows package provider fails if there is garbage characters after an embedded NULL
Title: Message Title Josh Cooper created an issue Puppet / PUP-10536 Puppet windows package provider fails if there is garbage characters after an embedded NULL Issue Type: Task Assignee: Unassigned Created: 2020/05/28 12:54 PM Priority: Normal Reporter: Josh Cooper Puppet scans the registry when retrieving the list of currently installed packages. If one of the registry values it scans contains an embedded null followed by garbage, then puppet will try to transcode from UTF-16LE to UTF-8 and fail. A fix for the embedded NULL problem was made in PUP-9639. However, the problem is that transcoding fails before the value can be sanitized. When reading package names, versions, etc from the registry puppet should read up to the first wide null or the length of the string, whichever comes first, and remove the sanitize method. If there is a problem reading one of the whitelisted keys, it should print the name of the key in the error message. Add Comment
Jira (PUP-9958) Cannot add custom CA certs for internal resources without replacing bundled CA
Title: Message Title Josh Cooper commented on PUP-9958 Re: Cannot add custom CA certs for internal resources without replacing bundled CA PUP-7814 makes it possible to specify an arbitrary file containing trusted CA certs that will be used when making HTTPS connections using puppet's HTTP client. This won't fix this issue because the apt provider uses open-uri. I think we should move this ticket to the MODULES project. 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.286210.1542994571000.72761.1590688080179%40Atlassian.JIRA.
Jira (PUP-7814) HTTPS file sources with non-puppet-trusted certs can't be used
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-7814
HTTPS file sources with non-puppet-trusted certs can't be used
Change By:
Josh Cooper
Acceptance Criteria:
It should be possible to retrieve file metadata and content from the following http(s) sources:1. From the puppetserver (already works)2. From a server whose CA cert is contained in the puppet-agent CA bundle (already works)3. From a server whose CA cert is not in the puppet-agent CA bundle, but is in a file or directory system location, eg /etc/pki/tls/cert.pem, and puppet is configured to use that location. If referring to a directory, it is up to the user to rehash the directory file (new).To support this:1. Add a new puppet setting of type {{ file_or_directory :file } } 2. Default to nil3. Update {{Puppet::SSL::SSLProvider#create_system_context}} to call {{OpenSSL::X509::Store#add_file}} or {{add_path}} if the setting is not-nil and the file or directory exists, respectively .4. Update spec/integration/http/client_spec to ensure it makes an HTTPS connection to a test server when the CA cert is not referenced by {{SSL_CERT_FILE}}, but is referenced by the new setting.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
Jira (PUP-7814) HTTPS file sources with non-puppet-trusted certs can't be used
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7814 HTTPS file sources with non-puppet-trusted certs can't be used Change By: Josh Cooper Release Notes: New Feature Release Notes Summary: Puppet agents can be configured to trust additional CA certificates when connecting to HTTPS servers whose issuing CA certificate is neither the puppet CA nor in the CA cert bundle in the puppet-agent package. This can be accomplished by setting "ssl_trust_store" to a file containing CA cert(s) in PEM format concatenated together. For example, "/etc/pki/tls/cert.pem". Note the setting only applies when puppet makes an HTTPS request to non-puppet REST endpoints, such as when applying a file resource with an "https://" source parameter or running "puppet module install" to install modules from the forge. Puppet REST requests, such as retrieving a catalog, will only trust the puppet CA regardless of the ssl_trust_store setting. Previously the only way to trust additional CA certificates was to manually add the certificate to puppet-agent's CA bundle, however, those changes were lost as soon as the puppet-agent package was next updated. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-7814) HTTPS file sources with non-puppet-trusted certs can't be used
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7814 HTTPS file sources with non-puppet-trusted certs can't be used Change By: Josh Cooper Fix Version/s: PUP 6.17.0 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.203766.1501710671000.72724.1590687420083%40Atlassian.JIRA.
Jira (PUP-10391) URI.escape is obsolete in Ruby 2.7
Title: Message Title Melissa Stone updated an issue Puppet / PUP-10391 URI.escape is obsolete in Ruby 2.7 Change By: Melissa Stone Release Notes: Not Needed 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.351394.1585310712000.72722.1590687360182%40Atlassian.JIRA.
Jira (PDB-4748) Check pinned deps for 6.11 release
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4748 Check pinned deps for 6.11 release Change By: Rob Browning Fix Version/s: PDB 6.11.0 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.359737.159017369.72715.1590687180495%40Atlassian.JIRA.
Jira (PUP-10391) URI.escape is obsolete in Ruby 2.7
Title: Message Title Josh Cooper commented on PUP-10391 Re: URI.escape is obsolete in Ruby 2.7 Passed CI in 9b5bd2ad8b180efa4c143798a1a2b362928f1f1c. I filed PUP-10535 to handle moving to addressable. 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.351394.1585310712000.72681.1590685860045%40Atlassian.JIRA.
Jira (PUP-7814) HTTPS file sources with non-puppet-trusted certs can't be used
Title: Message Title Josh Cooper commented on PUP-7814 Re: HTTPS file sources with non-puppet-trusted certs can't be used Passed CI in 9b5bd2ad8b180efa4c143798a1a2b362928f1f1c 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.203766.1501710671000.72682.1590685860087%40Atlassian.JIRA.
Jira (PUP-10535) Move to Addressable
Title: Message Title Josh Cooper created an issue Puppet / PUP-10535 Move to Addressable Issue Type: Task Assignee: Unassigned Created: 2020/05/28 10:09 AM Fix Versions: PUP 7.0.0 Priority: Normal Reporter: Josh Cooper Ruby's URI.escape/unescape is deprecated and will be removed in a future release. We should move to using Addressable instead. This will likely change how some special characters are encoded and may introduce incompatibility between old agents retrieving file metadata and content from newer puppetservers. It would be good to document differences among URI.escape vs Addressable vs puppetserver/jetty. Add Comment
Jira (PDB-4752) Broken link on PDB High Availability (HA) DOOs page
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4752 Broken link on PDB High Availability (HA) DOOs page Change By: Zachary Kent Labels: docs 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.360337.1590683319000.72665.1590685080027%40Atlassian.JIRA.
Jira (PDB-4752) Broken link on PDB High Availability (HA) DOOs page
Title: Message Title Steve Axthelm created an issue PuppetDB / PDB-4752 Broken link on PDB High Availability (HA) DOOs page Issue Type: Bug Assignee: Unassigned Created: 2020/05/28 9:28 AM Priority: Normal Reporter: Steve Axthelm The PDB HA page has a link in the second 'graph: For more information about high availability in Puppet Enterprise, see High availability overview. That 404's and I think should point to here: https://puppet.com/docs/pe/latest/high_availability_overview.html Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4744) Unify all default error exit statuses
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4744 Unify all default error exit statuses Change By: Rob Browning Fix Version/s: PDB 6.11.0 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.359580.1590090724000.72596.1590681420025%40Atlassian.JIRA.
Jira (PDB-4744) Unify all default error exit statuses
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4744 Unify all default error exit statuses Change By: Rob Browning Release Notes: Enhancement Release Notes Summary: In cases where the PuppetDB process previously exited with a status of 1 on failure, it should now exit with a status of 2, leaving 1 free for possible use in the future as a false value (as other programs like grep do). 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.359580.1590090724000.72587.1590681300127%40Atlassian.JIRA.
Jira (PDB-4743) Finish slingshot removal
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4743 Finish slingshot removal Change By: Rob Browning Fix Version/s: PDB 6.11.0 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.359541.1590078449000.72570.1590681000135%40Atlassian.JIRA.
Jira (PDB-4743) Finish slingshot removal
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4743 Finish slingshot removal Change By: Rob Browning Affects Version/s: PDB 6.11.0 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.359541.1590078449000.72569.159068192%40Atlassian.JIRA.
Jira (PDB-4743) Finish slingshot removal
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4743 Finish slingshot removal Change By: Rob Browning Affects Version/s: PDB 6.11.0 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.359541.1590078449000.72567.1590680940033%40Atlassian.JIRA.
Jira (FACT-2643) Timeout on resolution
Title: Message Title Andrei Filipovici created an issue Facter / FACT-2643 Timeout on resolution Issue Type: Task Assignee: Unassigned Created: 2020/05/28 5:04 AM Priority: Normal Reporter: Andrei Filipovici Timeout on resolution does nothing on Facter 4 and on Facter 3 it shows a warning saying that timeout is not supported on custom facts. Further investigation is needed. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2438) Remove methods from facter 4 api which are private in facter 3
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2438 Remove methods from facter 4 api which are private in facter 3 Change By: Andrei Filipovici The Exception module is extended by the Resolution class. Only the which and exec methods are needed, to maintain compatibility with Facter 3.x. For this, a new module with just the two methods from Execution will be created and included in the Resolution and Aggregate classes. value, name, execute, flush, weight on resolution are private in facter 3 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.348956.1583743089000.72187.1590666900045%40Atlassian.JIRA.
Jira (FACT-2438) Remove methods from facter 4 api which are private in facter 3
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2438 Remove methods from facter 4 api which are private in facter 3 Change By: Andrei Filipovici The Exception module is extended by the Resolution class. Only the which and exec methods are needed, to maintain compatibility with Facter 3.x. For this, a new module with just the two methods from Execution will be created and included in the Resolution and Aggregate classes. flush, weight on resolution is are private in facter 3 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.348956.1583743089000.72184.1590666540033%40Atlassian.JIRA.
Jira (FACT-2321) Extend Facter 4.x API with log_exception
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2321 Extend Facter 4.x API with log_exception Change By: Andrei Filipovici Facter.log_exception(NoMemoryError, 'new error') on facter 4 returnsERROR Facter - new errorFacter 3 returns:ERROR puppetlabs.facter - teapa new error 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.344087.1580306166000.72169.1590665160029%40Atlassian.JIRA.
Jira (FACT-2321) Extend Facter 4.x API with log_exception
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2321 Extend Facter 4.x API with log_exception Change By: Andrei Filipovici Facter.log_exception(NoMemoryError, 'new error') on facter 4 returnsERROR Facter - new errorFacter 3 returns:ERROR puppetlabs.facter - teapa 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.344087.1580306166000.72168.1590664860027%40Atlassian.JIRA.
Jira (FACT-2642) fact value for aggregates is printed twice on facter 3 and once on facter 4
Title: Message Title Andrei Filipovici created an issue Facter / FACT-2642 fact value for aggregates is printed twice on facter 3 and once on facter 4 Issue Type: Bug Assignee: Unassigned Created: 2020/05/28 4:11 AM Priority: Normal Reporter: Andrei Filipovici For a fact with chunks: chunk(:chunk1) do 'value 1' end chunk(:chunk2) do 'value 2' end fact.value on facter 3 yields: value 1 value 2 [ "value 1", "value 2" ] facter 4 gives: value 1 value 2 if we have the aggregate method with just an int, when calling fact.value, facter 3 prints the value twice and facter 4 prints it twice. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2438) Remove methods from facter 4 api which are private in facter 3
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2438 Remove methods from facter 4 api which are private in facter 3 Change By: Andrei Filipovici The Exception module is extended by the Resolution class. Only the which and exec methods are needed, to maintain compatibility with Facter 3.x. For this, a new module with just the two methods from Execution will be created and included in the Resolution and Aggregate classes. weight on resolution is private in facter 3 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.348956.1583743089000.72076.1590661020029%40Atlassian.JIRA.
Jira (FACT-2438) Remove methods from facter 4 api which are private in facter 3
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2438 Remove methods from facter 4 api which are private in facter 3 Change By: Andrei Filipovici Summary: Remove unnecessary Execution module methods from Resolution facter 4 api which are private in facter 3 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.348956.1583743089000.72074.1590660780027%40Atlassian.JIRA.
Jira (FACT-2641) Facter.add unknown parameter has different errors on Facter 3 and 4
Title: Message Title Andrei Filipovici created an issue Facter / FACT-2641 Facter.add unknown parameter has different errors on Facter 3 and 4 Issue Type: Bug Assignee: Unassigned Created: 2020/05/28 3:04 AM Priority: Low Reporter: Andrei Filipovici Facter.add(:foo, :setcode => nil) on facter 3 fails with: 2020-05-28 09:53:17.828663 ERROR puppetlabs.facter - error while resolving custom facts in /root/custom_facts/fact.rb: unexpected option setcode On facter 4 fails with: unable to add resolve nil for fact oss: Invalid resolution options [:setcode] Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2640) When api method is missing, errors between Facter 3 and 4 are different
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2640 When api method is missing, errors between Facter 3 and 4 are different Change By: Andrei Filipovici Summary: When api metod method is missing, errors between Facter 3 and 4 are different 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.360272.159065925.72062.1590659280127%40Atlassian.JIRA.
Jira (FACT-2640) When api metod is missing, errors between Facter 3 and 4 are different
Title: Message Title Andrei Filipovici created an issue Facter / FACT-2640 When api metod is missing, errors between Facter 3 and 4 are different Issue Type: Bug Assignee: Unassigned Created: 2020/05/28 2:47 AM Priority: Low Reporter: Andrei Filipovici When we make a call like Facter.foo() on facter 3 we get an error like this: 2020-05-28 09:41:15.089517 ERROR puppetlabs.facter - error while resolving custom facts in /root/custom_facts/fact.rb: undefined method `foo' for Facter:Module On Facter 4 we get an error like: [2020-05-28 12:45:03.058485 ] ERROR Facter - -foo- not implemented but required with params: [:oss] with block: # called by: ["/Users/andrei.filipovici/projects/facter-ng/custom_facts/fact.rb:3:in `'", "/Users/andrei.filipovici/projects/facter-ng/lib/custom_facts/util/loader.rb:125:in `load'", "/Users/andrei.filipovici/projects/facter-ng/lib/custom_facts/util/loader.rb:125:in `kernel_load'", "/Users/andrei.filipovici/projects/facter-ng/lib/custom_facts/util/loader.rb:110:in `load_file'", "/Users/andrei.filipovici/projects/facter-ng/lib/custom_facts/util/loader.rb:45:in `block (2 levels) in load_all'", "/Users/andrei.filipovici/projects/facter-ng/lib/custom_facts/util/loader.rb:43:in `each'", "/Users/andrei.filipovici/projects/facter-ng/lib/custom_facts/util/loader.rb:43:in `block in load_all'", "/Users/andrei.filipovici/projects/facter-ng/lib/custom_facts/util/loader.rb:41:in `each'", "/Users/andrei.filipovici/projects/facter-ng/lib/custom_facts/util/loader.rb:41:in `load_all'", "/Users/andrei.filipovici/projects/facter-ng/lib/custom_facts/util/collection.rb:116:in `custom_facts'", "/Users/andrei.filipovici/projects/facter-ng/lib/framework/core/fact_loaders/external_fact_loader.rb:22:in `load_custom_facts'", "/Users/andrei.filipovici/projects/facter-ng/lib/framework/core/fact_loaders/external_fact_loader.rb:6:in `custom_facts'", "/Users/andrei.filipovici/projects/facter-ng/lib/framework/core/fact_loaders/fact_loader.rb:51:in `load_external_facts'", "/Users/andrei.filipovici/projects/facter-ng/lib/framework/core/fact_loaders/fact_loader.rb:24:in `load'", "/Users/andrei.filipovici/projects/facter-ng/lib/framework/core/fact_manager.rb:20:in
Jira (FACT-2639) facter.conf location should be dependent on Agent AIO version
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2639 facter.conf location should be dependent on Agent AIO version Change By: Bogdan Irimie When in AIO context, Facter should read the config file from `/etc/puppetlabs/facter/facter.conf`When not in AIO context, Facter should read facter.conf from the gem root location. Since `facter.conf` was introduced in Facter 3, the change does not affect clients that migrate from Facter 2 to Facter 4. Client that were are using Facter 3, were are using the Puppet AIO version, so they will not be affected by this change. The main advantage of this approach is that we can have different facter.conf files for different gems on Facter (e.g. the Facter from AIO agent can have a facter config, while the one from pe_installer can have another config) 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
Jira (FACT-2639) facter.conf location should be dependent on Agent AIO version
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2639 facter.conf location should be dependent on Agent AIO version Change By: Bogdan Irimie When in AIO context, Facter should read the config file from `/etc/puppetlabs/facter/facter.conf`When not in AIO context, Facter should read facter.conf from the gem root location. Since `facter.conf` was introduced in Facter 3, the change does not affect clients that migrate from Facter 2 to Facter 4. Client that were using Facter 3, were using the Puppet AIO version, so they will not be impacted affected by this change. The main advantage of this approach is that we can have different facter.conf files for different gems on Facter (e.g. the Facter from AIO agent can have a facter config, while the one from pe_installer can have another config) 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
Jira (FACT-2639) facter.conf location should be dependent on Agent AIO version
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2639 facter.conf location should be dependent on Agent AIO version Change By: Bogdan Irimie When in AIO context, Facter should read the config file from `/etc/puppetlabs/facter/facter.conf`When not in AIO context, Facter should read facter.conf from the gem root location. Since `facter.conf` was introduced in Facter 3, the change does not affect clients that migrate from Facter 2 to Facter 4. Client that were using Facter 3, were using the Puppet AIO version, so they will not be impacted by this change. The main advantage of this approach is that we can have different facter.conf files for different gems on Facter (e.g. the Facter from AIO agent can have a facter config, while the one from pe_installer can have another config) 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
Jira (FACT-2639) facter.conf location should be dependent on Agent AIO version
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2639 facter.conf location should be dependent on Agent AIO version Issue Type: Task Assignee: Unassigned Created: 2020/05/28 1:22 AM Priority: Normal Reporter: Bogdan Irimie When in AIO context, Facter should read the config file from `/etc/puppetlabs/facter/facter.conf` When not in AIO context, Facter should read facter.conf from the gem root location. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2638) Investigate if we can use facter-ng.gemspec to specify AIO version
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2638 Investigate if we can use facter-ng.gemspec to specify AIO version Change By: Bogdan Irimie Issue Type: Bug Task 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.360268.1590653662000.72023.1590653760030%40Atlassian.JIRA.
Jira (FACT-2638) Investigate if we can use facter-ng.gemspec to specify AIO version
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2638 Investigate if we can use facter-ng.gemspec to specify AIO version Issue Type: Bug Assignee: Unassigned Created: 2020/05/28 1:14 AM Priority: Normal Reporter: Bogdan Irimie facter-ng.gemspec is used to build the gem that will be included in the Puppet AIO build. We want to investigate if we can specify directly (through some variables) or indirectly (through a path to a file) the Puppet AIO version. `aio_agent_version` fact could use the Puppet AIO information Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10511) Sensitive data type is lost when declaring multiple resources using title arrays
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10511 Sensitive data type is lost when declaring multiple resources using title arrays Change By: Mihai Buzgau Story Points: 3 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.358908.1589483014000.72016.1590652680043%40Atlassian.JIRA.
Jira (PUP-10511) Sensitive data type is lost when declaring multiple resources using title arrays
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10511 Sensitive data type is lost when declaring multiple resources using title arrays Change By: Mihai Buzgau Sprint: NW - 2020-06-10 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.358908.1589483014000.72017.1590652680087%40Atlassian.JIRA.
