Jira (BOLT-195) Bolt should support the sensitive type

2019-01-23 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith commented on  BOLT-195  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Bolt should support the sensitive type   
 

  
 
 
 
 

 
 Is there more work still needed here?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-211) Support ssh through a jump box

2019-01-23 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith commented on  BOLT-211  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support ssh through a jump box   
 

  
 
 
 
 

 
 Is this satisfied by proxyjump?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-744) Doc errors in "run_script" examples

2019-01-23 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-744  
 
 
  Doc errors in "run_script" examples   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Labels: 
 docs  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-835) hiera-config missing in Bolt Configuration documentation

2019-01-23 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-835  
 
 
  hiera-config missing in Bolt Configuration documentation   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Labels: 
 docs  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1051) Syntax corrections to Writing Tasks doc

2019-01-23 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1051  
 
 
  Syntax corrections to Writing Tasks doc   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Labels: 
 docs  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-4256) Installing with PuppetDB module creates dependency cycle with latest apt module

2019-01-23 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4256  
 
 
  Installing with PuppetDB module creates dependency cycle with latest apt module   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 

  
 
 
 
 

 
 With the latest release of the puppetlabs-apt module, beaker acceptance test presuites that install PDB via the puppetdb module have started failing with the following:{code}Error: Found 1 dependency cycle:(Package[apt-transport-https] => Apt::Source[apt.postgresql.org] => Package[apt-transport-https])\nTry the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz{code}Pre-suite from puppetserver: https://github.com/puppetlabs/puppetserver/blob/master/acceptance/suites/pre_suite/foss/95_install_pdb.rbFrom [~chuck] in Slack:Could be this line in puppetlabs-postgresql if `Package[apt-transport-https]` ended up tagged with `postgresql`:https://github.com/puppetlabs/puppetlabs-postgresql/blob/master/manifests/repo/apt_postgresql_org.pp#L30Hmm, https://github.com/puppetlabs/puppetlabs-apt/blob/master/manifests/source.pp#L91-L93 is causing me to give it some side-eye.I'm not sure what the containment path for that would end up being. But if the `apt::source` in `class postgresql::repo::apt_postgresql_org` ends up being the first one evaluated, then that `ensure_package` could end up creating `Package[apt-transport-https]` that is contained within `postgresql::repo::apt_postgresql_org`Which means it would end up with a `postgresql` tag because we take the name of the containing class, tag the resource with it, then recursively split on `::` and tag the resource with the remainder. Or something similarly ridiculous.Could comment out apt_postgresql_org.pp#L30 and see if the problem goes away. If it does, then that's probably it.Not sure what the correct path is to fix this, but both Server and PuppetDB's acceptance testing will fail until we do.  Note that this is only failing on Debian 8 for puppetserver at least.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  

Jira (PDB-4256) Installing with PuppetDB module creates dependency cycle with latest apt module

2019-01-23 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4256  
 
 
  Installing with PuppetDB module creates dependency cycle with latest apt module   
 

  
 
 
 
 

 
Issue Type: 
  CI Blocker  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/01/23 5:16 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Maggie Dreyer  
 

  
 
 
 
 

 
 With the latest release of the puppetlabs-apt module, beaker acceptance test presuites that install PDB via the puppetdb module have started failing with the following:  
 
 
 
 
 Error: Found 1 dependency cycle:  
 
 
 (Package[apt-transport-https] => Apt::Source[apt.postgresql.org] => Package[apt-transport-https])\nTry the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz
  
 
 
 
  Pre-suite from puppetserver: https://github.com/puppetlabs/puppetserver/blob/master/acceptance/suites/pre_suite/foss/95_install_pdb.rb From Charlie Sharpsteen in Slack: Could be this line in puppetlabs-postgresql if `Package[apt-transport-https]` ended up tagged with `postgresql`: https://github.com/puppetlabs/puppetlabs-postgresql/blob/master/manifests/repo/apt_postgresql_org.pp#L30 Hmm, https://github.com/puppetlabs/puppetlabs-apt/blob/master/manifests/source.pp#L91-L93 is causing me to give it some side-eye. I'm not sure what the containment path for that would end up being. But if the `apt::source` in `class postgresql::repo::apt_postgresql_org` ends up being the first one evaluated, then that `ensure_package` could end up 

