Jira (PUP-8663) http_keepalive_timeout setting doesn't work correctly under Ruby 2.x

2018-04-13 Thread Charlie Sharpsteen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Sharpsteen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8663  
 
 
  http_keepalive_timeout setting doesn't work correctly under Ruby 2.x   
 

  
 
 
 
 

 
Change By: 
 Charlie Sharpsteen  
 

  
 
 
 
 

 
 Back when the {{http_keepalive_timeout}} setting was introduced, Puppet ran under Ruby 1.9.3 and life was good:https://github.com/puppetlabs/puppet/blob/5.5.0/lib/puppet/network/http/pool.rbThen Ruby 2.x descended from the mountains and brought with it a {{Net::HTTP#keep_alive_timeout}}:https://github.com/ruby/ruby/blob/v2_4_3/lib/net/http.rb#L664Ruby's timeout defaults to 2 seconds and always overrides the timeout used by the Puppet agent. This causes HTTP connections to be closed early instead of being re-used which increases the TLS handshake load on Puppet Server along with the amount of connection state that network devices between the agent and server have to contend with.h2. Reproduction Case  - Install {{puppet-agent}} 5.5.0 and {{puppetserver}} 5.3.0 on a CentOS 7node:{code:bash}rpm -Uvh http://yum.puppetlabs.com/puppet5/puppet5-release-el-7.noarch.rpmyum install -y puppet-agent-5.5.0 puppetserver-5.3.0{code}  - Configure the puppet agent to connect to the local host and startpuppetserver:{code:bash}/opt/puppetlabs/bin/puppet config set --section main server $(hostname -f)systemctl start puppetserver{code}  - Run {{puppet agent -t}} to verify things work.  - Add a custom fact that will sleep for 4 seconds, which delays theHTTP POST request for a catalog:{code:bash}cat <<-'EOF' > /etc/puppetlabs/code/modules/testmod/lib/facter/sleep_fact.rbFacter.add(:sleep_fact) do  setcode do$stdout.puts("Sleeping for 4 seconds...")Kernel.sleep(4)nil  endendEOF{code}  - Set Puppet's {{http_keepalive_timeout}} to 15 seconds:{code:bash}/opt/puppetlabs/bin/puppet config set --section main http_keepalive_timeout 15s{code}  - Run {{puppet agent -t}} and track HTTP connections:{code:bash}/opt/puppetlabs/bin/puppet agent -t --http_debug 2>&1|grep -v '^->\|<-'{code}h3. OutcomeThe Puppet Agent opens a new TCP connection after loading facts despite{{http_keepalive_timeout}} being set to 15 seconds:{noformat}# /opt/puppetlabs/bin/puppet agent -t --http_debug 2>&1|grep -v '^->\|<-'opening connection to m4t83ynafhampi9.delivery.puppetlabs.net:8140...openedstarting SSL for m4t83ynafhampi9.delivery.puppetlabs.net:8140...SSL establishedreading 3339 bytes...read 3339 bytesConn keep-aliveInfo: Using configured environment 'production'Info: Retrieving pluginfactsreading 204 bytes...read 204 bytesConn keep-aliveInfo: Retrieving pluginreading 259 bytes...read 259 bytesConn keep-aliveInfo: Retrieving localesreading 204 bytes...read 204 bytesConn keep-alive  Info: Loading factsSleeping for 4 seconds...Conn close because of keep_alive_timeoutopening connection to m4t83ynafhampi9.delivery.puppetlabs.net:8140...openedstarting SSL for m4t83ynafhampi9.delivery.puppetlabs.net:8140...SSL established  reading 310 bytes...read 310 bytesConn keep-aliveInfo: Caching catalog for m4t83ynafhampi9.delivery.puppetlabs.netInfo: Applying 

Jira (PUP-8663) http_keepalive_timeout setting doesn't work correctly under Ruby 2.x

2018-04-13 Thread Charlie Sharpsteen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Sharpsteen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8663  
 
 
  http_keepalive_timeout setting doesn't work correctly under Ruby 2.x   
 

  
 
 
 
 

 
