Jira (PUP-10436) Remove strict_hostname_checking

2020-08-10 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10436  
 
 
  Remove strict_hostname_checking   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Fix Version/s: 
 PUP 7.0.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.356464.1587616816000.13221.1597098600109%40Atlassian.JIRA.


Jira (PUP-10436) Remove strict_hostname_checking

2020-08-10 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10436  
 
 
  Remove strict_hostname_checking   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Team: 
 Coremunity 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.356464.1587616816000.13220.1597098600059%40Atlassian.JIRA.


Jira (PUP-10473) Remove legacy auth.conf support

2020-08-10 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10473  
 
 
  Remove legacy auth.conf support   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Team: 
 Froyo Coremunity  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-8682) Allow disabling settings catalog

2020-08-10 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8682  
 
 
  Allow disabling settings catalog   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 

  
 
 
 
 

 
 When initializing Puppet as a library to handle master requests I do not want the settings catalog applied every time. There should be a setting that I can set when initializing Puppet that disables setting catalog compilation and application.* Are there packaging changes needed in FOSS if we do this? For example, we use the settings catalog to manage permissions on the codedir, which packaging creates as root. This ticket tracks adding the ability to prevent the settings catalog from being applied, while SERVER-2240 tracks puppetserver opting in to that behavior.  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (PUP-8682) Allow disabling settings catalog

2020-08-10 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8682  
 
 
  Allow disabling settings catalog   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 

  
 
 
 
 

 
 When initializing Puppet as a library to handle master requests I do not want the settings catalog applied every time. There should be a setting that I can set when initializing Puppet that disables setting catalog compilation and application. * Are there packaging changes needed in FOSS if we do this? For example, we use the settings catalog to manage permissions on the codedir, which packaging creates as root.  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-10436) Remove strict_hostname_checking

2020-08-10 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer commented on  PUP-10436  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remove strict_hostname_checking   
 

  
 
 
 
 

 
 This should be straightforward. The setting is in Ruby.  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-9648) Drop PSON support

