Jira (PUP-10525) puppet apply should set trusted['external']

2020-05-21 Thread Enis Inan (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Enis Inan commented on  PUP-10525  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet apply should set trusted['external']   
 

  
 
 
 
 

 
 Reid Vandewiele Is there a practical reason why we can't move it over to main? Something like "if we move it to main, then it won't work in this scenario"?  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-10525) puppet apply should set trusted['external']

2020-05-21 Thread Reid Vandewiele (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Reid Vandewiele commented on  PUP-10525  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet apply should set trusted['external']   
 

  
 
 
 
 

 
 Enis Inan interesting, sounds like that should support the dev/test use case. Either set trusted_external_command in the user/main section, or pass it on the CLI. For the servicenow_integration specifically I don't at first blush believe we should move it from the master section... I kind of feel like it shouldn't happen for manual invocations of apply unless intentionally invoked.  
 

  
 
 
 
 

 
 
 

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


Jira (BOLT-1545) ERROR Facter::ClassDiscoverer - There is no module named Ol

2020-05-21 Thread Jarret Lavallee (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jarret Lavallee updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1545  
 
 
  ERROR Facter::ClassDiscoverer - There is no module named Ol   
 

  
 
 
 
 

 
Change By: 
 Jarret Lavallee  
 
 
CS Priority: 
 Reviewed  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-10526) pip3 package provider fails manage multiple environments

2020-05-21 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10526  
 
 
  pip3 package provider fails manage multiple environments   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Epic Link: 
 PUP-8958  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4744) Unify all default error exit statuses

2020-05-21 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning assigned an issue to Rob Browning  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4744  
 
 
  Unify all default error exit statuses   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Assignee: 
 Rob Browning  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-10528) Extend the trusted_external_command setting to support specifying directories

2020-05-21 Thread Enis Inan (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Enis Inan assigned an issue to Enis Inan  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10528  
 
 
  Extend the trusted_external_command setting to support specifying directories   
 

  
 
 
 
 

 
Change By: 
 Enis Inan  
 
 
Assignee: 
 Enis Inan  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4745) Investigate transient configure-expiration-beavior faiures

2020-05-21 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4745  
 
 
  Investigate transient configure-expiration-beavior faiures   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/05/21 1:20 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Rob Browning  
 

  
 
 
 
 

 
  
 
 
 
 
 lein test :only puppetlabs.puppetdb.acceptance.node-ttl/configure-expiration-behavior  
 
 
    
 
 
 FAIL in (configure-expiration-behavior) (node_ttl.clj:133)  
 
 
 facts don't expire/purge when expire configured to false  
 
 
 expected: (tc/after? (now) (-> result first (get "expired") parse-wire-datetime))  
 
 
   actual: (not (tc/after? #object[org.joda.time.DateTime 0x6e02ebd4 "2020-05-21T19:30:39.726Z"] nil))  
 
 
  

Jira (PUP-7814) HTTPS file sources with non-puppet-trusted certs can't be used

2020-05-21 Thread Josh Cooper (Jira)
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 (new).To support this:1. Add a new puppet setting of type {{file_or_directory}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)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this 

Jira (PUP-7814) HTTPS file sources with non-puppet-trusted certs can't be used

2020-05-21 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper assigned an issue to Josh Cooper  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7814  
 
 
  HTTPS file sources with non-puppet-trusted certs can't be used   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Assignee: 
 Josh Cooper  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-7814) HTTPS file sources with non-puppet-trusted certs can't be used

2020-05-21 Thread Josh Cooper (Jira)
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  
 
 
Sprint: 
 Platform Core KANBAN  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4744) Unify all default error exit statuses

2020-05-21 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4744  
 
 
  Unify all default error exit statuses   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/05/21 12:52 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Rob Browning  
 

  
 
 
 
 

 
 Make sure they all use cli.util/err-exit-status, and change that to something other than 1, perhaps 2 if we're already using it in some places, matching grep, and leaving 1 open for any commands that might need a non-error boolean result (as grep does).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  

Jira (PUP-10528) Extend the trusted_external_command setting to support specifying directories

2020-05-21 Thread Enis Inan (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Enis Inan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10528  
 
 
  Extend the trusted_external_command setting to support specifying directories   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/05/21 12:13 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Enis Inan  
 

  
 
 
 
 

 
 If trusted_external_command points to a directory, then for each file in the directory, 
 
If the file's executable, we can assume it's a trusted external command. That means we'll execute it, fetch its data, and store it in trusted['external'][]. 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent 

Jira (PUP-10481) Deprecate Puppet::Network::HTTP::{Connection,NoCachePool,Compression}

2020-05-21 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10481  
 
 
  Deprecate Puppet::Network::HTTP::{Connection,NoCachePool,Compression}   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Release Notes: 
 Deprecation  
 
 
Release Notes Summary: 
 The Puppet::Network::HTTP::Connection class is deprecated and will be removed in puppet 7. Calls to the Puppet::Network::HttpPool factory methods (such as http_instance) will be routed to the new HTTP client in puppet.  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-10481) Deprecate Puppet::Network::HTTP::{Connection,NoCachePool,Compression}