Change By: 
 Charlie Sharpsteen  
 

  
 
 
 
 

 
 Back when the {{http_keepalive_timeout}} setting was introduced, Puppet ran  under Ruby 1.9.3 and life was good :https://github . com/puppetlabs/puppet/blob/5.5.0/lib/puppet/network/http/pool.rb  Then Ruby 2.x descended from the mountains  and brought with it a {{Net::HTTP#keep_alive_timeout}} :https://github . com/ruby/ruby/blob/v2_4_3/lib/net/http.rb#L664  Ruby's timeout defaults  to 2 seconds and always overrides the timeout used by the Puppet agent.  This causes HTTP connections to be closed early instead of being re-used which increases the TLS handshake load on Puppet Server along with the amount of connection state that network devices between the agent and server have to contend with. h2. Reproduction Case  - Install {{puppet-agent}} 5.5.0 and {{puppetserver}} 5.3.0 on a CentOS 7node:{code:bash}rpm -Uvh http://yum.puppetlabs.com/puppet5/puppet5-release-el-7.noarch.rpmyum install -y puppet-agent-5.5.0 puppetserver-5.3.0{code}  - Configure the puppet agent to connect to the local host and startpuppetserver:{code:bash}/opt/puppetlabs/bin/puppet config set --section main server $(hostname -f)systemctl start puppetserver{code}  - Run {{puppet agent -t}} to verify things work.  - Add a custom fact that will sleep for 4 seconds, which delays theHTTP POST request for a catalog:{code:bash}cat <<-'EOF' > /etc/puppetlabs/code/modules/testmod/lib/facter/sleep_fact.rbFacter.add(:sleep_fact) do  setcode do$stdout.puts("Sleeping for 4 seconds...")Kernel.sleep(4)nil  endendEOF{code}  - Set Puppet's {{http_keepalive_timeout}} to 15 seconds:{code:bash}/opt/puppetlabs/bin/puppet config set --section main http_keepalive_timeout 15s{code}  - Run {{puppet agent -t}} and track HTTP connections:{code:bash}/opt/puppetlabs/bin/puppet agent -t --http_debug 2>&1|grep -v '^->\|<-'{code}h3. OutcomeThe Puppet Agent opens a new TCP connection after loading facts despite{{http_keepalive_timeout}} being set to 15 seconds:{noformat}# /opt/puppetlabs/bin/puppet agent -t --http_debug 2>&1|grep -v '^->\|<-'opening connection to m4t83ynafhampi9.delivery.puppetlabs.net:8140...openedstarting SSL for m4t83ynafhampi9.delivery.puppetlabs.net:8140...SSL establishedreading 3339 bytes...read 3339 bytesConn keep-aliveInfo: Using configured environment 'production'Info: Retrieving pluginfactsreading 204 bytes...read 204 bytesConn keep-aliveInfo: Retrieving pluginreading 259 bytes...read 259 bytesConn keep-aliveInfo: Retrieving localesreading 204 bytes...read 204 bytesConn keep-aliveInfo: Loading factsSleeping for 4 seconds...Conn close because of keep_alive_timeoutopening connection to m4t83ynafhampi9.delivery.puppetlabs.net:8140...openedstarting SSL for m4t83ynafhampi9.delivery.puppetlabs.net:8140...SSL establishedreading 310 bytes...read 310 bytesConn keep-aliveInfo: Caching catalog for m4t83ynafhampi9.delivery.puppetlabs.netInfo: 

Jira (PUP-8663) http_keepalive_timeout setting doesn't work correctly under Ruby 2.x

2018-04-13 Thread Charlie Sharpsteen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Sharpsteen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8663  
 
 
  http_keepalive_timeout setting doesn't work correctly under Ruby 2.x   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 5.5.0, PUP 4.10.10  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/04/13 6:14 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Charlie Sharpsteen  
 

  
 
 
 
 

 
 Back when the http_keepalive_timeout setting was introduced, Puppet ran under Ruby 1.9.3 and life was good. Then Ruby 2.x descended from the mountains and brought with it a Net::HTTP#keep_alive_timeout. Ruby's timeout defaults to 2 seconds and always overrides the timeout used by the Puppet agent. Reproduction Case 
 
