Jira (PUP-3262) By default, the cadir should be separated from the ssldir

2018-05-31 Thread Eric Sorenson (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-3262  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: By default, the cadir should be separated from the ssldir   
 

  
 
 
 
 

 
 Justin Stoller and I talked through this; a bit more guidance: 
 
the new CA dir ought to be under /etc/puppetlabs/puppetserver/ca, though the location should still be relocatable via a puppetserver.conf setting 
new installations should use that by default; existing installations should look in the old /etc/puppetlabs/puppet/ssl/ca directory and use that without modification if it exists (i.e. do not try to auto-migrate people's CA certs. that path lies madness!) 
the CLI tool from SERVER-2162 ought to provide an affordance for people to migrate an existing CA (whether single root+intermediate combo or root-only) from the old setup into a root+intermediate combo in the new location 
if we migrate it should also bring over the old CRL 
the implications on PE installations, both new and upgrades, need to be considered as part of this work (but under separate tickets) 
  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (PUP-8900) "puppet facts upload" face only tries first master in server_list

2018-05-31 Thread Jesse Reynolds (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Reynolds updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8900  
 
 
  "puppet facts upload" face only tries first master in server_list   
 

  
 
 
 
 

 
Change By: 
 Jesse Reynolds  
 
 
Attachment: 
 puppet-facts-upload-server_list-debug-trace.txt  
 

  
 
 
 
 

 
 
 

 
 
 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-3743) ensure PDB 4.4.x can be run with puppetserver 5.x

2018-05-31 Thread Shi Yan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shi Yan commented on  PDB-3743  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ensure PDB 4.4.x can be run with puppetserver 5.x   
 

  
 
 
 
 

 
 I have the same issue as well.   puppetserver is 5.3.1 puppetdb-termini is 5.2.2 puppetdb is 4.4.0   
 

  
 
 
 
 

 
 
 

 
 
 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-8900) "puppet facts upload" face only tries first master in server_list

2018-05-31 Thread Jesse Reynolds (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Reynolds updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8900  
 
 
  "puppet facts upload" face only tries first master in server_list   
 

  
 
 
 
 

 
Change By: 
 Jesse Reynolds  
 
 
Attachment: 
 puppet-facts-upload-server_list-debug-trace.txt  
 

  
 
 
 
 

 
 
 

 
 
 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-8900) "puppet facts upload" face only tries first master in server_list

2018-05-31 Thread Jesse Reynolds (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Reynolds updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8900  
 
 
  "puppet facts upload" face only tries first master in server_list   
 

  
 
 
 
 

 
Change By: 
 Jesse Reynolds  
 
 
Attachment: 
 puppet-facts-upload-server_list-debug-trace.txt  
 

  
 
 
 
 

 
 
 

 
 
 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-8900) "puppet facts upload" face only tries first master in server_list

2018-05-31 Thread Jesse Reynolds (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Reynolds created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8900  
 
 
  "puppet facts upload" face only tries first master in server_list   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 5.5.1  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/05/31 5:23 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Jesse Reynolds  
 

  
 
 
 
 

 
 Puppet Version: 5.5.1 Puppet Server Version: 5.5.2 (2018.1.0.41) OS Name/Version: RHEL 7 When a node's puppet.conf specifies multiple masters in server_list the facts upload face only tries the first master in the list. If this fails due to a hostname lookup failure on the first master the face exits with an error, rather than trying the second master.  Steps to reproduce: 
 
remove any "server" configs from puppet.conf 
add the following "server_list" configuration: "foo.example,actual-master.example" (where "actual-master.example" is the working master address, and "foo.example" is not resolvable to an IP address) 
run "puppet facts upload" 
 Desired Behavior: 
 
the face should gracefully fail over to the second master in the server_list and complete the facts upload successfully 
 Actual Behavior: 
 
the face fails with the following error message: 
  
 
 
 
  

Jira (BOLT-545) upload/script/task doesn't work with --run-as on AIX (and possibly others)

2018-05-31 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-545  
 
 
  upload/script/task doesn't work with --run-as on AIX (and possibly others)   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Assignee: 
 Michael Smith  
 

  
 
 
 
 

 
 
 

 
 
 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-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent

2018-05-31 Thread Adam Bottchen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Bottchen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1858  
 
 
  Provide an option to disable legacy facts so they are not sent to the master from the agent   
 

  
 
 
 
 

 
Change By: 
 Adam Bottchen  
 
 
CS Priority: 
 Needs Priority Reviewed  
 

  
 
 
 
 

 
 
 

 
 
 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-3928) Facts blacklist should support providing a fact name regex to blacklist facts matching a pattern

2018-05-31 Thread Adam Bottchen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Bottchen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3928  
 
 
  Facts blacklist should support providing a fact name regex to blacklist facts matching a pattern   
 

  
 
 
 
 

 
Change By: 
 Adam Bottchen  
 
 
CS Priority: 
 Needs Priority Major  
 
 
CS Impact: 
 There is a significant performance boost available for customers if they block unneeded facts from being sent for storage.  Without the ability to use regexs, it is not reasonable to blacklist all possible permutations of possible names for network and block device facts since they could be in the hundreds depending on installation size.  These are most likely not going to be needed by customers in general.  
 
 
CS Severity: 
 4 - Major  
 
 
CS Business Value: 
 4 - $  
 
 
CS Frequency: 
 3 - 25-50% of Customers  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

Jira (BOLT-545) upload/script/task doesn't work with --run-as on AIX (and possibly others)

2018-05-31 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-545  
 
 
  upload/script/task doesn't work with --run-as on AIX (and possibly others)   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 

  
 
 
 
 

 
 When we need to change the owner of a file over SSH (which we do when using run-as while uploading files, running scripts or running tasks), we do so with {{chown username: file}}. The trailing colon means "set the group of the file to the primary group of the user". However, that syntax isn't universally supported (AIX in particular). That causes the run to fail.We'd like to preserve setting groups. For uploading files with run-as, not setting the group correctly could leave files in an unpredictable state (depending on who runs Bolt).Use {{id -g }} to query the group and pass to chown, as in {{chown :`id -g ` }}.  If that fails, fall back to {{chown  }} and issue a warning.  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (BOLT-545) upload/script/task doesn't work with --run-as on AIX (and possibly others)

2018-05-31 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith assigned an issue to Michael Smith  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-545  
 
 
  upload/script/task doesn't work with --run-as on AIX (and possibly others)   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Assignee: 
 Michael Smith  
 

  
 
 
 
 

 
 
 

 
 
 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-8619) File Resource: error when attempting to use checksum and checksum_value to retrieve from filebucket