2020-05-21 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10481  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deprecate Puppet::Network::HTTP::{Connection,NoCachePool,Compression}   
 

  
 
 
 
 

 
 Passed CI in https://github.com/puppetlabs/puppet/commit/cdd4bddef009d34091b2bebc4b49c342cb4b333d  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-10289) Route HttpPool.connection through http client

2020-05-21 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10289  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Route HttpPool.connection through http client   
 

  
 
 
 
 

 
 Passed CI in https://github.com/puppetlabs/puppet/commit/cdd4bddef009d34091b2bebc4b49c342cb4b333d  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-10525) puppet apply should set trusted['external']

2020-05-21 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10525  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet apply should set trusted['external']   
 

  
 
 
 
 

 
 Can you change https://github.com/puppetlabs/puppetlabs-servicenow_integration/blob/master/manifests/trusted_external_command.pp#L77 to use the main section instead of master?  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-10527) Add beaker test to ensure puppet-agent service executes in the background

2020-05-21 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10527  
 
 
  Add beaker test to ensure puppet-agent service executes in the background   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/05/21 11:16 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Josh Cooper  
 

  
 
 
 
 

 
 Commit https://github.com/puppetlabs/puppet/commit/7d8b0d37664e1bdf274bfa04ccf7ef5e5ab425eb#diff-c6a03ccca02fa0c4815d03fba3017602L192-R179 disable the job that runs the daemonized agent. As a result, puppet would never run when started as a service on *nix platforms. Had this gotten out we would have had to yank the release as daemonized agents would never run, so you couldn't use puppet to fix/update them. Fortunately we noticed and fixed it before release (https://github.com/puppetlabs/puppet/commit/58c02cceda56025623ad5bc227579a9aaeddfc80) but we have some gaps in test coverage. It looks like our service test is getting skipped due to the medium tag, https://github.com/puppetlabs/puppet/blob/58c02cceda56025623ad5bc227579a9aaeddfc80/acceptance/tests/resource/service/puppet_service_management.rb#L3, though I don't think that would have been sufficient to detect this issue. We either need a new test that verifies the service can be started and run in the background or update the existing test. The success or failure of the run could be detected by the last run summary file that the agent produces or ensuring the master receives a report for that node. /cc Mihai Buzgau, John Duarte, Christopher Thorn  
 

  
 
 
 
 

 
 
 

 
 
 

Jira (PDB-4656) Adjust PDB ingest to submit commands to multiple DBs

2020-05-21 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4656  
 
 
  Adjust PDB ingest to submit commands to multiple DBs
 

  
 
 
 
 

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


Jira (PDB-4732) Adjust status/gc/migration/etc. to handle multiple write dbs

2020-05-21 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4732  
 
 
  Adjust status/gc/migration/etc. to handle multiple write dbs   
 

  
 
 
 
 

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


Jira (PDB-4654) Adjust PDB config to allow for multiple write dbs

2020-05-21 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4654  
 
 
  Adjust PDB config to allow for multiple write dbs   
 

  
 
 
 
 

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


Jira (PDB-4654) Adjust PDB config to allow for multiple write dbs

2020-05-21 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4654  
 
 
  Adjust PDB config to allow for multiple write dbs   
 

  
 
 
 
 

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


Jira (PDB-4732) Adjust status/gc/migration/etc. to handle multiple write dbs

2020-05-21 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4732  
 
 
  Adjust status/gc/migration/etc. to handle multiple write dbs   
 

  
 
 
 
 

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


Jira (PDB-4743) Finish slingshot removal

2020-05-21 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4743  
 
 
  Finish slingshot removal   
 

  
 
 
 
 

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


Jira (PDB-4743) Finish slingshot removal

2020-05-21 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning assigned an issue to Rob Browning  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4743  
 
 
  Finish slingshot removal   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Assignee: 
 Rob Browning  
 

  
 
 
 
 

 
 
 

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


Jira (PDB-4743) Finish slingshot removal