Install puppet-agent 5.5.0 and puppetserver 5.3.0 on a CentOS 7 node: 
  
 
 
 
 
 rpm -Uvh http://yum.puppetlabs.com/puppet5/puppet5-release-el-7.noarch.rpm  
 
 
 yum install -y puppet-agent-5.5.0 puppetserver-5.3.0
  
 
 
 
  
 
Configure the puppet agent to connect to the local host and start puppetserver: 

Jira (PUP-8662) puppet plugin download doesn't re-use HTTP connections

2018-04-13 Thread Charlie Sharpsteen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Sharpsteen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8662  
 
 
  puppet plugin download doesn't re-use HTTP connections   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 5.5.0, PUP 4.10.10  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/04/13 5:33 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Charlie Sharpsteen  
 

  
 
 
 
 

 
 The puppet plugin download command doesn't re-use connections to the Puppet Server when downloading plugins from modules. This adds considerable time to downloads along with extra load on the Puppet Server due to multiple redundant TLS handshakes. Reproduction Case 
 
Install puppet-agent 5.5.0 and puppetserver 5.3.0 on a CentOS 7 node: 
  
 
 
 
 
 rpm -Uvh http://yum.puppetlabs.com/puppet5/puppet5-release-el-7.noarch.rpm  
 
 
 yum install -y puppet-agent-5.5.0 puppetserver-5.3.0
  
 
 
 
  
 
Configure the puppet agent to connect to the local host and start puppetserver: 
  
  

Jira (PUP-8662) puppet plugin download doesn't re-use HTTP connections

2018-04-13 Thread Charlie Sharpsteen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Sharpsteen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8662  
 
 
  puppet plugin download doesn't re-use HTTP connections   
 

  
 
 
 
 

 
Change By: 
 Charlie Sharpsteen  
 
 
Priority: 
 Normal 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-8634) Chown of ssldir Causing Failures

2018-04-13 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols assigned an issue to Daniel Mcilhagga  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8634  
 
 
  Chown of ssldir Causing Failures   
 

  
 
 
 
 

 
Change By: 
 Geoff Nichols  
 
 
Assignee: 
 Daniel Mcilhagga  
 

  
 
 
 
 

 
 
 

 
 
 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-455) Puppets log format doesn't match bolts

2018-04-13 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-455  
 
 
  Puppets log format doesn't match bolts   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Assignee: 
 Nick Lewis  
 

  
 
 
 
 

 
 
 

 
 
 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-482) Bump puppetlabs-service version for agentless tasks on windows/linux

2018-04-13 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-482  
 
 
  Bump puppetlabs-service version for agentless tasks on windows/linux   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Release Notes Summary: 
 service task packaged with Bolt now includes Linux- and Windows-specific tasks that don't rely on the puppet-agent.  
 
 
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-482) Bump puppetlabs-service version for agentless tasks on windows/linux

2018-04-13 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-482  
 
 
  Bump puppetlabs-service version for agentless tasks on windows/linux   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/04/13 4:21 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Michael Smith  
 

  
 
 
 
 

 
 Bump puppetlabs-service to 0.3.0 for https://github.com/puppetlabs/puppetlabs-service/blob/release/CHANGELOG.md#release-030.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   

Jira (PUP-6344) metrics.time.total does not correlate to time reported in log

2018-04-13 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-6344  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: metrics.time.total does not correlate to time reported in log   
 

  
 
 
 
 

 
 Merged to 5.5.1_release in https://github.com/puppetlabs/puppet/commit/4c12d149cefe20edfc55c86e7743e33ff85e480e  
 

  
 
 
 
 

 
 
 

 
 
 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-8240) ERB and EPP templates handle CRLF line endings inconsistently