Jira (PDB-4214) --data-urlencode 'pretty=true' does not work

2019-01-23 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt assigned an issue to Austin Blatt  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4214  
 
 
  --data-urlencode 'pretty=true' does not work   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Assignee: 
 Austin Blatt  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9463) Save X509 objects with the correct permissions

2019-01-23 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9463  
 
 
  Save X509 objects with the correct permissions   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/01/23 3:54 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Josh Cooper  
 

  
 
 
 
 

 
 When running as root/privileged user, and the Puppet[:user]/Puppet[:group] accounts exist, then puppet should set the owner and group for many of its SSL related files to that user/group. This is needed so that puppetserver running on the same host can share the client cert/private key. When running as root/privileged user, and the Puppet[:user]/Puppet[:group] accounts don't exist, then it should leave the owner/group as is, but enforce the mode as defined in the settings object, eg :hostprivkey. When running as a non-privileged user, it should enforce the mode as defined in the settings object, eg :hostprivkey.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
  

Jira (PUP-9462) Add locking to the state machine

2019-01-23 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9462  
 
 
  Add locking to the state machine   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/01/23 3:48 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Josh Cooper  
 

  
 
 
 
 

 
 Prevent concurrent puppet processes, eg puppet agent -t and background puppet service from running the state machine at the same time. For example, if two process race, then the first process may write the private key, while the second process overwrites the key, and then the first process submits the CSR.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

Jira (PUP-9461) Load available X509 objects

2019-01-23 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9461  
 
 
  Load available X509 objects   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/01/23 3:44 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Josh Cooper  
 

  
 
 
 
 

 
 During normal puppet execution, load whatever key/cert-related objects are available (if any) and make them available in Puppet's context system. For the puppet agent, puppet ssl and puppet device applications, run the state machine.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 

Jira (PUP-9460) Update HTTP clients to use new HttpPool method

2019-01-23 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9460  
 
 
  Update HTTP clients to use new HttpPool method   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Team: 
 Coremunity  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9460) Update HTTP clients to use new HttpPool method

2019-01-23 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9460  
 
 
  Update HTTP clients to use new HttpPool method   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/01/23 3:42 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Josh Cooper  
 

  
 
 
 
 

 
 Update HTTP clients (indirector rest requests, configurer, remote file sources, server status) to use the new HttpPool method for creating a connection from a host, port, and SSLContext.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 

Jira (PUP-9459) Create SSL state machine for generating a client cert

2019-01-23 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9459  
 
 
  Create SSL state machine for generating a client cert   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/01/23 3:41 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Josh Cooper  
 

  
 
 
 
 

 
 Create an SSL state machine for loading/generating a private key, loading/submitting a CSR, and loading/downloading a client cert. The state machine should verify the consistency of the data before committing changes to disk and moving to the next state. For example, if we download the client cert, but its public key doesn't match our private key, then the cert should be discarded and an error generated. Connections should always authenticate the server (VERIFY_PEER) and never downgrade to VERIFY_NONE. The state machine should generate an SSLContext initialized with the CA certs, CRL bundle, client cert and private key so that all future connections are mutually authenticated.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 
   

Jira (PUP-9458) Create SSL state machine for downloading CA and CRL bundles

2019-01-23 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9458  
 
 
  Create SSL state machine for downloading CA and CRL bundles   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/01/23 3:36 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Josh Cooper  
 

  
 
 
 
 

 
 Create a state machine for downloading CA and CRL bundles. It should verify each cert and CRL before committing them to disk, eg should be valid X509 objects and signatures should be valid. The state machine should produce an SSLContext initialized with those objects so that subsequent requests are guaranteed to authenticate the server (VERIFY_PEER).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  

Jira (PUP-9457) Add HttpPool method for creating connections using an SSLContext

2019-01-23 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9457  
 
 
  Add HttpPool method for creating connections using an SSLContext   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/01/23 3:33 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Josh Cooper  
 

  
 
 
 
 

 
 Update the Puppet::Network::HttpPool factory to return a SSL connection from a host, port and SSLContext. If caching is not enabled, then it should always create a new connection. If caching is enabled, it should only return a cached connection, if they both have the same SSLContext (and same verification mode, certs/keys, etc).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
   