2018-05-31 Thread Garrett Guillotte (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Garrett Guillotte updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8619  
 
 
  File Resource: error when attempting to use checksum and checksum_value to retrieve from filebucket   
 

  
 
 
 
 

 
Change By: 
 Garrett Guillotte  
 
 
Release Notes: 
 Not 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 (FACT-1851) Linux networking resolver doesn't collect DHCP information under systemd-networkd

2018-05-31 Thread Casey Williams (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Casey Williams updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1851  
 
 
  Linux networking resolver doesn't collect DHCP information under systemd-networkd   
 

  
 
 
 
 

 
Change By: 
 Casey Williams  
 
 
Release Notes Summary: 
 Systems relying entirely on systemd-networkd for DHCP management do not use dhclient -- this checks systemd-networkd's DHCP leases directory (/run/systemd/netif/leases) in addition to dhclient's lease files when attempting to identify DHCP servers.  
 

  
 
 
 
 

 
 
 

 
 
 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-1851) Linux networking resolver doesn't collect DHCP information under systemd-networkd

2018-05-31 Thread Casey Williams (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Casey Williams commented on  FACT-1851  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Linux networking resolver doesn't collect DHCP information under systemd-networkd   
 

  
 
 
 
 

 
 Apologies, Garrett Guillotte – missed kenn's note initially – I've added some notes  
 

  
 
 
 
 

 
 
 

 
 
 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-1851) Linux networking resolver doesn't collect DHCP information under systemd-networkd

2018-05-31 Thread Casey Williams (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Casey Williams updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1851  
 
 
  Linux networking resolver doesn't collect DHCP information under systemd-networkd   
 

  
 
 
 
 

 
Change By: 
 Casey Williams  
 
 
Release Notes: 
 Bug Fix  
 

  
 
 
 
 

 
 
 

 
 
 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-1851) Linux networking resolver doesn't collect DHCP information under systemd-networkd

2018-05-31 Thread Garrett Guillotte (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Garrett Guillotte commented on  FACT-1851  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Linux networking resolver doesn't collect DHCP information under systemd-networkd   
 

  
 
 
 
 

 
 Casey Williams bump, even if this doesn't need release notes, please set the Release Notes dropdown in the DOCS tab  
 

  
 
 
 
 

 
 
 

 
 
 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-8748) Puppet::Rest::Client should allow its verify mode to be configured by the caller

2018-05-31 Thread Tony Vu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tony Vu commented on  PUP-8748  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet::Rest::Client should allow its verify mode to be configured by the caller   
 

  
 
 
 
 

 
 The caller still doesn't explicitly set the SSL configuration; the configure_verify_mode for the client class still does a lookup for the localcacert to determine the configuration of the ssl_config object. I included the code for my comment above in PUP-8654, but the client still doesn't have an explicit ability to modify its configuration.  
 

  
 
 
 
 

 
 
 

 
 
 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-555) Accept 'tty' option in inventory and/or config file