2020-08-10 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9648  
 
 
  Drop PSON support   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 

  
 
 
 
 

 
 Puppet prefers JSON but will fallback to PSON if there are binary fact values or if the catalog contains binary content, such as the {{file}} resource's {{content => binary_file('/path/to/bin')}}. Now that rich data is supported and enabled by default, we should look into eliminating PSON support.* Where does the fallback code live? Is it centralized or scattered around?* There are some [mentions of PSON|https://github.com/puppetlabs/puppetserver/blob/master/src/clj/puppetlabs/services/ca/certificate_authority_core.clj#L163-L166] in the CA endpoint code. This is to support agents requesting certs in PSON. Can we drop this support?* In what version did we add real rich data support that doesn't require PSON? That version is likely the oldest we can support if we do this. We think this happened in  [  Puppet 6 |https://tickets.puppetlabs.com/browse/PUP-8587] , which is likely too recent for this to be doable.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 
 

Jira (PUP-9648) Drop PSON support

2020-08-10 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9648  
 
 
  Drop PSON support   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 

  
 
 
 
 

 
 Puppet prefers JSON but will fallback to PSON if there are binary fact values or if the catalog contains binary content, such as the {{file}} resource's {{content => binary_file('/path/to/bin')}}. Now that rich data is supported and enabled by default, we should look into eliminating PSON support.* Where does the fallback code live? Is it centralized or scattered around?* There are some [mentions of PSON|https://github.com/puppetlabs/puppetserver/blob/master/src/clj/puppetlabs/services/ca/certificate_authority_core.clj#L163-L166] in the CA endpoint code. This is to support agents requesting certs in PSON. Can we drop this support?* In what version did we add real rich data support that doesn't require PSON? That version is likely the oldest we can support if we do this.  We think this happened in Puppet 6, which is likely too recent for this to be doable.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

Jira (PUP-9648) Drop PSON support

2020-08-10 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9648  
 
 
  Drop PSON support   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 

  
 
 
 
 

 
 Puppet prefers JSON but will fallback to PSON if there are binary fact values or if the catalog contains binary content, such as the {{file}} resource's {{content => binary_file('/path/to/bin')}}. Now that rich data is supported and enabled by default, we should look into eliminating PSON support.* Where does the fallback code live? Is it centralized or scattered around?* There are some [mentions of PSON|https://github.com/puppetlabs/puppetserver/blob/master/src/clj/puppetlabs/services/ca/certificate_authority_core.clj#L163-L166] in the CA endpoint code. This is to support agents requesting certs in PSON. Can we drop this support? * In what version did we add real rich data support that doesn't require PSON? That version is likely the oldest we can support if we do this.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are 

Jira (PUP-9648) Drop PSON support

2020-08-10 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer commented on  PUP-9648  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Drop PSON support   
 

  
 
 
 
 

 
 I think we might need to make a call on how far back we want to support for agents if we do this. If we are going to say "all of them forever", then this ticket should be closed, because it's not possible to 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.305621.1555690549000.13158.1597096800212%40Atlassian.JIRA.


Jira (PUP-9648) Drop PSON support

2020-08-10 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9648  
 
 
  Drop PSON support   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 

  
 
 
 
 

 
 Puppet prefers JSON but will fallback to PSON if there are binary fact values or if the catalog contains binary content, such as the {{file}} resource's {{content => binary_file('/path/to/bin')}}. Now that rich data is supported and enabled by default, we should look into eliminating PSON support. * Where does the fallback code live? Is it centralized or scattered around?* There are some [mentions of PSON|https://github.com/puppetlabs/puppetserver/blob/master/src/clj/puppetlabs/services/ca/certificate_authority_core.clj#L163-L166] in the CA endpoint code. This is to support agents requesting certs in PSON. Can we drop this support?  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (PUP-10615) Add facts and vars back to PAL ScriptCompiler scope

2020-08-10 Thread Tom Beech (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10615  
 
 
  Add facts and vars back to PAL ScriptCompiler scope   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Tom Beech  
 
 
Created: 
 2020/08/10 1:57 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Tom Beech  
 

  
 
 
 
 

 
 Puppet Version: 6.15.0 - 6.17.0 As part of work on Bolt, PUP-10397 removed vars and facts for the current node from PAL's script compiler. This resulted in a breaking change to a public API, affecting downstream projects that rely on PAL. The script compiler should make the current node's vars and facts available again. Desired Behavior: **PAL's script compiler should have access to vars and facts for the node running the script. Actual Behavior: PAL's script compiler does not have access to the vars and facts for the node running the script, causing project's that rely on the PAL API to lose access to this data.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
  

Jira (PUP-10614) Check if package is installed before enforcing configured version

2020-08-10 Thread Corey Benefrayim (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Corey Benefrayim updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10614  
 
 
  Check if package is installed before enforcing configured version   
 

  
 
 
 
 

 
Change By: 
 Corey Benefrayim  
 

  
 
 
 
 

 
 Customer has asked me to create a feature request to allow them to check if a package is installed before puppet enforces the configured version.For example, customer would like to be able to do something like this: {quote}  $packages = {  'puppet' => \{ ensure => '6.14.0-1.el7' },  'ntp' => \{ ensure => '1.5.3-1' },}keys($pkg_hash).each |Integer $index, String $pkg| {  if ! $facts['_puppet_inventory_1']['packages'][$pkg]['1'] {    $upgrade=undef  }  elsif versioncmp($facts['_puppet_inventory_1']['packages'][$pkg]['1'], ${attributes['ensure']}) == "1" {    $upgrade=False  }  elsif versioncmp($facts['_puppet_inventory_1']['packages'][$pkg]['1'], ${attributes['ensure']}) == "-1" {      $upgrade=True  }if ($upgrade == undef) or ($upgrade) {  package { $pkg:    ensure => $attributes['ensure'],  }}} {quote}    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
   

Jira (PUP-10614) Check if package is installed before enforcing configured version

2020-08-10 Thread Austin Boyd (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Boyd updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10614  
 
 
  Check if package is installed before enforcing configured version   
 

  
 
 
 
 

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


Jira (PUP-10614) Check if package is installed before enforcing configured version

2020-08-10 Thread Austin Boyd (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Boyd updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10614  
 
 
  Check if package is installed before enforcing configured version   
 

  
 
 
 
 

 
Change By: 
 Austin Boyd  
 
 
Zendesk Ticket Count: 
 1  
 
 
Zendesk Ticket IDs: 
 40361  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-10614) Check if package is installed before enforcing configured version

2020-08-10 Thread Corey Benefrayim (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Corey Benefrayim created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10614  
 
 
  Check if package is installed before enforcing configured version   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Types and Providers  
 
 
Created: 
 2020/08/10 1:37 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Corey Benefrayim  
 

  
 
 
 
 

 
 Customer has asked me to create a feature request to allow them to check if a package is installed before puppet enforces the configured version. For example, customer would like to be able to do something like this: 

$packages =  

Unknown macro: {   'puppet' => { ensure => '6.14.0-1.el7' } 
 
,   'ntp' => { ensure => '1.5.3-1' }, } 
keys($pkg_hash).each |Integer $index, String $pkg| {   if ! $facts['_puppet_inventory_1']['packages'][$pkg]['1']  

Unknown macro: {     $upgrade=undef   } 
 
  elsif versioncmp($facts['_puppet_inventory_1']['packages'][$pkg]['1'], ${attributes['ensure']}) == "1"  

Unknown macro: {     $upgrade=False   } 
 
  elsif versioncmp($facts['_puppet_inventory_1']['packages'][$pkg]['1'], ${attributes['ensure']}) == "-1"  

Jira (PUP-9262) Remove fine grained file and environment timeouts

2020-08-10 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer commented on  PUP-9262  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remove fine grained file and environment timeouts   
 

  
 
 
 
 

 
 Josh Cooper I confirmed with Froyo that we still consider https://tickets.puppetlabs.com/browse/PUP-8014 a pre-req for this work. Do you have a sense of what implementing environment_ttl would entail?  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4269) Integer comparisons in PQL can overflow the Java int type

2020-08-10 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4269  
 
 
  Integer comparisons in PQL can overflow the Java int type   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Fix Version/s: 
 PDB 6.11.4  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4269) Integer comparisons in PQL can overflow the Java int type

2020-08-10 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4269  
 
 
  Integer comparisons in PQL can overflow the Java int type   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Release Notes: 
 Bug Fix  
 
 
Release Notes Summary: 
 Integers in PQL queries can now range from -9223372036854775808 to 9223372036854775807 (64-bit), matching the Puppet language.  Previously they were unintentionally limited to range from -2147483648 to 2147483647 (32-bit).https://puppet.com/docs/puppet/6.17/lang_data_number.html#lang_data_number_integer_type  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4810) Audit thread pool use and try to ensure we avoid silent failures

2020-08-10 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4810  
 
 
  Audit thread pool use and try to ensure we avoid silent failures   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
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.365405.1594312361000.12395.1597075380100%40Atlassian.JIRA.


Jira (PDB-4655) Audit error handling/shutdown behavior when PDB is broadcasting

2020-08-10 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4655  
 
 
  Audit error handling/shutdown behavior when PDB is broadcasting   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Release Notes: 
 Not Needed  
 
 
Issue Type: 
 New Feature Improvement  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4765) Audit/adjust read-database use in light of command broadcast

2020-08-10 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4765  
 
 
  Audit/adjust read-database use in light of command broadcast   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Release Notes: 
 Not Needed  
 
 
Issue Type: 
 Bug Improvement  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4831) Finish initial pdbext adjustments for command broadcast

2020-08-10 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4831  
 
 
  Finish initial pdbext adjustments for command broadcast   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Fix Version/s: 
 PDB 6.11.4  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4808) Check the validity of the read database and migrate all write dbs

2020-08-10 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4808  
 
 
  Check the validity of the read database and migrate all write dbs   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Fix Version/s: 
 PDB 6.11.4  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4783) Disallow sync with broadcast in pdbext

2020-08-10 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4783  
 
 
  Disallow sync with broadcast in pdbext   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Fix Version/s: 
 PDB 6.11.4  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4765) Audit/adjust read-database use in light of command broadcast