Jira (PUP-9456) Create SSLContext and SSLProvider

2019-01-23 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9456  
 
 
  Create SSLContext and SSLProvider   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/01/23 3:30 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Josh Cooper  
 

  
 
 
 
 

 
 Create an SSLProvider responsible for generating SSLContext objects containing all cert/key material needed to create an SSL connection. This includes the X509 store, CA certs, CRLs, revocation mode, client cert, private key, and peer verification mode. The provider should have methods for creating an SSLContext for 3 different use cases: 1. No authentication: We don't have any certs, and need to download the CA bundle. 2. Server verification: We have a CA certs (and optionally CRLs), but no client cert/private key 3. Mutual authentication: We have CA certs (and optionally CRLs), private key, and client cert  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 

Jira (PUP-9455) Create CertProvider

2019-01-23 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9455  
 
 
  Create CertProvider   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/01/23 3:25 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Josh Cooper  
 

  
 
 
 
 

 
 Create CertProvider with methods for loading and saving X509 objects (CA certs, CRLs, CSR, private key, client cert). It should support loading/saving multiple CA certs and CRLs. It should be possible to load objects from either a file or string.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   

Jira (PUP-5575) puppet.conf permission issues should be blocking - now silently ignoring error

2019-01-23 Thread Jean Bond (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean Bond updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-5575  
 
 
  puppet.conf permission issues should be blocking - now silently ignoring error   
 

  
 
 
 
 

 
Change By: 
 Jean Bond  
 
 
Labels: 
 resolved-issue-added  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6571) An invalid path to the --logdest option is silently ignored

2019-01-23 Thread Kris Bosland (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kris Bosland updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6571  
 
 
  An invalid path to the --logdest option is silently ignored   
 

  
 
 
 
 

 
Change By: 
 Kris Bosland  
 
 
Release Notes Summary: 
 When the only log is a file, and Puppet fails to open that file, Puppet will exit with an error.  
 
 
Release Notes: 
 Enhancement  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9337) Puppet sets permissions for Puppet files every run

2019-01-23 Thread Adam Bottchen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Bottchen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9337  
 
 
  Puppet sets permissions for Puppet files every run   
 

  
 
 
 
 

 
Change By: 
 Adam Bottchen  
 
 
CS Priority: 
 Reviewed Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3745) Various tables in the puppetdb database get autovacuumed too frequently

2019-01-23 Thread Adam Bottchen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Bottchen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3745  
 
 
  Various tables in the puppetdb database get autovacuumed too frequently
 

  
 
 
 
 

 
Change By: 
 Adam Bottchen  
 
 
CS Priority: 
 Reviewed Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6591) Recurse option on nested directories silently omits files

2019-01-23 Thread Adam Bottchen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Bottchen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6591  
 
 
  Recurse option on nested directories silently omits files   
 

  
 
 
 
 

 
Change By: 
 Adam Bottchen  
 
 
CS Priority: 
 Reviewed Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-4072) HA out-of-sync after restart

2019-01-23 Thread Adam Bottchen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Bottchen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4072  
 
 
  HA out-of-sync after restart   
 

  
 
 
 
 

 
Change By: 
 Adam Bottchen  
 
 
CS Priority: 
 Reviewed Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1907) facter 3.12.2 choses wrong ip as main ip

2019-01-23 Thread Tim Meusel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Meusel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1907  
 
 
  facter 3.12.2 choses wrong ip as main ip   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/01/23 1:43 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Tim Meusel  
 

  
 
 
 
 

 
 Hi people, I did some debugging with Eric Sorenson on slack about this. I have a server with multiple ip addresses on a single interface. One address is considered the main address. This one is persistant and always present. the others are floating ips.they might be added/removed during runtime. The setup at the moment:  
 
 
 
 
 # facter -p networking.interfaces.enp5s0.ip  
 
 
 10.254.4.100  
 
 
  # facter -p networking.ip  
 
 
 10.254.4.100  
 
 
  # facter --version  
 
 
 3.12.2  
 
 
   