2018-04-13 Thread Kris Bosland (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kris Bosland commented on  PUP-8240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ERB and EPP templates handle CRLF line endings inconsistently   
 

  
 
 
 
 

 
 Fixed in 5.5.1 rc:  
 
 
 
 
 puppet % cat -v /tmp/test.pp  
 
 
 file { "/tmp/test.txt":  
 
 
   content => epp("/tmp/test.epp")  
 
 
 }  
 
 
 puppet % cat -v /tmp/test.epp  
 
 
 line 1^M  
 
 
 line 2^M  
 
 
 :P^M  
 
 
 puppet % bx puppet apply /tmp/test.pp  
 
 
 Notice: Compiled catalog for [redacted] in environment production in 0.02 seconds  
 
 
 Notice: /Stage[main]/Main/File[/tmp/test.txt]/ensure: defined content as '{md5}ec01eff99f50062fb0927769185166eb'  
 
 
 Notice: Applied catalog in 0.02 seconds  
 
 
 puppet % cat -v /tmp/test.txt  
 
 

Jira (BOLT-450) Modules shipped in Bolt should have acceptance tests

2018-04-13 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith commented on  BOLT-450  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Modules shipped in Bolt should have acceptance tests   
 

  
 
 
 
 

 
 Somewhat blocked on not having a good Beaker workflow for AppVeyor.  
 

  
 
 
 
 

 
 
 

 
 
 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-455) Puppets log format doesn't match bolts

2018-04-13 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-455  
 
 
  Puppets log format doesn't match bolts   
 

  
 
 
 
 

 
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 (PUP-8498) Improve error for 'No title provided and "foo" is not a valid resource reference'

2018-04-13 Thread Kris Bosland (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kris Bosland commented on  PUP-8498  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Improve error for 'No title provided and "foo" is not a valid resource reference'   
 

  
 
 
 
 

 
 Fixed in 5.5.1 rc:  
 
 
 
 
 puppet % cat ~/.puppetlabs/etc/code/modules/foo/manifests/init.pp  
 
 
 class foo () {  
 
 
   notify { 'testing':  
 
 
 notify => xyz,  
 
 
   }  
 
 
 }  
 
 
 puppet % bx puppet apply -t --exec 'include foo'  
 
 
 Info: Loading facts  
 
 
 Error: No title provided and "xyz" is not a valid resource reference (file: /Users/kris.bosland/.puppetlabs/etc/code/modules/foo/manifests/init.pp, line: 3) on node [redacted]  
 
 
 
   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
   

Jira (PDB-3905) Update jenkins pipelines so that final builds have SHIP_NIGHTLY=false

2018-04-13 Thread Rob Browning (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3905  
 
 
  Update jenkins pipelines so that final builds have SHIP_NIGHTLY=false   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/04/13 3:03 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Rob Browning  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (PUP-6344) metrics.time.total does not correlate to time reported in log

2018-04-13 Thread Jacob Helwig (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Helwig assigned an issue to Jacob Helwig  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6344  
 
 
  metrics.time.total does not correlate to time reported in log   
 

  
 
 
 
 

 
Change By: 
 Jacob Helwig  
 
 
Assignee: 
 Kris Bosland Jacob Helwig  
 

  
 
 
 
 

 
 
 

 
 
 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-8661) Total time metric is nil on failed catalog retrieval

2018-04-13 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8661  
 
 
  Total time metric is nil on failed catalog retrieval   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Labels: 
 regression  
 

  
 
 
 
 

 
 
 

 
 
 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-3900) Check builds, promote to PE (PuppetDB 5.2.2)

2018-04-13 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3900  
 
 
  Check builds, promote to PE (PuppetDB 5.2.2)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Team: 
 Data Platform  
 

  
 
 
 
 

 
 
 

 
 
 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-3901) Update winston (PuppetDB 5.2.2)

2018-04-13 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3901  
 
 
  Update winston (PuppetDB 5.2.2)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Team: 
 Data Platform  
 

  
 
 
 
 

 
 
 

 
 
 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-3899) Bump versions, push directly, and tag (PuppetDB 5.2.2)

2018-04-13 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3899  
 
 
  Bump versions, push directly, and tag (PuppetDB 5.2.2)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Team: 
 Data Platform  
 

  
 
 
 
 

 
 
 

 
 
 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-8661) Total time metric is nil on failed catalog retrieval