2018-05-31 Thread Kate Lopresti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kate Lopresti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-555  
 
 
  Accept 'tty' option in inventory and/or config file   
 

  
 
 
 
 

 
Change By: 
 Kate Lopresti  
 
 
Labels: 
 docs-reviewed feature  
 

  
 
 
 
 

 
 
 

 
 
 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-464) Publish Bolt to chocolatey.org

2018-05-31 Thread Kate Lopresti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kate Lopresti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-464  
 
 
  Publish Bolt to chocolatey.org   
 

  
 
 
 
 

 
Change By: 
 Kate Lopresti  
 
 
Labels: 
 docs-reviewed feature  
 

  
 
 
 
 

 
 
 

 
 
 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-465) Publish Bolt to Homebrew Cask

2018-05-31 Thread Kate Lopresti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kate Lopresti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-465  
 
 
  Publish Bolt to Homebrew Cask   
 

  
 
 
 
 

 
Change By: 
 Kate Lopresti  
 
 
Labels: 
 DOCS docs  feature  
 

  
 
 
 
 

 
 
 

 
 
 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 (HI-603) Hiera v5 lookups not working as expected

2018-05-31 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  HI-603  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Hiera v5 lookups not working as expected   
 

  
 
 
 
 

 
 The posted sample looks odd - there should be no numbers or bullets in a hiera.yaml file version 5. Looks like the description from the documentation has been copied into hiera.yaml? It looks like you are a PE user and you can contact puppet support to get help.  
 

  
 
 
 
 

 
 
 

 
 
 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-488) I would like to know how often subcommands in bolt are run

2018-05-31 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis commented on  BOLT-488  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: I would like to know how often subcommands in bolt are run   
 

  
 
 
 
 

 
 I've filed WEB-2932 for the work on the google analytics side, since it sounds like the help desk request wasn't the right way to proceed.  
 

  
 
 
 
 

 
 
 

 
 
 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-488) I would like to know how often subcommands in bolt are run

