Jira (FACT-3173) Facter option store does not reset after Facter is reset

2023-01-05 Thread Aria Li (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Aria Li created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-3173  
 
 
  Facter option store does not reset after Facter is reset   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2023/01/05 4:55 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Aria Li  
 

  
 
 
 
 

 
 Facter.reset should reset Facter back to its default configuration but OptionStore in Facter is not reset when Facter.reset or Facter.clear are called.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)  
 
 

 
   

Jira (PDB-5571) ini4j vulnerability

2023-01-05 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5571  
 
 
  ini4j vulnerability   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Rob Browning  
 
 
Created: 
 2023/01/05 2:11 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Rob Browning  
 

  
 
 
 
 

 
 clj-kitchensink imports a vulnerable version of ini4j. See https://security.snyk.io/vuln/SNYK-JAVA-ORGINI4J-3042998 It should be updated, promoted, and updated in clj-parent.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)  
 
 

 
   
  

Jira (PDB-5570) Update postgres jdbc driver to 42.4.3 to address security issue

2023-01-05 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5570  
 
 
  Update postgres jdbc driver to 42.4.3 to address security issue   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Rob Browning  
 
 
Created: 
 2023/01/05 2:09 PM  
 
 
Fix Versions: 
 PDB 7.12.1, PDB 8.0.0  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Rob Browning  
 

  
 
 
 
 

 
 See https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-562r-vg33-8x8h#event-84471 main branch (promotes into PE 2021.7.x and PE 2023.0 (main)): https://github.com/puppetlabs/clj-parent/blob/0f26ad7841370f3ccb70431bb7f6c263626cada1/project.clj#L100 to 42.4.3 4.x branch (promotes into PE 2019.8.x): https://github.com/puppetlabs/clj-parent/blob/c2bb8c9cf61ba6c1c0fa2b6285ab3969894fa5b9/project.clj#L97 to 42.4.3 and ensure the parent bump is promoted into all the projects promoted into PE.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
   

Jira (PDB-5569) RHEL9 packages for puppetdb

2023-01-05 Thread Pat Riehecky (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pat Riehecky created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5569  
 
 
  RHEL9 packages for puppetdb   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 PuppetDB  
 
 
Created: 
 2023/01/05 11:14 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Pat Riehecky  
 

  
 
 
 
 

 
 Is there an expected timetable for puppetdb to be packaged for RHEL9?  The RHEL9 platform has been out for a while  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)  
 
   

Jira (PDB-5568) Query failure when ordering by json element

2023-01-05 Thread Austin Blatt (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5568  
 
 
  Query failure when ordering by json element
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Release Notes Summary: 
 Fix issue where queries ordering by a fact value failed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)  
 
 

 
   
 

  
 

  
 

   





-- 
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.477993.1672942656000.69984.1672943760260%40Atlassian.JIRA.


Jira (PDB-5568) Query failure when ordering by json element

2023-01-05 Thread Austin Blatt (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5568  
 
 
  Query failure when ordering by json element
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Release Notes: 
 Bug Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)  
 
 

 
   
 

  
 

  
 

   





-- 
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.477993.1672942656000.69977.1672943580089%40Atlassian.JIRA.


Jira (FACT-3151) Facter fails on the `/etc/os-release` that contains the '#`

2023-01-05 Thread Michael Hashizume (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Hashizume updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-3151  
 
 
  Facter fails on the `/etc/os-release` that contains the '#`   
 

  
 
 
 
 

 
Change By: 
 Michael Hashizume  
 
 
Team: 
 Phoenix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)  
 
 

 
   
 

  
 

  
 

   





-- 
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.469451.1664227327000.69975.1672943400186%40Atlassian.JIRA.


Jira (PDB-5568) Query failure when ordering by json element

2023-01-05 Thread Austin Blatt (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5568  
 
 
  Query failure when ordering by json element
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Sprint: 
 Skeletor 01/18/2023  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)  
 
 

 
   
 

  
 

  
 

   





-- 
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.477993.1672942656000.69972.1672942980039%40Atlassian.JIRA.