2018-04-13 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8661  
 
 
  Total time metric is nil on failed catalog retrieval   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
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 (PDB-3898) Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.2)

2018-04-13 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3898  
 
 
  Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.2)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Team: 
 Data Platform  
 

  
 
 
 
 

 
 
 

 
 
 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-3897) Merge-up, branch, and create pipelines (PuppetDB 5.2.2)

2018-04-13 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3897  
 
 
  Merge-up, branch, and create pipelines (PuppetDB 5.2.2)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Team: 
 Data Platform  
 

  
 
 
 
 

 
 
 

 
 
 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-8661) Total time metric is nil on failed catalog retrieval

2018-04-13 Thread Jacob Helwig (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Helwig created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8661  
 
 
  Total time metric is nil on failed catalog retrieval   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jacob Helwig  
 
 
Created: 
 2018/04/13 2:49 PM  
 
 
Fix Versions: 
 PUP 5.5.1  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Jacob Helwig  
 

  
 
 
 
 

 
 Puppet sticks a nil total time in the metrics if it failed to retrieve a catalog from the master. We should make sure we stick a real time there.  
 
 
 
 
 "time"=>  
 
 
  {"name"=>"time",  
 
 
   "label"=>"Time",  
 
 
   "values"=>  
 
 
[["node_retrieval", "Node retrieval", 0.07789189496543258],  
 
 
 ["plugin_sync", "Plugin sync", 0.06572247401345521],  
   

Jira (PUP-7534) Deprecate using file checksums in `content` property

2018-04-13 Thread Jennifer Solman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jennifer Solman commented on  PUP-7534  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deprecate using file checksums in `content` property   
 

  
 
 
 
 

 
 https://projects.puppetlabs.com/issues/3955  
 

  
 
 
 
 

 
 
 

 
 
 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-8486) Warning for undefined variables is slow in jruby

2018-04-13 Thread Enis Inan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Enis Inan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8486  
 
 
  Warning for undefined variables is slow in jruby   
 

  
 
 
 
 

 
Change By: 
 Enis Inan  
 
 
Fix Version/s: 
 PUP 5.5.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-8486) Warning for undefined variables is slow in jruby

2018-04-13 Thread Enis Inan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Enis Inan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8486  
 
 
  Warning for undefined variables is slow in jruby   
 

  
 
 
 
 

 
Change By: 
 Enis Inan  
 
 
Fix Version/s: 
 PUP 5.5.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-8416) Remove old acceptance code that now lives in beaker-puppet

2018-04-13 Thread Enis Inan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Enis Inan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8416  
 
 
  Remove old acceptance code that now lives in beaker-puppet   
 

  
 
 
 
 

 
Change By: 
 Enis Inan  
 
 
Fix Version/s: 
 PUP 5.5.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-8495) Ubuntu 16.10 _AND NEWER_ use systemd provider as default

2018-04-13 Thread Enis Inan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Enis Inan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8495  
 
 
  Ubuntu 16.10 _AND NEWER_ use systemd provider as default   
 

  
 
 
 
 

 
Change By: 
 Enis Inan  
 
 
Fix Version/s: 
 PUP 5.5.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-7904) return() documentation incorrect regarding lambdas

2018-04-13 Thread Enis Inan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Enis Inan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7904  
 
 
  return() documentation incorrect regarding lambdas   
 

  
 
 
 
 

 
Change By: 
 Enis Inan  
 
 
Fix Version/s: 
 PUP 5.5.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-7057) Update password property of User type to mention Sensitive data type

2018-04-13 Thread Enis Inan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Enis Inan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7057  
 
 
  Update password property of User type to mention Sensitive data type   
 

  
 
 
 
 

 
Change By: 
 Enis Inan  
 
 
Fix Version/s: 
 PUP 5.5.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-8240) ERB and EPP templates handle CRLF line endings inconsistently