2018-05-31 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis commented on  BOLT-488  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: I would like to know how often subcommands in bolt are run   
 

  
 
 
 
 

 
 I have a help desk request open to get a project created in google analytics. This work is currently blocked waiting for that.  
 

  
 
 
 
 

 
 
 

 
 
 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-8748) Puppet::Rest::Client should allow its verify mode to be configured by the caller

2018-05-31 Thread Justin Stoller (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Justin Stoller commented on  PUP-8748  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet::Rest::Client should allow its verify mode to be configured by the caller   
 

  
 
 
 
 

 
 Tony Vu was this, or some part of this, done in PUP-8654 ?  
 

  
 
 
 
 

 
 
 

 
 
 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-1077) Extract nagios type/provider into a module

2018-05-31 Thread Jacob Helwig (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Helwig updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-1077  
 
 
  Extract nagios type/provider into a module   
 

  
 
 
 
 

 
Change By: 
 Jacob Helwig  
 
 
Release Notes Summary: 
 The Nagios types no longer ship with Puppet, and are now available as the puppetlabs/nagios_core module from the Forge.  
 
 
Release Notes: 
 New Feature  
 

  
 
 
 
 

 
 
 

 
 
 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-546) mktemp is not available on all platform (AIX specifically)

2018-05-31 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-546  
 
 
  mktemp is not available on all platform (AIX specifically)   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 

  
 
 
 
 

 
 We recently were trying to run a "script" to install bash on AIX (which is not as simple as "yum install bash") and noticed that it was trying to run "mktemp" to make a temporary directory to upload the 'random' filename of the script to. While I appreciate not creating predictable temporary directories, we should probably use a more portable mechanism, or at least test for its existence (similar to how the PE install.bash does). When {{mktemp}} fails, we should do one of the following- issue an error and request that you set {{--tmpdir}}- use one of the custom random file naming solutions in https://stackoverflow.com/a/10235393  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (BOLT-545) upload/script/task doesn't work with --run-as on AIX (and possibly others)

2018-05-31 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-545  
 
 
  upload/script/task doesn't work with --run-as on AIX (and possibly others)   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 

  
 
 
 
 

 
 When we need to change the owner of a file over SSH (which we do when using run-as while uploading files, running scripts or running tasks), we do so with {{chown username: file}}. The trailing colon means "set the group of the file to the primary group of the user". However, that syntax isn't universally supported (AIX in particular). That causes the run to fail.We'd like to preserve setting groups. For uploading files with run-as, not setting the group correctly could leave files in an unpredictable state (depending on who runs Bolt).Use {{id -g }} to query the group and pass to chown, as in {{chown :`id -g `   }}. If that fails, fall back to {{chown}} and issue a warning.  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (BOLT-545) upload/script/task doesn't work with --run-as on AIX (and possibly others)

2018-05-31 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-545  
 
 
  upload/script/task doesn't work with --run-as on AIX (and possibly others)   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 

  
 
 
 
 

 
 When we need to change the owner of a file over SSH (which we do when using run-as while uploading files, running scripts or running tasks), we do so with {{chown username: file}}. The trailing colon means "set the group of the file to the primary group of the user". However, that syntax isn't universally supported (AIX in particular). That causes the run to fail.We  need 'd like  to  come up  preserve setting groups. For uploading files  with  some alternative solution for  run-as, not  setting  the  group  correctly could leave files in an unpredictable state (depending  on  those platforms  who runs Bolt) . Use {{id -g }} to query the group and pass to chown, as in {{chown :`id -g `}}. If that fails, fall back to {{chown }} and issue a warning.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You 

Jira (BOLT-555) Accept 'tty' option in inventory and/or config file

2018-05-31 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-555  
 
 
  Accept 'tty' option in inventory and/or config file   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Fix Version/s: 
 BOLT Next  
 

  
 
 
 
 

 
 
 

 
 
 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-464) Publish Bolt to chocolatey.org