Jira (BOLT-1099) Bolt docs suggest you can pass params as key=value when they need to be json.

2019-01-23 Thread Mikker Gimenez-Peterson (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mikker Gimenez-Peterson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1099  
 
 
  Bolt docs suggest you can pass params as key=value when they need to be json.   
 

  
 
 
 
 

 
Change By: 
 Mikker Gimenez-Peterson  
 

  
 
 
 
 

 
 these docs suggest you can pass params as key=value:[ https://puppet.com/docs/bolt/1.x/writing_plans.html#variables-and-facts-on-targets ]  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1099) Bolt docs suggest you can pass params as key=value when they need to be json.

2019-01-23 Thread Mikker Gimenez-Peterson (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mikker Gimenez-Peterson created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1099  
 
 
  Bolt docs suggest you can pass params as key=value when they need to be json.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/01/23 1:33 PM  
 
 
Environment: 
 https://puppet.com/docs/bolt/1.x/writing_plans.html#variables-and-facts-on-targets  
 
 
Labels: 
 customer0  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Mikker Gimenez-Peterson  
 

  
 
 
 
 

 
 https://puppet.com/docs/bolt/1.x/writing_plans.html#variables-and-facts-on-targets  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  

Jira (PUP-9435) Windows - Group resource member parameter outputs an array of SID's instead of Names

2019-01-23 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols commented on  PUP-9435  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Windows - Group resource member parameter outputs an array of SID's instead of Names   
 

  
 
 
 
 

 
 PR#7334 was merged to puppet#5.5.x in https://github.com/puppetlabs/puppet/commit/1b55647efd034746b6190f402f08a2889b233586  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9337) Puppet sets permissions for Puppet files every run

2019-01-23 Thread Eric Thompson (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Thompson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9337  
 
 
  Puppet sets permissions for Puppet files every run   
 

  
 
 
 
 

 
Change By: 
 Eric Thompson  
 
 
Comment: 
 hi y'all.  please set a fix version when we know where the fix will go.  hopefully this will prevent tickets like this getting lost or not prioritized when they are no longer associated with a (closed) support escalation.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9454) Newer agent can't submit CSR to older server, error "environment must be purely alphanumeric, not 'puppet-ca' "

2019-01-23 Thread Leroy tennison (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Leroy tennison commented on  PUP-9454  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Newer agent can't submit CSR to older server, error "environment must be purely alphanumeric, not 'puppet-ca' "   
 

  
 
 
 
 

 
 That is exactly the case I have.  Although not what I was hoping to hear, it's what I needed to know, thank you.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8376) Revert to production when agent-specified environment doesn't exist

2019-01-23 Thread Daniel Parks (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Parks commented on  PUP-8376  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Revert to production when agent-specified environment doesn't exist   
 

  
 
 
 
 

 
 We generally want to run the agent in that environment for a while, since often reverting the environment early will cause undesirable changes. It's general enough that we set the current environment in puppet.conf from within our Puppet code. This boils down to three requirements: 
 
I can set the environment on a node from the node itself. Ideally, this can be enforced with Puppet code. 
The environment will be reverted to production when the branch is deleted. 
Built into puppet. 
 I don't really care about the implementation. A nice to have is being able to get the current environment with puppet config print.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1906) networking.dhcp fact is blank on RedHat 8 beta

2019-01-23 Thread Jean Bond (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean Bond updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1906  
 
 
  networking.dhcp fact is blank on RedHat 8 beta   
 

  
 
 
 
 

 
Change By: 
 Jean Bond  
 
 
Labels: 
 dhcp  known-issue-added  linux redhat  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8962) Type and provider info should be logged when prefetch fails

2019-01-23 Thread Jean Bond (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean Bond updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8962  
 
 
  Type and provider info should be logged when prefetch fails   
 

  
 
 
 
 

 
Change By: 
 Jean Bond  
 
 
Labels: 
 resolved-issue-added  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9324) Puppet agent run output to differentiate between corrective and intentional change

2019-01-23 Thread Melissa Stone (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Melissa Stone updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9324  
 
 
  Puppet agent run output to differentiate between corrective and intentional change   
 

  
 
 
 
 

 
Change By: 
 Melissa Stone  
 
 
Fix Version/s: 
 PUP 6.0.6  
 
 
Fix Version/s: 
 PUP 6.2.1  
 
 
Fix Version/s: 
 PUP 6.1.z  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9336) Ensure provider suitability is always lazily evaluated

2019-01-23 Thread Casey Williams (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Casey Williams commented on  PUP-9336  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ensure provider suitability is always lazily evaluated   
 

  
 
 
 
 

 
 This work was reverted after merging up to the 6.0.x branch to allow the 6.2.0 release to proceed. I'll open a PR to un-revert it after the release is finished.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8376) Revert to production when agent-specified environment doesn't exist

2019-01-23 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-8376  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Revert to production when agent-specified environment doesn't exist   
 

  
 
 
 
 

 
 The agent logic for switching environments is already convoluted (since facts can change your environment, but when you switch environments, you will pluginsync from a potentially different set of modules, so your facts may change). I'd rather see the ENC handle whatever policy is desired, and keep the agent/server communication as it is. Also if the goal is to only run in the agent specified environment to test the PR, then we shouldn't be doing puppet config set environment devbranch. Instead just specify the devbranch environment when running "oneshot" run puppet agent -tE devbranch. That way we don't need to "reset" the environment once the PR is merged. But maybe I'm not understanding?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9303) A heredoc with interpolation containing [ ] in the expression can cause syntax error

2019-01-23 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-9303  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: A heredoc with interpolation containing [ ] in the _expression_ can cause syntax error   
 

  
 
 
 
 

 
 So, what happens now - who does what to get the fix back in? Ping Josh Cooper  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9454) Newer agent can't submit CSR to older server, error "environment must be purely alphanumeric, not 'puppet-ca' "

2019-01-23 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9454  
 
 
  Newer agent can't submit CSR to older server, error "environment must be purely alphanumeric, not 'puppet-ca' "   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Priority: 
 Blocker Normal  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9454) Newer agent can't submit CSR to older server, error "environment must be purely alphanumeric, not 'puppet-ca' "

2019-01-23 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-9454  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Newer agent can't submit CSR to older server, error "environment must be purely alphanumeric, not 'puppet-ca' "   
 

  
 
 
 
 

 
 In general a newer server can service older agents, but not the other way around. You must upgrade your master before you upgrade your agents. If you are seeing errors because you have an old server servicing newer agents - that is to be expected. Is this the case here? If so there is nothing we can do to help you out. If I misunderstood the issue, then more information is needed.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9454) Newer agent can't submit CSR to older server, error "environment must be purely alphanumeric, not 'puppet-ca' "

2019-01-23 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg assigned an issue to Leroy tennison  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9454  
 
 
  Newer agent can't submit CSR to older server, error "environment must be purely alphanumeric, not 'puppet-ca' "   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Assignee: 
 Leroy tennison  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9454) Newer agent can't submit CSR to older server, error "environment must be purely alphanumeric, not 'puppet-ca' "

2019-01-23 Thread Leroy tennison (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Leroy tennison created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9454  
 
 
  Newer agent can't submit CSR to older server, error "environment must be purely alphanumeric, not 'puppet-ca' "   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 5.4.0  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 CLI, Puppet Server  
 
 
Created: 
 2019/01/23 7:54 AM  
 
 
Environment: 
   server version - 3.8.5 (open source running on Ubuntu 16.04, installed using apt-get, successfully servicing a number of same-version or older clients) client (agent) version - 5.4.0 (open source running on Ubuntu 18.04, installed using apt-get)   
 
 
Fix Versions: 
 PUP 5.4.0  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Leroy tennison  
 

  
 
 
 
 

 
 (The below is from question "No certificate request generated for agent, what do I do?" posted 1/16/19)  "puppet agent -t" on the client returns: Downgrading to PSON for future requests Could not request certificate: Error 400 on SERVER: The environment must be purely alphanumeric, not 'puppet-ca' Exiting; failed to retrieve certificate and waitforcert is disabled (I understand this issue and what to do about it) I have tried setting "environment = production" in puppet.conf and using "--environment production" on the command line - no change "tcpdump -neli any host " on the server shows traffic destined for port 8140 arriving and being answered but "puppet cert list" doesn't show a request "telnet  8140" on the agent shows a 

Jira (PUP-9437) Make it easier to set Puppets current locale

2019-01-23 Thread Thomas Honey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Honey commented on  PUP-9437  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make it easier to set Puppets current locale   
 

  
 
 
 
 

 
 Josh Cooper do you still need more information ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9422) Release puppetlabs-mount_core

2019-01-23 Thread Octavian Larion (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Octavian Larion assigned an issue to Octavian Larion  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9422  
 
 
  Release puppetlabs-mount_core   
 

  
 
 
 
 

 
Change By: 
 Octavian Larion  
 
 
Assignee: 
 Octavian Larion  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7859) Test Add functions 'all' and 'any'

2019-01-23 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-7859  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Test Add functions 'all' and 'any'   
 

  
 
 
 
 

 
 The functions all and any were added in Puppet 5.1 along with unit tests. What is this ticket for?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1906) networking.dhcp fact is blank on RedHat 8 beta

2019-01-23 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1906  
 
 
  networking.dhcp fact is blank on RedHat 8 beta   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 1 3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1906) networking.dhcp fact is blank on RedHat 8 beta