2018-04-13 Thread Jacob Helwig (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Helwig commented on  PUP-8240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ERB and EPP templates handle CRLF line endings inconsistently   
 

  
 
 
 
 

 
 This was merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/6082ad07c68d947f892552081d8159768a485ee9  
 

  
 
 
 
 

 
 
 

 
 
 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-8498) Improve error for 'No title provided and "foo" is not a valid resource reference'

2018-04-13 Thread Jacob Helwig (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Helwig commented on  PUP-8498  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Improve error for 'No title provided and "foo" is not a valid resource reference'   
 

  
 
 
 
 

 
 This was merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/d81bcf487b9af8f38198423404b14191909fe611  
 

  
 
 
 
 

 
 
 

 
 
 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-8561) Augeas unable to handle escaped quotes within quotes

2018-04-13 Thread Jacob Helwig (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Helwig commented on  PUP-8561  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Augeas unable to handle escaped quotes within quotes   
 

  
 
 
 
 

 
 This was merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/8010eef96deef702b225bbd0ca4c3eca77cbe9da  
 

  
 
 
 
 

 
 
 

 
 
 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-8610) PuppetStack.stacktrace is slow with a large stack

2018-04-13 Thread Jacob Helwig (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Helwig commented on  PUP-8610  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PuppetStack.stacktrace is slow with a large stack   
 

  
 
 
 
 

 
 This was merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/7af7246856b968658d48f74dcdb63c13749e6d54  
 

  
 
 
 
 

 
 
 

 
 
 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-8623) Remove deprecation of empty(undef) introduced in PUP-8492

2018-04-13 Thread Jacob Helwig (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Helwig commented on  PUP-8623  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remove deprecation of empty(undef) introduced in PUP-8492   
 

  
 
 
 
 

 
 This was merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/f45dfb991741130ed437465791835187fe64d2ed  
 

  
 
 
 
 

 
 
 

 
 
 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-1761) Infiniband's mac (hardware) address not provided

2018-04-13 Thread Enis Inan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Enis Inan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1761  
 
 
  Infiniband's mac (hardware) address not provided   
 

  
 
 
 
 

 
Change By: 
 Enis Inan  
 
 
Fix Version/s: 
 FACT 3.11.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 (FACT-1597) "Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug." on AIX

2018-04-13 Thread Enis Inan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Enis Inan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1597  
 
 
  "Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug." on AIX   
 

  
 
 
 
 

 
Change By: 
 Enis Inan  
 
 
Fix Version/s: 
 FACT 3.11.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 (FACT-1549) Build CFacter gems in Jenkins

2018-04-13 Thread Enis Inan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Enis Inan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1549  
 
 
  Build CFacter gems in Jenkins   
 

  
 
 
 
 

 
Change By: 
 Enis Inan  
 
 
Fix Version/s: 
 FACT 3.11.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-6996) Puppet automatically creates the production environment with the incorrect permissions

2018-04-13 Thread Kris Bosland (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kris Bosland commented on  PUP-6996  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet automatically creates the production environment with the incorrect permissions   
 

  
 
 
 
 

 
 Jacob Helwig is this ticket ready to be closed, or does it need another look?  
 

  
 
 
 
 

 
 
 

 
 
 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-8556) environment.conf modulepath should accept globs

2018-04-13 Thread Jacob Helwig (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Helwig commented on  PUP-8556  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: environment.conf modulepath should accept globs   
 

  
 
 
 
 

 
 Merged to master in bc8e56000f.  
 

  
 
 
 
 

 
 
 

 
 
 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-8556) environment.conf modulepath should accept globs

2018-04-13 Thread Jacob Helwig (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Helwig updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8556  
 
 
  environment.conf modulepath should accept globs   
 

  
 
 
 
 

 
Change By: 
 Jacob Helwig  
 
 
Fix Version/s: 
 PUP 6.0.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-8653) Agents should save all certs downloaded from the server

2018-04-13 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8653  
 
 
  Agents should save all certs downloaded from the server   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Attachment: 
 network_formats_diagram.jpg  
 

  
 
 
 
 

 
 
 

 
 
 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-8653) Agents should save all certs downloaded from the server