2020-08-10 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4765  
 
 
  Audit/adjust read-database use in light of command broadcast   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Fix Version/s: 
 PDB 6.11.4  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4810) Audit thread pool use and try to ensure we avoid silent failures

2020-08-10 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4810  
 
 
  Audit thread pool use and try to ensure we avoid silent failures   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Fix Version/s: 
 PDB 6.11.4  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4655) Audit error handling/shutdown behavior when PDB is broadcasting

2020-08-10 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4655  
 
 
  Audit error handling/shutdown behavior when PDB is broadcasting   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Fix Version/s: 
 PDB 6.11.4  
 

  
 
 
 
 

 
 
 

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


Jira (FACT-2741) Floating point numbers with no decimals have a .0 displayed

2020-08-10 Thread Andrei Filipovici (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrei Filipovici created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2741  
 
 
  Floating point numbers with no decimals have a .0 displayed   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/08/10 7:47 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Andrei Filipovici  
 

  
 
 
 
 

 
 On facter 4 floating point numbers with no decimals are displayed like this: 4.0. On facter 3, the '.0' is not displayed anymore.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
  

Jira (PUP-10054) Incorrect function in documentation examples for strip and rstrip functions

2020-08-10 Thread Claire Cadman (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Claire Cadman commented on  PUP-10054  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Incorrect function in documentation examples for strip and rstrip functions   
 

  
 
 
 
 

 
 Josh Cooper I've made a PR here: https://github.com/puppetlabs/puppet/pull/8266  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-5758) Remove usage of win32-service gem (if applicable)

2020-08-10 Thread Gheorghe Popescu (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gheorghe Popescu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-5758  
 
 
  Remove usage of win32-service gem (if applicable)   
 

  
 
 
 
 

 
Change By: 
 Gheorghe Popescu  
 
 
Release Notes Summary: 
 Remove Puppet dependency on win32-process gem and implement the needed functionality using FFI.  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-10597) Remove deprecated held from apt provider

2020-08-10 Thread Dorin Pleava (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava assigned an issue to Dorin Pleava  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10597  
 
 
  Remove deprecated held from apt provider   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Assignee: 
 Dorin Pleava  
 

  
 
 
 
 

 
 
 

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


Jira (FACT-2730) Fix networking on Solaris 11 SPARC

2020-08-10 Thread Andrei Filipovici (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrei Filipovici updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2730  
 
 
  Fix networking on Solaris 11 SPARC   
 

  
 
 
 
 

 
Change By: 
 Andrei Filipovici  
 

  
 
 
 
 

 
 The backtrace is attached .This is blocked until the packaging for FFI library is fixed in puppet-agent.  
 

  
 
 
 
 

 
 
 

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


Jira (FACT-2731) Fix mountpoints fact on Solaris 11 SPARC

2020-08-10 Thread Andrei Filipovici (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrei Filipovici updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2731  
 
 
  Fix mountpoints fact on Solaris 11 SPARC   
 

  
 
 
 
 

 
Change By: 
 Andrei Filipovici  
 

  
 
 
 
 

 
 The backtrace is attached .This is blocked until the packaging for FFI library is fixed in puppet-agent.  
 

  
 
 
 
 

 
 
 

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