2020-05-21 Thread Rob Browning (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4743  
 
 
  Finish slingshot removal   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/05/21 9:27 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Rob Browning  
 

  
 
 
 
 

 
 
 

 
 
 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 (PUP-10526) pip3 package provider fails manage multiple environments

2020-05-21 Thread Vadym Chepkov (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vadym Chepkov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10526  
 
 
  pip3 package provider fails manage multiple environments   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/05/21 8:33 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Vadym Chepkov  
 

  
 
 
 
 

 
 Puppet Version: 6.15.0 Puppet Server Version: 6.11.1 OS Name/Version: CentOS 8 Desired Behavior: Would like to manage multiple python environments with pip3 package provider Actual Behavior: Catalog fails if you try to manage multiple environments Here is a reproducer:    
 
 
 
 
 exec { 'python env1':  
 
 
   command => "/bin/python3 -m venv --clear /opt/env1 && /opt/env1/bin/pip3 install --upgrade pip && /opt/env1/bin/pip3 install --upgrade setuptools",  
 
 
   creates => "/opt/env1/bin/activate",  
 
 
 }  
 
 
 package { 'cfn-lint':  
 
 
   ensure   => latest,  
  

Jira (PUP-10524) Puppet tests fail with facter 4

2020-05-21 Thread Bogdan Irimie (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie commented on  PUP-10524  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet tests fail with facter 4   
 

  
 
 
 
 

 
 Josh Cooper with the fixes from Melissa Stone branch (https://github.com/puppetlabs/puppet/pull/8165/files), Facter 4 master and the fix for $CHILD_STATUS https://github.com/puppetlabs/puppet/pull/8165#issuecomment-632109253 the unit test for puppet pass. A new version of Facter 4 will be released tomorrow.  
 

  
 
 
 
 

 
 
 

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


Jira (FACT-2631) Trace is not working as expected

2020-05-21 Thread Bogdan Irimie (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie assigned an issue to Bogdan Irimie  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2631  
 
 
  Trace is not working as expected   
 

  
 
 
 
 

 
Change By: 
 Bogdan Irimie  
 
 
Assignee: 
 Bogdan Irimie  
 

  
 
 
 
 

 
 
 

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


Jira (FACT-2632) Log error when we cannot load custom fact from file

2020-05-21 Thread Bogdan Irimie (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie assigned an issue to Bogdan Irimie  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2632  
 
 
  Log error when we cannot load custom fact from file   
 

  
 
 
 
 

 
Change By: 
 Bogdan Irimie  
 
 
Assignee: 
 Bogdan Irimie  
 

  
 
 
 
 

 
 
 

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


Jira (FACT-2632) Log error when we cannot load custom fact from file

2020-05-21 Thread Bogdan Irimie (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2632  
 
 
  Log error when we cannot load custom fact from file   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/05/21 5:23 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Bogdan Irimie  
 

  
 
 
 
 

 
 
 

 
 
 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 (FACT-2631) Trace is not working as expected

2020-05-21 Thread Bogdan Irimie (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2631  
 
 
  Trace is not working as expected   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/05/21 4:50 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Bogdan Irimie  
 

  
 
 
 
 

 
 Puppet Version: Puppet Server Version: OS Name/Version: Describe your issue in as much detail as possible… Describe steps to reproduce… Desired Behavior: Actual Behavior: Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. Examples: Run puppet agent with --test --trace --debug Relevant sections of /var/log/puppetlabs/puppetserver/puppetserver.log or any applicable logs from the same directory. For more detailed information turn up the server logs by upping the log level in the server's logback.xml Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig) For memory issues with server heap dumps are also helpful.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
  

Jira (PUP-10525) puppet apply should set trusted['external']

2020-05-21 Thread Enis Inan (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Enis Inan commented on  PUP-10525  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet apply should set trusted['external']   
 

  
 
 
 
 

 
 Yes, as part of https://github.com/puppetlabs/puppetlabs-servicenow_integration where we have a servicenow.rb script that returns the external data.  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-1289) Ability to manage a windows service's user account and password

2020-05-21 Thread Luchian Nemes (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Luchian Nemes assigned an issue to Luchian Nemes  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-1289  
 
 
  Ability to manage a windows service's user account and password   
 

  
 
 
 
 

 
Change By: 
 Luchian Nemes  
 
 
Assignee: 
 Luchian Nemes  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-10524) Puppet tests fail with facter 4

2020-05-21 Thread Bogdan Irimie (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie assigned an issue to Bogdan Irimie  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10524  
 
 
  Puppet tests fail with facter 4   
 

  
 
 
 
 

 
Change By: 
 Bogdan Irimie  
 
 
Assignee: 
 Bogdan Irimie  
 

  
 
 
 
 

 
 
 

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


Jira (FACT-2619) External fact caching

2020-05-21 Thread Bogdan Irimie (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie assigned an issue to Florin Dragos  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2619  
 
 
  External fact caching   
 

  
 
 
 
 

 
Change By: 
 Bogdan Irimie  
 
 
Assignee: 
 Bogdan Irimie Florin Dragos  
 

  
 
 
 
 

 
 
 

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