Jira (PDB-5568) Query failure when ordering by json element

2023-01-05 Thread Austin Blatt (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5568  
 
 
  Query failure when ordering by json element
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Austin Blatt  
 
 
Created: 
 2023/01/05 10:17 AM  
 
 
Fix Versions: 
 PDB 7.12.0  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Austin Blatt  
 

  
 
 
 
 

 
 Error  
 
 
 
 
 2023-01-05 09:20:41,327 ERROR [qtp1721282939-73] [p.p.middleware] #error {  
 
 
  :cause ERROR: syntax error at or near "_"  
 
 
   Position: 822  
 
 
  :via  
 
 
  [{:type org.postgresql.util.PSQLException  
 
 
:message ERROR: syntax error at or near "_"  
 
  

Jira (PUP-11689) Enable strict mode by default

2023-01-05 Thread Morgan Rhodes (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Morgan Rhodes updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-11689  
 
 
  Enable strict mode by default   
 

  
 
 
 
 

 
Change By: 
 Morgan Rhodes  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)  
 
 

 
   
 

  
 

  
 

   





-- 
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.476842.1670862344000.69962.1672942260031%40Atlassian.JIRA.


Jira (PUP-11689) Enable strict mode by default

2023-01-05 Thread Morgan Rhodes (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Morgan Rhodes updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-11689  
 
 
  Enable strict mode by default   
 

  
 
 
 
 

 
Change By: 
 Morgan Rhodes  
 

  
 
 
 
 

 
 Puppet supports various strict language related settings. These were added in 2016 (puppet 4.x) and it's time to enable strict behavior by default.[strict|https://github.com/puppetlabs/puppet/blob/381a3e2b2e6858570fcc6e755bfae9eeff1226f1/lib/puppet/defaults.rb#L191][strict_variables|https://github.com/puppetlabs/puppet/blob/381a3e2b2e6858570fcc6e755bfae9eeff1226f1/lib/puppet/defaults.rb#L2212] A good thing to verify - take a module like stdlib, test against puppet8 gem, change the setting for strict variables, and make sure the spec tests still pass. Note you can use the PUPPET_GEM_VERSION to pin to a local checkout of puppet rather than building a gem.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails 

Jira (PUP-8639) need seamless way to replace expiring CA certificate

2023-01-05 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-8639  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: need seamless way to replace expiring CA certificate   
 

  
 
 
 
 

 
 I'm going to close this as a dup of PUP-10639 as that's what we're using internally to track this issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)  
 
 

 
   
 

  
 

  
 

   





-- 
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.244671.1523046645000.69942.1672939380036%40Atlassian.JIRA.


Jira (PUP-10639) renew cached Puppet CA on Puppet client

2023-01-05 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10639  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: renew cached Puppet CA on Puppet client   
 

  
 
 
 
 

 
 Yep, that makes sense to me.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)  
 
 

 
   
 

  
 

  
 

   





-- 
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.369858.1597923633000.69941.1672939320036%40Atlassian.JIRA.


Jira (PUP-11695) Windows package uninstall uses msi provider when exe provider available

2023-01-05 Thread GeorgesZ (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 GeorgesZ updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-11695  
 
 
  Windows package uninstall uses msi provider when exe provider available   
 

  
 
 
 
 

 
Change By: 
 GeorgesZ  
 

  
 
 
 
 

 
 *Puppet Version:* 7.20.0{*}Puppet Server Version:{*} ** 7.20.0*OS Name/Version:* Windows 10Using the package resource, version 2.1.802 of Microsoft .NET SDK x86 cannot be uninstalled like the x64 architecture or other versions (eg: 2.1.403, 5.0.102, 5.0.401).Installers for Microsoft .NET SDK can be downloaded using a url like this [https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/sdk-${version}-windows-x86-installer|https://dotnet.microsoft.com/en-us/download/dotnet] and can be installed/uninstalled using something like this:{code: java puppet }package { "Microsoft .NET ${optional_core}SDK ${version} (x86)":  ensure            => $ensure,  source            => "${download_folder}/dotnet-sdk-${version}-win-x86.exe",  install_options   => ['/install', '/passive', '/norestart'],  uninstall_options => ['/uninstall', '/passive', '/norestart'],}package { "Microsoft .NET ${optional_core}SDK ${version} (x64)":  ensure            => $ensure,  source            => "${download_folder}/dotnet-sdk-${version}-win-x86.exe",  install_options   => ['/install', '/passive', '/norestart'],  uninstall_options => ['/uninstall', '/passive', '/norestart'],}{code}except for version 2.1.802 that MUST be installed/uninstalled using something like this:{code: java puppet } if $ensure == absent {exec { '"C:\\ProgramData\\Package Cache\\{92a4ca67-9d75-4067-8522-e684fd033096}\\dotnet-sdk-2.1.802-win-x86.exe" /uninstall /passive /norestart':_onlyif_ => 'C:\\Windows\\System32\\reg.exe query HKLM\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\{92a4ca67-9d75-4067-8522-e684fd033096}',  }} else { package { 'Microsoft .NET Core SDK 2.1.802 (x86)':  ensure            =>  absent  present ,  source            => "${download_folder}/dotnet-sdk-2.1.802-win-x86.exe",  install_options   => ['/install', '/passive', '/norestart'],   uninstall_options => undef,   } }package { 'Microsoft .NET Core SDK 2.1.802 (x64)':  ensure            =>  absent  $ensure ,  source            => "${download_folder}/dotnet-sdk-2.1.802-win-x64.exe",  install_options   => ['/install', '/passive', '/norestart'],  uninstall_options => ['/uninstall', '/passive', '/norestart'],}{code}The cause seems to be that the package resource uninstalls Microsoft .NET SDK version 2.1.802 x86 using the msi provider:{noformat}msiexec.exe /qn /norestart /x {F56405A6-5942-4EC9-A446-54167AA57752} $uninstall_options{noformat}when it could use the exe provider:{noformat}"C:\ProgramData\Package Cache\{92a4ca67-9d75-4067-8522-e684fd033096}\dotnet-sdk-2.1.802-win-x86.exe"  /uninstall $uninstall_options{noformat}I am wondering if the root cause could be [this|https://github.com/puppetlabs/puppet/blob/main/lib/puppet/provider/package/windows/package.rb#L28] where the MSI provider may be used before the EXE provider. It seems that in this case, the Microsoft .NET SDK EXE installer uses 

Jira (PUP-11688) Allow options to be passed to the pkg provider

2023-01-05 Thread Alvin Rodis (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alvin Rodis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-11688  
 
 
  Allow options to be passed to the pkg provider   
 

  
 
 
 
 

 
Change By: 
 Alvin Rodis  
 
 
Zendesk Ticket Count: 
 1  
 
 
Zendesk Ticket IDs: 
 50465  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)  
 
 

 
   
 

  
 

  
 

   





-- 
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.476804.1670534477000.69912.1672923060029%40Atlassian.JIRA.


Jira (PUP-11688) Allow options to be passed to the pkg provider

2023-01-05 Thread Alvin Rodis (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alvin Rodis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-11688  
 
 
  Allow options to be passed to the pkg provider   
 

  
 
 
 
 

 
Change By: 
 Alvin Rodis  
 
 
Labels: 
 jira_escalated  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)  
 
 

 
   
 

  
 

  
 

   





-- 
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.476804.1670534477000.69911.167292369%40Atlassian.JIRA.


Jira (PUP-10639) renew cached Puppet CA on Puppet client

2023-01-05 Thread Tim Meusel (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Meusel commented on  PUP-10639  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: renew cached Puppet CA on Puppet client   
 

  
 
 
 
 

 
 Hi, as a first step, what about a refresh interval, like we have it for the CRL, to update a not expired CA cert? The agent can establish the usual HTTPS connection and if that works, download a new CA cert. That would enable people to use short-lived certificated and automate their rollover.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)  
 
 

 
   
 

  
 

  
 

   





-- 
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.369858.1597923633000.69883.1672911360046%40Atlassian.JIRA.