2018-05-31 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-464  
 
 
  Publish Bolt to chocolatey.org   
 

  
 
 
 
 

 
Change By: 
 Lucy Wyman  
 
 
Fix Version/s: 
 BOLT Next  
 
 
Fix Version/s: 
 BOLT 0.20.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 (BOLT-464) Publish Bolt to chocolatey.org

2018-05-31 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-464  
 
 
  Publish Bolt to chocolatey.org   
 

  
 
 
 
 

 
Change By: 
 Lucy Wyman  
 
 
Fix Version/s: 
 BOLT Next  
 

  
 
 
 
 

 
 
 

 
 
 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-519) Bolt should send a Bolt user agent header to orchestrator

2018-05-31 Thread Kate Lopresti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kate Lopresti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-519  
 
 
  Bolt should send a Bolt user agent header to orchestrator   
 

  
 
 
 
 

 
Change By: 
 Kate Lopresti  
 
 
Labels: 
 docs-reviewed  
 

  
 
 
 
 

 
 
 

 
 
 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-135) I want to execute different versions of the task file on different platforms

2018-05-31 Thread Kate Lopresti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kate Lopresti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-135  
 
 
  I want to execute different versions of the task file on different platforms   
 

  
 
 
 
 

 
Change By: 
 Kate Lopresti  
 
 
Labels: 
 docs  docs-reviewed feature  
 

  
 
 
 
 

 
 
 

 
 
 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-399) Update fact gathering task to leverage cross-platform support

2018-05-31 Thread Kate Lopresti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kate Lopresti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-399  
 
 
  Update fact gathering task to leverage cross-platform support   
 

  
 
 
 
 

 
Change By: 
 Kate Lopresti  
 
 
Labels: 
 docs-reviewed  
 

  
 
 
 
 

 
 
 

 
 
 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-551) Reconcile git commits, JIRA tickets, and versions (Bolt 0.20.4)

2018-05-31 Thread Yasmin Rajabi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yasmin Rajabi updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-551  
 
 
  Reconcile git commits, JIRA tickets, and versions (Bolt 0.20.4)   
 

  
 
 
 
 

 
Change By: 
 Yasmin Rajabi  
 
 
Team: 
 Direct Change  
 

  
 
 
 
 

 
 
 

 
 
 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-494) Document how to opt-out of analytics

2018-05-31 Thread David Kramer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Kramer assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-494  
 
 
  Document how to opt-out of analytics   
 

  
 
 
 
 

 
Change By: 
 David Kramer  
 
 
Assignee: 
 David Kramer  
 

  
 
 
 
 

 
 
 

 
 
 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-554) Send release announcements (Bolt 0.20.4)

2018-05-31 Thread Yasmin Rajabi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yasmin Rajabi updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-554  
 
 
  Send release announcements (Bolt 0.20.4)   
 

  
 
 
 
 

 
Change By: 
 Yasmin Rajabi  
 
 
Sub-team: 
 Bolt  
 
 
Team: 
 Direct Change  
 

  
 
 
 
 

 
 
 

 
 
 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-553) Docs for bolt release (Bolt 0.20.4)

2018-05-31 Thread Yasmin Rajabi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yasmin Rajabi updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-553  
 
 
  Docs for bolt release (Bolt 0.20.4)   
 

  
 
 
 
 

 
Change By: 
 Yasmin Rajabi  
 
 
Sub-team: 
 Bolt  
 
 
Team: 
 Direct Change  
 

  
 
 
 
 

 
 
 

 
 
 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-551) Reconcile git commits, JIRA tickets, and versions (Bolt 0.20.4)

2018-05-31 Thread Yasmin Rajabi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yasmin Rajabi updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-551  
 
 
  Reconcile git commits, JIRA tickets, and versions (Bolt 0.20.4)   
 

  
 
 
 
 

 
Change By: 
 Yasmin Rajabi  
 
 