2018-04-13 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer commented on  PUP-8653  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Agents should save all certs downloaded from the server   
 

  
 
 
 
 

 
 I've gotten to the point where I can download something, so now I need to parse the response into a form that our SSL code can actually handle. I started to extract some of our response handling code, but it's looking like that's going to turn into a very long, complicated thread to pull, so I may investigate using it in its current form, since it's not indirector-dependent. That being said, the class/module structure is kind of convoluted (mostly the stuff related to formats, which is the most closely tied to indirections), so this might ultimately be a good excuse to make some of that more straightforward.  
 

  
 
 
 
 

 
 
 

 
 
 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-466) Document creating release tickets for Bolt

2018-04-13 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman commented on  BOLT-466  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Document creating release tickets for Bolt   
 

  
 
 
 
 

 
 Created https://docs.google.com/document/d/1qhY9_1AIEO03-lmrOPzFX78WmyWxC2WHW7aokz_p-0A/edit  
 

  
 
 
 
 

 
 
 

 
 
 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-380) Support ed25519 out-of-the-box

2018-04-13 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith commented on  BOLT-380  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support ed25519 out-of-the-box   
 

  
 
 
 
 

 
 We have fully standalone packages now, we'll add the gems in packaging.  
 

  
 
 
 
 

 
 
 

 
 
 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-380) Support ed25519 out-of-the-box

2018-04-13 Thread Gene Liverman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gene Liverman commented on  BOLT-380  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support ed25519 out-of-the-box   
 

  
 
 
 
 

 
 Nothing really. I kinda like the idea of a gem that works out the other things to pull in though for people who do need the support.  
 

  
 
 
 
 

 
 
 

 
 
 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-461) Rename bolt package to puppet-bolt

2018-04-13 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-461  
 
 
  Rename bolt package to puppet-bolt   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 

  
 
 
 
 

 
 Ubuntu 18.04 has a package called 'bolt' as part of the core system:https://packages.ubuntu.com/bionic/boltWe will need to rename our packages to avoid a conflict. Fortunately they do not have a binary called 'bolt' so I think we can retain that, but we'll definitely need to rename the packages.Setup puppet-bolt to replace bolt  < 0.20.0 and  only on the platforms where we currently ship packages.  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (BOLT-461) Rename bolt package to puppet-bolt

2018-04-13 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-461  
 
 
  Rename bolt package to puppet-bolt   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 

  
 
 
 
 

 
 Ubuntu 18.04 has a package called 'bolt' as part of the core system:https://packages.ubuntu.com/bionic/boltWe will need to rename our packages to avoid a conflict. Fortunately they do not have a binary called 'bolt' so I think we can retain that, but we'll definitely need to rename the packages. Setup puppet-bolt ?  to replace bolt only on the platforms where we currently ship packages.  
 

  
 
 
 
 

 
 
 

 
 
 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-461) Rename bolt package to puppet-bolt

2018-04-13 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith commented on  BOLT-461  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Rename bolt package to puppet-bolt   
 

  
 
 
 
 

 
 We expect this to propagate to all the major Linux distros eventually, given they're on Ubuntu and Fedora.  
 

  
 
 
 
 

 
 
 

 
 
 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-461) Rename bolt package to puppet-bolt

2018-04-13 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-461  
 
 
  Rename bolt package to puppet-bolt   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Fix Version/s: 
 BOLT 0.20.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 (BOLT-461) Rename bolt package to puppet-bolt

2018-04-13 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-461  
 
 
  Rename bolt package to puppet-bolt   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Summary: 
 Rename bolt package  conflict on Ubuntu 18.04  to puppet-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 (PUP-8655) Agent should use whole cert bundle to verify master's credentials

2018-04-13 Thread Tony Vu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tony Vu assigned an issue to Tony Vu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8655  
 
 
  Agent should use whole cert bundle to verify master's credentials   
 

  
 
 
 
 

 
Change By: 
 Tony Vu  
 
 
Assignee: 
 Tony Vu  
 

  
 
 
 
 

 
 
 

 
 
 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-7407) Add deprecation warning to Puppet::Util.absolute_path?