2019-01-23 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1906  
 
 
  networking.dhcp fact is blank on RedHat 8 beta   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-02-06  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1906) networking.dhcp fact is blank on RedHat 8 beta

2019-01-23 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1906  
 
 
  networking.dhcp fact is blank on RedHat 8 beta   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9409) Release puppetlabs-cron_core

2019-01-23 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9409  
 
 
  Release puppetlabs-cron_core   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-02-06  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9416) Release puppetlabs-zfs_core

2019-01-23 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9416  
 
 
  Release puppetlabs-zfs_core   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-02-06  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9422) Release puppetlabs-mount_core

2019-01-23 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9422  
 
 
  Release puppetlabs-mount_core   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-02-06  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9420) Release puppetlabs-zone_core

2019-01-23 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9420  
 
 
  Release puppetlabs-zone_core   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9420) Release puppetlabs-zone_core

2019-01-23 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9420  
 
 
  Release puppetlabs-zone_core   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-02-06  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9414) Release puppetlabs-selinux_core 1.0.3 (6157ab8de510d)

2019-01-23 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9414  
 
 
  Release puppetlabs-selinux_core 1.0.3 (6157ab8de510d)   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-02-06  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9416) Release puppetlabs-zfs_core

2019-01-23 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9416  
 
 
  Release puppetlabs-zfs_core   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9414) Release puppetlabs-selinux_core 1.0.3 (6157ab8de510d)