Sub-team: 
 Bolt  
 

  
 
 
 
 

 
 
 

 
 
 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-552) Kick off release pipeline (Bolt 0.20.4)

2018-05-31 Thread Yasmin Rajabi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yasmin Rajabi updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-552  
 
 
  Kick off release pipeline (Bolt 0.20.4)   
 

  
 
 
 
 

 
Change By: 
 Yasmin Rajabi  
 
 
Sub-team: 
 Bolt  
 
 
Team: 
 Direct Change  
 

  
 
 
 
 

 
 
 

 
 
 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-547) Finish plans when using the pcp transport

2018-05-31 Thread David Kramer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Kramer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-547  
 
 
  Finish plans when using the pcp transport   
 

  
 
 
 
 

 
Change By: 
 David Kramer  
 
 
Summary: 
 Finish plans when using the pcp transport .  
 

  
 
 
 
 

 
 
 

 
 
 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-546) mktemp is not available on all platform (AIX specifically)

2018-05-31 Thread David Kramer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Kramer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-546  
 
 
  mktemp is not available on all platform (AIX specifically)   
 

  
 
 
 
 

 
Change By: 
 David Kramer  
 
 
Sprint: 
 Bolt  Ready for Grooming  Kanban  
 

  
 
 
 
 

 
 
 

 
 
 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-534) Bolt hangs when no sudo password is provided

2018-05-31 Thread David Kramer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Kramer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-534  
 
 
  Bolt hangs when no sudo password is provided   
 

  
 
 
 
 

 
Change By: 
 David Kramer  
 
 
Sprint: 
 Bolt  Ready for Grooming  Kanban  
 

  
 
 
 
 

 
 
 

 
 
 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-555) Accept 'tty' option in inventory and/or config file

2018-05-31 Thread David Kramer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Kramer assigned an issue to Alex Dreyer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-555  
 
 
  Accept 'tty' option in inventory and/or config file   
 

  
 
 
 
 

 
Change By: 
 David Kramer  
 
 
Assignee: 
 Alex Dreyer  
 

  
 
 
 
 

 
 
 

 
 
 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-521) I want to escalate with a non-sudo command

2018-05-31 Thread David Kramer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Kramer assigned an issue to Alex Dreyer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-521  
 
 
  I want to escalate with a non-sudo command   
 

  
 
 
 
 

 
Change By: 
 David Kramer  
 
 
Assignee: 
 Alex Dreyer  
 

  
 
 
 
 

 
 
 

 
 
 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-399) Update fact gathering task to leverage cross-platform support

2018-05-31 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-399  
 
 
  Update fact gathering task to leverage cross-platform support   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Release Notes: 
 Not 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 (BOLT-399) Update fact gathering task to leverage cross-platform support

2018-05-31 Thread David Kramer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Kramer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-399  
 
 
  Update fact gathering task to leverage cross-platform support   
 

  
 
 
 
 

 
Change By: 
 David Kramer  
 
 
Fix Version/s: 
 BOLT Next  
 

  
 
 
 
 

 
 
 

 
 
 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-521) I want to escalate with a non-sudo command

2018-05-31 Thread David Kramer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Kramer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-521  
 
 
  I want to escalate with a non-sudo command   
 

  
 
 
 
 

 
Change By: 
 David Kramer  
 
 
Fix Version/s: 
 BOLT Next  
 

  
 
 
 
 

 
 
 

 
 
 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-546) mktemp is not available on all platform (AIX specifically)

2018-05-31 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith commented on  BOLT-546  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: mktemp is not available on all platform (AIX specifically)   
 

  
 
 
 
 

 
 Vinoth Kumar why did you mark this as Needs 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-8898) Change default input_method for Task object type

2018-05-31 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8898  
 
 
  Change default input_method for Task object type   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Release Notes Summary: 
 The input_method property of Tasks now defaults to undef rather than the string "both". This allows more flexibility in defaults and what input_methods we choose to support in the future.  
 
 