2018-04-13 Thread Craig Gomes (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Gomes updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7407  
 
 
  Add deprecation warning to Puppet::Util.absolute_path?   
 

  
 
 
 
 

 
Change By: 
 Craig Gomes  
 
 
Sprint: 
 Agent 2017-04-19 , Platform Core Hopper  
 

  
 
 
 
 

 
 
 

 
 
 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-7551) deprecate 'puppet describe'

2018-04-13 Thread Craig Gomes (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Gomes updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7551  
 
 
  deprecate 'puppet describe'   
 

  
 
 
 
 

 
Change By: 
 Craig Gomes  
 
 
Sprint: 
 Platform Core Hopper  
 

  
 
 
 
 

 
 
 

 
 
 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-7600) Deprecate built-in LDAP Node Terminus

2018-04-13 Thread Craig Gomes (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Gomes updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7600  
 
 
  Deprecate built-in LDAP Node Terminus   
 

  
 
 
 
 

 
Change By: 
 Craig Gomes  
 
 
Sprint: 
 Platform Core Hopper  
 

  
 
 
 
 

 
 
 

 
 
 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-5921) Deprecate source_permissions

2018-04-13 Thread Craig Gomes (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Gomes updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-5921  
 
 
  Deprecate source_permissions   
 

  
 
 
 
 

 
Change By: 
 Craig Gomes  
 
 
Sprint: 
 Platform Core Hopper  
 

  
 
 
 
 

 
 
 

 
 
 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-8637) freeze_main setting breaks when used with type aliases

2018-04-13 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8637  
 
 
  freeze_main setting breaks when used with type aliases   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Release Notes Summary: 
 When using {{--freeze_main}} there were circumstances when this would cause an error even if there were no code loading resulting in a modification of the main loaded logic.  
 
 
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 (PUP-8660) "puppet apply" should not ignore updated custom facts within the module under test

2018-04-13 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8660  
 
 
  "puppet apply" should not ignore updated custom facts within the module under test   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Team: 
 Platform Core  
 

  
 
 
 
 

 
 
 

 
 
 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-8660) "puppet apply" should not ignore updated custom facts within the module under test

2018-04-13 Thread Martin Ewings (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Ewings updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8660  
 
 
  "puppet apply" should not ignore updated custom facts within the module under test   
 

  
 
 
 
 

 
Change By: 
 Martin Ewings  
 
 
CS Priority: 
 Needs Priority  
 
 
Zendesk Ticket IDs: 
 29447  
 
 
Zendesk Ticket Count: 
 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-8660) "puppet apply" should not ignore updated custom facts within the module under test

2018-04-13 Thread Martin Ewings (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Ewings updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8660  
 
 
  "puppet apply" should not ignore updated custom facts within the module under test   
 

  
 
 
 
 

 
Change By: 
 Martin Ewings  
 
 
Zendesk Ticket IDs: 
 29447  
 
 
Zendesk Ticket Count: 
 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 (PDB-3904) (maint) Portability fixes

2018-04-13 Thread gepetto-bot (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 gepetto-bot created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3904  
 
 
  (maint) Portability fixes   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/04/12 11:58 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 gepetto-bot  
 

  
 
 
 
 

 
 Manpages generation was broken on FreeBSD. These commits improve portability allowing the man page to build successfully on this platform.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

Jira (FACT-1762) valid networking facts in 2.x get ignored in 3.x

2018-04-13 Thread Jake Yip (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jake Yip commented on  FACT-1762  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: valid networking facts in 2.x get ignored in 3.x   
 

  
 
 
 
 

 
 In addition to alias interfaces, vlan interfaces that were munged in facter 2 are also broken in facter 3 On a Linux box, the interface name is eth0.100 facter 2: ipaddress_eth0_100 facter 3: ipaddress_eth0.100 I'm wondering if this is fixed as a by-product of fixing this bug, or should this be another bug? I can't find a bug report pointing this vlan interfaces specifically.  
 

  
 
 
 
 

 
 
 

 
 
 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.