2019-01-23 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9414  
 
 
  Release puppetlabs-selinux_core 1.0.3 (6157ab8de510d)   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9422) Release puppetlabs-mount_core

2019-01-23 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9422  
 
 
  Release puppetlabs-mount_core   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9409) Release puppetlabs-cron_core

2019-01-23 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9409  
 
 
  Release puppetlabs-cron_core   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9453) Default OS repositories layout messed up by yum module

2019-01-23 Thread Christopher Peeters (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Peeters created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9453  
 
 
  Default OS repositories layout messed up by yum module   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 CentOS-Base-expected.repo, CentOS-Base-reality.repo, CentOS-Base.repo  
 
 
Created: 
 2019/01/23 1:58 AM  
 
 
Environment: 
 
 
OS: CentOS 7 (CentOS Linux release 7.6.1810 (Core)) 
Running on KVM virtual machines (libvirt version 4.7.0-1.fc29) using vagrant-libvirt 
 
vagrant 2.1.2 
vagrant-libvirt 0.0.40, system 
  
Host OS: Fedora 29 
Puppet version: 5.5.10 
 
Yum module version: 3.1.1 
Stdlib module version: 5.1.0 
Concat module version: 5.2.0 
  
Hardware specs on demand 
  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Christopher Peeters  
 

  
 
 
 
 

 
 When using the yum module to manage the default repositories, I get a messed up repofile. It