Release Notes: 
 New Feature  
 

  
 
 
 
 

 
 
 

 
 
 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-534) Bolt hangs when no sudo password is provided

2018-05-31 Thread Eoin McQuillan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eoin McQuillan commented on  BOLT-534  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Bolt hangs when no sudo password is provided   
 

  
 
 
 
 

 
 Ok, sorry we just assumed it was unsupported. So we gem install bolt on our "edge" docker container which is a container running I think Alpine Linux. Bolt runs in there and calls out to whatever host we configure it to run against. The native OS is Mac OS X. The context of how it runs is that within a go application a system call is performed. N.B. The same behaviour occurs when bolt is run from the command line so I don't think it is the go app. My test environment was to vmpooler debian and ubuntu machines. I have installed again and what I see on the remote side is the following upon a ps: (10.32.112.222) root 14430 14426 0 14:44 ? 00:00:00 sudo -S -u root -p [sudo] Bolt needs to run as another user, password: chown -R root: /tmp/tmp.dlb3yIrgwM root 14431 14426 0 14:44 ? 00:00:00 sudo -S -u root -p [sudo] Bolt needs to run as another user, password: rm -rf /tmp/tmp.dlb3yIrgwM (N.B. pid 14426 is the pid of the SSH connection) On the docker container I have the following hanging round: root 95 9 0 14:44 ? 00:00:01 /usr/local/bin/ruby /usr/local/bundle/bin/bolt --format json --run-as root task run service::linux --modulepath /task-modules --nodes 10.32.112.222 --params {"action":"restart","name":"rsyslog"} In the proc file the environment variable is the following: BOLT_INVENTORY={"nodes":[{"name":"10.32.112.222","config":{"transport":"ssh","ssh": {"user":"eoin","password":"eoin","host-key-check":false} }}]}  (N.B. not very secure but it is purely to replicate the issue!) The version gives the following: /usr/local/bundle/bin/bolt --version 0.20.2 So the environment I have it running on is the following: 
 
Discovery Host:  10.32.123.103 
Underlying container: docker exec -it pd_edge /bin/sh (You can see the bolt pid still hanging round) 
Remote host which bolt is running against: 10.32.112.222 
 You should be able to login and see what's happening. If you want to run on the command line feel free. (Basically this is a temporary system for me so feel free to do whatever you want on it to help you troubleshoot)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

Jira (HI-603) Hiera v5 lookups not working as expected

2018-05-31 Thread matt montmorency (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 matt montmorency created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Hiera /  HI-603  
 
 
  Hiera v5 lookups not working as expected   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 matt montmorency  
 
 
Created: 
 2018/05/31 5:36 AM  
 
 
Environment: 
 We are a windows shop, so this is happening on windows nodes.  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 matt montmorency  
 

  
 
 
 
 

 
 Ever since upgrading to enterprise 2018.1, our puppet lookups have been failing.   lookup: PS C:\Users\mmontmorencyx> puppet lookup hieratest::fakevalue --explain Searching for "lookup_options" Global Data Provider (hiera configuration version 5) No such key: "lookup_options" Module "hieratest" not found Searching for "hieratest::fakevalue" Global Data Provider (hiera configuration version 5) No such key: "hieratest::fakevalue" Module "hieratest" not found Function lookup() did not find a value for the name 'hieratest::fakevalue'     env hiera.yaml: — version: 5 defaults: 
 
The default value for "datadir" is "data" under the same directory as the hiera.yaml 
file (this file) 
When specifying a datadir, make sure the directory exists. 
See https://docs.puppet.com/puppet/latest/environments.html for further details on environments. 
datadir: data 
data_hash: yaml_data hierarchy: 
 
 
name: "Per-node data (yaml version)" path:"nodes/%{::trusted.certname}.yaml" 
name: "Other YAML hierarchy levels" paths: