Jira (BOLT-950) Send release announcements (Bolt 1.2.0)

2018-10-30 Thread Kate Lopresti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kate Lopresti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-950  
 
 
  Send release announcements (Bolt 1.2.0)   
 

  
 
 
 
 

 
Change By: 
 Kate Lopresti  
 

  
 
 
 
 

 
 (Initial planned release date: 2018-10-25)Once docs have finished building (check that all links resolve appropriately) - * Create an e-mail announcement with the subject "Bolt  Bolt  1.2.0 now available". Include a summary of the release and links to the installation instructions and release notes. ** In the From: field, enter the Google account Puppet Product Updates (puppet-product-upda...@puppet.com). ** In the Bcc: field, enter the following addresses. Send a separate message to each: internal-puppet-product-upda...@puppet.com, puppet-us...@googlegroups.com, puppet-...@googlegroups.com, and puppet-annou...@googlegroups.com. * If this release has security implications, also send to puppet-security-annou...@googlegroups.com. * If you want, make a PSA on IRC and/or Slack, something along the lines of "PSA: Bolt 1.2.0 is now available".  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
   

Jira (BOLT-459) Reboot a target and wait for it to become available.

2018-10-30 Thread Michael Fyffe (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fyffe commented on  BOLT-459  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Reboot a target and wait for it to become available.   
 

  
 
 
 
 

 
 This will be an exciting 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 (PUP-9238) pxp-agent's tests/task.run_puppet.rb test fails on Windows with PUP-9106 changes

2018-10-30 Thread Glenn Sarti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Glenn Sarti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9238  
 
 
  pxp-agent's tests/task.run_puppet.rb test fails on Windows with PUP-9106 changes   
 

  
 
 
 
 

 
Change By: 
 Glenn Sarti  
 
 
Flagged: 
 Impediment  
 

  
 
 
 
 

 
 
 

 
 
 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-459) Reboot a target and wait for it to become available.

2018-10-30 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith assigned an issue to Michael Smith  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-459  
 
 
  Reboot a target and wait for it to become available.   
 

  
 
 
 
 

 
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-9293) read_wide_string hides errors if the string is nil

2018-10-30 Thread Patrick Grant (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Grant updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9293  
 
 
  read_wide_string hides errors if the string is nil   
 

  
 
 
 
 

 
Change By: 
 Patrick Grant  
 

  
 
 
 
 

 
 *Puppet Version:*  Unknown  5.5.2 (PE 2018.1.2 Master & Agent) *Puppet Server Version:* N/A*OS Name/Version:* Windows  Server 2012r2 As part of  [  https://puppetlabs.zendesk.com/agent/tickets/32364 ]  it was found that there was a bug in the error handler in the read_wide_string method ( [ https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/api_types.rb#L56-L63 ] )Where if {{str}} is nil then an error is raised during the debug statement and raises the wrong error.  Instead the Puppet.debug statement should never error and raise the real error   
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (PUP-9268) 5.5.7 breaks custom function

2018-10-30 Thread Charlie Sharpsteen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Sharpsteen commented on  PUP-9268  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 5.5.7 breaks custom function   
 

  
 
 
 
 

 
 A linting tool makes the most sense to me. Could possibly be added to Forge lint checks along with a large demerit to the quality score if such sub-functions are found.  
 

  
 
 
 
 

 
 
 

 
 
 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-9293) read_wide_string hides errors if the string is nil

2018-10-30 Thread Glenn Sarti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Glenn Sarti commented on  PUP-9293  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: read_wide_string hides errors if the string is nil   
 

  
 
 
 
 

 
 This will probably affect all the way back to 4.10.x  
 

  
 
 
 
 

 
 
 

 
 
 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-9293) read_wide_string hides errors if the string is nil

2018-10-30 Thread Glenn Sarti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Glenn Sarti commented on  PUP-9293  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: read_wide_string hides errors if the string is nil   
 

  
 
 
 
 

 
 Example stack trace  
 
 
 
 
 Failed to apply catalog: undefined method `dump' for nil:NilClass  
 
 
    
 
 
 C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:61:in `rescue in read_wide_string'  
 
 
    
 
 
 C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/windows/api_types.rb:56:in `read_wide_string'  
 
 
    
 
 
 C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:213:in `block in read'  
 
 
    
 
 
 C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:255:in `block (3 levels) in query_value_ex'  
 
 
    
 
 
 C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/windows/registry.rb:244:in `initialize'
  
 
 
 
   
 

 

Jira (PUP-9293) read_wide_string hides errors if the string is nil

2018-10-30 Thread Glenn Sarti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Glenn Sarti created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9293  
 
 
  read_wide_string hides errors if the string is nil   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/10/30 3:27 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Glenn Sarti  
 

  
 
 
 
 

 
 Puppet Version: Unknown Puppet Server Version: N/A OS Name/Version: Windows As part of https://puppetlabs.zendesk.com/agent/tickets/32364 it was found that there was a bug in the error handler in the read_wide_string method (https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/api_types.rb#L56-L63) Where if str is nil then an error is raised during the debug statement and raises the wrong error. Instead the Puppet.debug statement should never error and raise the real error  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
   

Jira (BOLT-941) Publish apply_helpers to forge and document it's installation

2018-10-30 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith commented on  BOLT-941  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Publish apply_helpers to forge and document it's installation   
 

  
 
 
 
 

 
 For testing, we can 
 
test Bolt + apply_helpers with Orchestrator 
include apply_helpers in Bolt to replace the tasks in libexec 
  
 

  
 
 
 
 

 
 
 

 
 
 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-941) Publish apply_helpers to forge and document it's installation

2018-10-30 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith commented on  BOLT-941  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Publish apply_helpers to forge and document it's installation   
 

  
 
 
 
 

 
 Initial updates at https://github.com/puppetlabs/puppetlabs-apply_helpers/pull/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 (BOLT-941) Publish apply_helpers to forge and document it's installation

2018-10-30 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith commented on  BOLT-941  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Publish apply_helpers to forge and document it's installation   
 

  
 
 
 
 

 
 One wrinkle in this plan: to get custom facts, they'll need to use apply_prep. And apply_prep depends on tasks in an unreleased version of the puppet_agent module.  
 

  
 
 
 
 

 
 
 

 
 
 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-9292) use-after-free in windows service utils

2018-10-30 Thread Sean McDonald (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean McDonald commented on  PUP-9292  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: use-after-free in windows service utils   
 

  
 
 
 
 

 
 Nevermind, I forgot you don't need to clone or dup integers. You can still reproduce the use-after-free scenario if someone tries to return the reference to the object yielded inside the queries (or if someone tries to assign the pointers returned for the string values from the config query). These are unlikely scenarios and we should probably be fine. I do still think that the first option is handy because the string values for the config query will already be pulled in to ruby strings so any functions that call query won't need to do that. Plus the first change requires less code to work.   
 

  
 
 
 
 

 
 
 

 
 
 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-9292) use-after-free in windows service utils

2018-10-30 Thread Sean McDonald (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean McDonald commented on  PUP-9292  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: use-after-free in windows service utils   
 

  
 
 
 
 

 
 There's two PRs open to fix this: One that copies the return values to ruby memory: https://github.com/puppetlabs/puppet/pull/7213 and another that changes the service query functions to execute blocks and yield the returned values: https://github.com/puppetlabs/puppet/pull/7214 The second option leaves open the possibility to reproduce the use-after-free scenario if in the future other functions make use of the service query functions and assign the values in the returned structs to variables meant to exist outside the blocks given to the query functions. You can assign the values to variables, but you must use .dup or .clone when doing so, otherwise you'll be right back in use-after-free land. Forgetting about .dup/.clone is easy, and I believe makes it easy to recreate this scenario. The first option however will make more garbage for the GC to collect. Though IMO in context it doesn't seem like that much: status queries would be the ones returning all the garbage, and they would only return a hash with 9 integers which seems pretty small to me.  
 

  
 
 
 
 

 
 
 

 
 
 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-941) Publish apply_helpers to forge and document it's installation

2018-10-30 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith assigned an issue to Michael Smith  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-941  
 
 
  Publish apply_helpers to forge and document it's installation   
 

  
 
 
 
 

 
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 (BOLT-858) I want to apply a manifest remotely without a plan

2018-10-30 Thread Kate Lopresti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kate Lopresti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-858  
 
 
  I want to apply a manifest remotely without a plan   
 

  
 
 
 
 

 
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 (PUP-9217) Crontab gets erased after error during agent run

2018-10-30 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9217  
 
 
  Crontab gets erased after error during agent run   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Fix Version/s: 
 PUP 5.5.9  
 

  
 
 
 
 

 
 
 

 
 
 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-9217) Crontab gets erased after error during agent run

2018-10-30 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9217  
 
 
  Crontab gets erased after error during agent run   
 

  
 
 
 
 

 
Change By: 
 Branan Riley  
 
 
Fix Version/s: 
 PUP 5.5.8  
 

  
 
 
 
 

 
 
 

 
 
 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-1870) Stdout in facts invalidates formatted output (yaml/json)

2018-10-30 Thread Jean Bond (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean Bond commented on  FACT-1870  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Stdout in facts invalidates formatted output (yaml/json)   
 

  
 
 
 
 

 
 Hey Branan Riley, I know you have your hands full with the 6.0.4/5.5.8 release, but I'm hoping to catch Facter release notes up. Should this have a note, and if so, what does it need to say?  
 

  
 
 
 
 

 
 
 

 
 
 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-1889) Windows operating system facts should resolve correctly for Server 2019

2018-10-30 Thread Jean Bond (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean Bond updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1889  
 
 
  Windows operating system facts should resolve correctly for Server 2019   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9292) use-after-free in windows service utils

2018-10-30 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9292  
 
 
  use-after-free in windows service utils   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Fix Version/s: 
 PUP 5.5.8  
 
 
Fix Version/s: 
 PUP 5.5.9  
 

  
 
 
 
 

 
 
 

 
 
 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-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored

2018-10-30 Thread Robert Roland (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert Roland assigned an issue to Robert Roland  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-2487  
 
 
  Allow for a "resource-events-ttl" to reduce the number of days of events that are stored   
 

  
 
 
 
 

 
Change By: 
 Robert Roland  
 
 
Assignee: 
 Robert Roland  
 

  
 
 
 
 

 
 
 

 
 
 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-8918) Finalize separation of CA from Ruby

2018-10-30 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8918  
 
 
  Finalize separation of CA from Ruby   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Epic Colour: 
 ghx-label- 1 3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9270) puppet 5.5.7 and 6.0.3 cause a stacktrace with puppetlabs-mysql 5.x series

2018-10-30 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9270  
 
 
  puppet 5.5.7 and 6.0.3 cause a stacktrace with puppetlabs-mysql 5.x series   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Flagged: 
 Impediment  
 

  
 
 
 
 

 
 
 

 
 
 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-3434) Allow certs to be signed by fingerprint

2018-10-30 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer commented on  PUP-3434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow certs to be signed by fingerprint   
 

  
 
 
 
 

 
 Should revoking by fingerprint also be supported?  
 

  
 
 
 
 

 
 
 

 
 
 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-3434) Allow certs to be signed by fingerprint

2018-10-30 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-3434  
 
 
  Allow certs to be signed by fingerprint   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 

  
 
 
 
 

 
 Puppet cert sign should support signing by fingerprint. Signing by hostname can be dangerous and/or annoying if an attacker creates certificate requests in bulk with hostnames that you want to sign. Fingerprint should not be remotely guessable, and should be the safest option. This will probably involve updates to both the CA API and the {{puppetserver ca}} command line tool.  
 

  
 
 
 
 

 
 
 

 
 
 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-3434) Allow certs to be signed by fingerprint

2018-10-30 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-3434  
 
 
  Allow certs to be signed by fingerprint   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Assignee: 
 Andrew Parker  
 

  
 
 
 
 

 
 
 

 
 
 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-3434) Allow certs to be signed by fingerprint

2018-10-30 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-3434  
 
 
  Allow certs to be signed by fingerprint   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Summary: 
 Puppet cert sign Allow certs to be signed  by fingerprint  
 

  
 
 
 
 

 
 
 

 
 
 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-9268) 5.5.7 breaks custom function

2018-10-30 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-9268  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 5.5.7 breaks custom function   
 

  
 
 
 
 

 
 Richard Pearce I have not come up with an obvious way to do that. From the implementation perspective it just uses Ruby to define things - there are lots of them so would make it slow. The implementation basically asks Ruby "do this", and then it hopes that the result is what was expected - it does check if the loaded code for a function actually did define the function - but what happened in between is opaque. To do this right, the ruby code has to be parsed in introspected. We don't want to do that at runtime.  There is some more spelunking to do regarding the exact details what happens when there are methods before the function, inside the function, and after with the hope that would reveal a practical approach of providing relevant feedback. Maybe this is best done by a linting tool? But then, not everyone uses 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 (BOLT-950) Send release announcements (Bolt 1.2.0)

2018-10-30 Thread Kate Lopresti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kate Lopresti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-950  
 
 
  Send release announcements (Bolt 1.2.0)   
 

  
 
 
 
 

 
Change By: 
 Kate Lopresti  
 

  
 
 
 
 

 
 (Initial planned release date: 2018-10-25)  Once docs have finished building (check that all links resolve appropriately) -  * Create an e-mail announcement with the subject "Bolt Bolt 1.2.0 now available". Include a summary of the release and links to the installation instructions and release notes.  * *  In the From: field, enter the Google account Puppet Product Updates (puppet-product-upda...@puppet.com).  * *  In the Bcc: field, enter the following addresses. Send a separate message to each: internal-puppet-product-upda...@puppet.com, puppet-us...@googlegroups.com, puppet-...@googlegroups.com, and puppet-annou...@googlegroups.com.* If this release has security implications, also send to puppet-security-annou...@googlegroups.com.* If you want, make a PSA on IRC and/or Slack, something along the lines of "PSA: Bolt 1.2.0 is now available".   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 


Jira (PUP-3059) add support for crlDistributionPoint

2018-10-30 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer commented on  PUP-3059  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: add support for crlDistributionPoint   
 

  
 
 
 
 

 
 I feel like there might be a way to get this to work, but it could be that we disallow that particular extension. This may be relevant for SERVER-2144. We should look into at which point using this extension is disallowed.  
 

  
 
 
 
 

 
 
 

 
 
 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-950) Send release announcements (Bolt 1.2.0)

2018-10-30 Thread Kate Lopresti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kate Lopresti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-950  
 
 
  Send release announcements (Bolt 1.2.0)   
 

  
 
 
 
 

 
Change By: 
 Kate Lopresti  
 

  
 
 
 
 

 
 (Initial planned release date: 2018-10-25)  Once docs have finished building (check that all links resolve appropriately) -*  Send the  Create an e-mail  announcement  pasted by [~kate  with the subject "Bolt Bolt 1 . lopresti] 2.0 now available". Include a summary of the release and links  to  the installation instructions and release notes.  * In the From: field, enter the Google account Puppet Product Updates (  puppet- users product-updates @ googlegroups puppet .com ).  * In the Bcc: field ,  enter the following addresses. Send a separate message to each: internal-  puppet- dev product-updates @ googlegroups puppet .com, puppet- announce users @googlegroups.com, puppet- product-updates dev @ puppet googlegroups .com, and  dev@ puppet -announce@googlegroups .com  (all separately) .  You must be a member of these groups in order to send. * If this release has security implications, also send to puppet-security-annou...@googlegroups.com.* If you want, make a PSA on IRC and/or Slack, something along the lines of "PSA: Bolt 1.2.0 is now available".  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   

Jira (PUP-8918) Finalize separation of CA from Ruby

2018-10-30 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8918  
 
 
  Finalize separation of CA from Ruby   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Epic Colour: 
 ghx-label- 6 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-8213) Error message for certificate name mismatch is clear as mud

2018-10-30 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8213  
 
 
  Error message for certificate name mismatch is clear as mud   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Team: 
 Server Coremunity  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8563) The puppet agent should have a 'local' mode for CRL checking

2018-10-30 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8563  
 
 
  The puppet agent should have a 'local' mode for CRL checking   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Team: 
 Server Coremunity  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8918) Finalize separation of CA from Ruby

2018-10-30 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8918  
 
 
  Finalize separation of CA from Ruby   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 

  
 
 
 
 

 
 This epic contains the work for  separating puppetserver  removing the CA 's  CA dir  last ties to Ruby Puppet. This includes moving settings  from Puppet  into Puppetserver and moving the CA directory under puppetserver 's  SSL dir  file tree instead of {{puppet/ssl}} . We plan to provide a path for doing this in the Puppet 6 series and move the directories  and settings  by default in Puppet 7.  
 

  
 
 
 
 

 
 
 

 
 
 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-8918) Finalize separation of CA from Ruby

2018-10-30 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer commented on  PUP-8918  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Finalize separation of CA from Ruby   
 

  
 
 
 
 

 
 Updating this epic to include both the effort to separate the dirs and the remaining work to remove our entanglement with Ruby Puppet (mostly moving settings to Puppet Server).  
 

  
 
 
 
 

 
 
 

 
 
 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-8918) Finalize separation of CA from Ruby

2018-10-30 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8918  
 
 
  Finalize separation of CA from Ruby   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Epic Name: 
 Separate CA  and SSL dirs  from Ruby  
 

  
 
 
 
 

 
 
 

 
 
 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-8918) Finalize separation of CA from Ruby

2018-10-30 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8918  
 
 
  Finalize separation of CA from Ruby   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Summary: 
 Separate Finalize separation of  CA  and SSL dirs  from Ruby  
 

  
 
 
 
 

 
 
 

 
 
 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-9292) use-after-free in windows service utils

2018-10-30 Thread Sean McDonald (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean McDonald created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9292  
 
 
  use-after-free in windows service utils   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 6.0.3, PUP 5.5.6  
 
 
Assignee: 
 Sean McDonald  
 
 
Created: 
 2018/10/30 11:22 AM  
 
 
Fix Versions: 
 PUP 5.5.8, PUP 6.0.5  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Sean McDonald  
 

  
 
 
 
 

 
 The windows service utils have a use-after-free failure in the query functions  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 
  

Jira (BOLT-905) [SPIKE] Investigate performance issues around concurrent connections over winrm

2018-10-30 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman assigned an issue to Lucy Wyman  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-905  
 
 
  [SPIKE] Investigate performance issues around concurrent connections over winrm   
 

  
 
 
 
 

 
Change By: 
 Lucy Wyman  
 
 
Assignee: 
 Lucy Wyman  
 

  
 
 
 
 

 
 
 

 
 
 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-858) I want to apply a manifest remotely without a plan

2018-10-30 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-858  
 
 
  I want to apply a manifest remotely without a plan   
 

  
 
 
 
 

 
Change By: 
 Nick Lewis  
 
 
Release Notes Summary: 
 This introduces a new command `bolt apply`, which is used to directly apply Puppet manifest code on targets without having to wrap them in an `apply()` block in a plan.  
 

  
 
 
 
 

 
 
 

 
 
 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-917) BoltServer should return json error responses

2018-10-30 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman commented on  BOLT-917  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: BoltServer should return json error responses   
 

  
 
 
 
 

 
 Alex Dreyer Do we want to construct an error hash with 'msg', 'kind', and 'details', or just call 'generate' on the error message?  
 

  
 
 
 
 

 
 
 

 
 
 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-9150) cwd option in Puppet::Util::Execution.execute should work with different Windows path types

2018-10-30 Thread Sean McDonald (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean McDonald updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9150  
 
 
  cwd option in Puppet::Util::Execution.execute should work with different Windows path types   
 

  
 
 
 
 

 
Change By: 
 Sean McDonald  
 
 
Fix Version/s: 
 PUP 6.0.5  
 

  
 
 
 
 

 
 
 

 
 
 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-9150) cwd option in Puppet::Util::Execution.execute should work with different Windows path types

2018-10-30 Thread Sean McDonald (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean McDonald commented on  PUP-9150  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: cwd option in Puppet::Util::Execution.execute should work with different Windows path types   
 

  
 
 
 
 

 
 Enis Inan I don't think CreateProcess actually has a security issue. It appears that CreateProcess won't fail when starting in the directory, but as soon as any operation is executed on the directory it will fail. technically it appears you would be inside the directory when CreateProcess starts, but you don't have access to anything inside it, you can't navigate within the directory (i.e. if there are other dirs inside the dir in question you can't access them), and you can't copy anything in or out. I've run a few tests and it appears windows will let you list your cwd, which wouldn't violate any security rules, because you can still view the existence of the top folder you can't access.  However if you attempt any operations inside a nested dir (i.e. a dir you know exists but you don't have access to it's parent or itself) the operations will fail. I think in this scenario we can stick to just setting :cwd directly with CreateProcess and let that fail.   
 

  
 
 
 
 

 
 
 

 
 
 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-917) BoltServer should return json error responses

2018-10-30 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman assigned an issue to Lucy Wyman  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-917  
 
 
  BoltServer should return json error responses   
 

  
 
 
 
 

 
Change By: 
 Lucy Wyman  
 
 
Assignee: 
 Lucy Wyman  
 

  
 
 
 
 

 
 
 

 
 
 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-9268) 5.5.7 breaks custom function

2018-10-30 Thread Richard Pearce (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Pearce commented on  PUP-9268  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 5.5.7 breaks custom function   
 

  
 
 
 
 

 
 I fell over this today, it was exceptionally hard to track it back to this bug.  Given that you have decided to revert, would it be possible to implement a warning for functions that 'pollute scope' and output it on the Puppet run? This would give everyone visibility of this problem and drive everyone to adopt the newer API.  
 

  
 
 
 
 

 
 
 

 
 
 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-858) I want to apply a manifest remotely without a plan

2018-10-30 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith assigned an issue to Michael Smith  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-858  
 
 
  I want to apply a manifest remotely without a plan   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Assignee: 
 Nick Lewis 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 (PDB-4174) Encoding issue submitting facts from package inventory

2018-10-30 Thread Erik Hansen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Erik Hansen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4174  
 
 
  Encoding issue submitting facts from package inventory   
 

  
 
 
 
 

 
Change By: 
 Erik Hansen  
 
 
Affects Version/s: 
 PDB 5.2.4  
 

  
 
 
 
 

 
 
 

 
 
 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-645) Support puppet device modules in a manifest block

2018-10-30 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer assigned an issue to Alex Dreyer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-645  
 
 
  Support puppet device modules in a manifest block   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
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 (PUP-1214) File resources: Make source/content parameters and the file/template functions consistent.

2018-10-30 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-1214  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: File resources: Make source/content parameters and the file/template functions consistent.   
 

  
 
 
 
 

 
 I would much rather see a separate function that returns the first existing file/template given a list of paths. Such a function can then also accept different suffixes and this function can then be used with all kinds of functions taking a path (for example epp()). There is a find_file function in puppet core, but no find_template.  
 

  
 
 
 
 

 
 
 

 
 
 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-4174) Encoding issue submitting facts from package inventory

2018-10-30 Thread Rob Browning (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning commented on  PDB-4174  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Encoding issue submitting facts from package inventory   
 

  
 
 
 
 

 
 In newer versions, I suspect this should be handled by the "universal" null escaping here: https://github.com/puppetlabs/puppetdb/blob/master/src/puppetlabs/puppetdb/cheshire.clj#L118 And note that puppetdb cannot store unicode nulls in string values (hence that mangling above).  
 

  
 
 
 
 

 
 
 

 
 
 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-4174) Encoding issue submitting facts from package inventory

2018-10-30 Thread Rob Browning (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning commented on  PDB-4174  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Encoding issue submitting facts from package inventory   
 

  
 
 
 
 

 
 Erik Hansen which version of pdb was this?  
 

  
 
 
 
 

 
 
 

 
 
 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-9150) cwd option in Puppet::Util::Execution.execute should work with different Windows path types

2018-10-30 Thread Sean McDonald (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean McDonald assigned an issue to Sean McDonald  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9150  
 
 
  cwd option in Puppet::Util::Execution.execute should work with different Windows path types   
 

  
 
 
 
 

 
Change By: 
 Sean McDonald  
 
 
Assignee: 
 Enis Inan Sean McDonald  
 

  
 
 
 
 

 
 
 

 
 
 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-131) Simplify tasks for repeatable code and importing code

2018-10-30 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-131  
 
 
  Simplify tasks for repeatable code and importing code   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Fix Version/s: 
 BOLT 1.1.0  
 
 
Fix Version/s: 
 PE 2019.0.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 (BOLT-131) Simplify tasks for repeatable code and importing code

2018-10-30 Thread David Kramer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Kramer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-131  
 
 
  Simplify tasks for repeatable code and importing code   
 

  
 
 
 
 

 
Change By: 
 David Kramer  
 
 
Epic Status: 
 To Do Done  
 

  
 
 
 
 

 
 
 

 
 
 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-645) Support puppet device modules in a manifest block

2018-10-30 Thread David Kramer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Kramer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-645  
 
 
  Support puppet device modules in a manifest block   
 

  
 
 
 
 

 
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 (PUP-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency

2018-10-30 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-6964  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency   
 

  
 
 
 
 

 
 This was reverted for Puppet 5.5.8, but is in effect for Puppet >= 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-9268) 5.5.7 breaks custom function

2018-10-30 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-9268  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 5.5.7 breaks custom function   
 

  
 
 
 
 

 
 The specification has been updated with stronger language regarding having extra methods in a legacy (3.x) function.  
 

  
 
 
 
 

 
 
 

 
 
 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-9270) puppet 5.5.7 and 6.0.3 cause a stacktrace with puppetlabs-mysql 5.x series

2018-10-30 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9270  
 
 
  puppet 5.5.7 and 6.0.3 cause a stacktrace with puppetlabs-mysql 5.x series   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Release Notes Summary: 
 When a legacy function does not comply with the rules for how it should be written it caused Puppet 5.5.7 and Puppet 6.0.0 to fail with a faulty error message. This is now fixed in Puppet 5.5.8 by accepting the illegal implementation of the function. For Puppet 6.0.4 the intended error will be raised.  
 
 
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-9270) puppet 5.5.7 and 6.0.3 cause a stacktrace with puppetlabs-mysql 5.x series

2018-10-30 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9270  
 
 
  puppet 5.5.7 and 6.0.3 cause a stacktrace with puppetlabs-mysql 5.x series   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Summary: 
 puppet 5.5.7  causes  and 6.0.3 cause  a stacktrace with puppetlabs-mysql 5.x series  
 

  
 
 
 
 

 
 
 

 
 
 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-9263) Modulepath should not be case sensitive on case insensitive file systems

2018-10-30 Thread Jacob Helwig (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Helwig assigned an issue to Jacob Helwig  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9263  
 
 
  Modulepath should not be case sensitive on case insensitive file systems   
 

  
 
 
 
 

 
Change By: 
 Jacob Helwig  
 
 
Assignee: 
 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 (BOLT-915) Make the shell facts implementation sharable and use it in the puppet_agent task

2018-10-30 Thread Kate Lopresti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kate Lopresti commented on  BOLT-915  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make the shell facts implementation sharable and use it in the puppet_agent task   
 

  
 
 
 
 

 
 Cas Donoghue that's fine. I just needed info in the Docs tab to filter it out. Thanks.  
 

  
 
 
 
 

 
 
 

 
 
 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-9270) puppet 5.5.7 causes a stacktrace with puppetlabs-mysql 5.x series

2018-10-30 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-9270  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet 5.5.7 causes a stacktrace with puppetlabs-mysql 5.x series   
 

  
 
 
 
 

 
 Merged to 6.0.x in https://github.com/puppetlabs/puppet/commit/998ec0e3e4020c6e34e6d08a9eddb2e3cb36f7a5  
 

  
 
 
 
 

 
 
 

 
 
 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-4174) Encoding issue submitting facts from package inventory

2018-10-30 Thread Erik Hansen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Erik Hansen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4174  
 
 
  Encoding issue submitting facts from package inventory   
 

  
 
 
 
 

 
Change By: 
 Erik Hansen  
 
 
Security: 
 Internal  
 

  
 
 
 
 

 
 
 

 
 
 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-9289) lookup_options/convert_to should be able to convert values in hashes

2018-10-30 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9289  
 
 
  lookup_options/convert_to should be able to convert values in hashes   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Team: 
 Server  
 

  
 
 
 
 

 
 
 

 
 
 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-9290) `puppet facts upload` always uses environment "production" ignoring setting from puppet.conf

2018-10-30 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9290  
 
 
  `puppet facts upload` always uses environment "production" ignoring setting from puppet.conf   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
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-9289) lookup_options/convert_to should be able to convert values in hashes

2018-10-30 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9289  
 
 
  lookup_options/convert_to should be able to convert values in hashes   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sub-team: 
 Language  
 

  
 
 
 
 

 
 
 

 
 
 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-9290) `puppet facts upload` always uses environment "production" ignoring setting from puppet.conf

2018-10-30 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-9290  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: `puppet facts upload` always uses environment "production" ignoring setting from puppet.conf   
 

  
 
 
 
 

 
 In lib/puppet/face/facts.rb, we need to specify the environment when trying to save the facts, something like:  
 
 
 
 
   Puppet::Node::Facts.indirection.save(facts, nil, :environment => Puppet::Node::Environment.remote(Puppet[:environment]))
  
 
 
 
   
 

  
 
 
 
 

 
 
 

 
 
 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-9290) `puppet facts upload` always uses environment "production" ignoring setting from puppet.conf

2018-10-30 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9290  
 
 
  `puppet facts upload` always uses environment "production" ignoring setting from puppet.conf   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Team: 
 Coremunity  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9289) lookup_options/convert_to should be able to convert values in hashes

2018-10-30 Thread Daniel Parks (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Parks commented on  PUP-9289  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: lookup_options/convert_to should be able to convert values in hashes   
 

  
 
 
 
 

 
 I figured this would a tricky one. Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 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-9289) lookup_options/convert_to should be able to convert values in hashes

2018-10-30 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-9289  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: lookup_options/convert_to should be able to convert values in hashes   
 

  
 
 
 
 

 
 Need to think about if it is always ok for `convert_to` to use a Tuple, Array, Hash, Struct and convert input according to their type parameters. As this is implemented now, the function simply delegates to the given data type - it has no knowledge on its own about conversion or types.   
 

  
 
 
 
 

 
 
 

 
 
 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-9289) lookup_options/convert_to should be able to convert values in hashes

2018-10-30 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9289  
 
 
  lookup_options/convert_to should be able to convert values in hashes   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Issue Type: 
 Improvement 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 (PUP-9291) 5x Agent Unable to Communicate with 6x Master via SSL

2018-10-30 Thread Charlie Sharpsteen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Sharpsteen commented on  PUP-9291  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 5x Agent Unable to Communicate with 6x Master via SSL   
 

  
 
 
 
 

 
 
 
if the CA should have to be regenerated at some point things will fail
 Also, for posterity, if you take a backup of nothing else in Puppet install, take a backup the CA files. They're small and save heaps of time and trouble on those rainy days where someone ran rm -rf /etc/puppetlabs/puppet/ssl in the wrong terminal window   
 

  
 
 
 
 

 
 
 

 
 
 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-9291) 5x Agent Unable to Communicate with 6x Master via SSL

2018-10-30 Thread Michael Lombardi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Lombardi assigned an issue to Charlie Sharpsteen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This ended up being a known limitation of Puppet 5, not a bug in Puppet 6; Charlie Sharpsteen's suggestion fixed the issue.  
 

  
 
 
 
 

 
 Puppet /  PUP-9291  
 
 
  5x Agent Unable to Communicate with 6x Master via SSL   
 

  
 
 
 
 

 
Change By: 
 Michael Lombardi  
 
 
Resolution: 
 Won't Fix  
 
 
Assignee: 
 Charlie Sharpsteen  
 
 
Status: 
 Open Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
   

Jira (PUP-9291) 5x Agent Unable to Communicate with 6x Master via SSL

2018-10-30 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer commented on  PUP-9291  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 5x Agent Unable to Communicate with 6x Master via SSL   
 

  
 
 
 
 

 
 Puppet 5 agents are known to not work correctly with intermediate CAs, and new (or regenerated) Puppet 6 masters have an intermediate CA by default. We do not recommend using Puppet 5 agents with 6 masters long term (upgrades that keep the old SSL artifacts are fine, but if the CA should have to be regenerated at some point things will fail), but if you must, all the caveats about Puppet 5 agents with intermediate CAs still apply. For instructions on how to handle that, see https://puppet.com/docs/puppetserver/5.3/intermediate_ca_configuration.html. The important pieces for this setup are: 1) Set CRL checking to "leaf" or "false" 2) Manually distribute ca_crt.pem and ca_crl.pem to the agent. No action should be needed server side. For information on Puppet 6's intermediate CA, see https://puppet.com/docs/puppetserver/6.0/intermediate_ca.html.  
 

  
 
 
 
 

 
 
 

 
 
 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-9291) 5x Agent Unable to Communicate with 6x Master via SSL

2018-10-30 Thread Michael Lombardi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Lombardi commented on  PUP-9291  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 5x Agent Unable to Communicate with 6x Master via SSL   
 

  
 
 
 
 

 
 Following along that doc and running puppet config set --section main certificate_revocation leaf seems to have worked. Happy to update my testing doc and close this, thanks for the quick turnaround!  
 

  
 
 
 
 

 
 
 

 
 
 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-9291) 5x Agent Unable to Communicate with 6x Master via SSL

2018-10-30 Thread Charlie Sharpsteen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Sharpsteen commented on  PUP-9291  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 5x Agent Unable to Communicate with 6x Master via SSL   
 

  
 
 
 
 

 
 Puppet Agent 5.x and earlier did not support CRL files that had been issued by intermediate CAs. Historically, use of these agents with an intermediate CA required CRL checking to be disabled: https://puppet.com/docs/puppetserver/5.3/intermediate_ca_configuration.html#puppet-agent-has-certificaterevocation-set-to-true If disabling CRL checking solves the issue, then this is not a bug in Puppet 6 but rather a limitation of Puppet 5 and earlier that was removed as part of the CA work in Puppet 6.  
 

  
 
 
 
 

 
 
 

 
 
 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-9291) 5x Agent Unable to Communicate with 6x Master via SSL

2018-10-30 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey commented on  PUP-9291  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 5x Agent Unable to Communicate with 6x Master via SSL   
 

  
 
 
 
 

 
 Maggie Dreyer might you be able to chime in here?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9291) 5x Agent Unable to Communicate with 6x Master via SSL

2018-10-30 Thread Michael Lombardi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Lombardi updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9291  
 
 
  5x Agent Unable to Communicate with 6x Master via SSL   
 

  
 
 
 
 

 
Change By: 
 Michael Lombardi  
 
 
Issue Type: 
 Improvement Bug  
 

  
 
 
 
 

 
 
 

 
 
 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-9291) 5x Agent Unable to Communicate with 6x Master via SSL

2018-10-30 Thread Michael Lombardi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Lombardi updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9291  
 
 
  5x Agent Unable to Communicate with 6x Master via SSL   
 

  
 
 
 
 

 
Change By: 
 Michael Lombardi  
 
 
Summary: 
 5x Agent Unable to Communicate with  5x  6x  Master via SSL  
 

  
 
 
 
 

 
 
 

 
 
 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-9291) 5x Agent Unable to Communicate with 5x Master via SSL

2018-10-30 Thread Michael Lombardi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Lombardi created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9291  
 
 
  5x Agent Unable to Communicate with 5x Master via SSL   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Affects Versions: 
 PUP 6.0.0, PUP 5.5.7  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/10/30 7:40 AM  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Michael Lombardi  
 

  
 
 
 
 

 
 During testing for MODULES-8172 we discovered that a downgraded node (6.0.0 => 5.5.7) was no longer able to communicate with the puppet server due to SSL errors. A clean secondary node was spun up, Puppet 5.5.7 installed, and was also unable to communicate. Current predictions: 1. In environments where the server was upgraded from 5-6 and then the agents were upgraded, everything is "fine" until certs need to be regenerated. 2. In environments where a user tries to add a server with a 5x agent to a 6x master, it will fail. Repro (via Glenn Sarti): 
 
Install a Puppet 6 master (2019.0) 
Install a Puppet 6 Agent and connect succesfully. At this point the ca.pem contains two certificates Serial #1 of the CA and Serial #2 of the CA. Also the crl.pem file contains two CRL entries. I assume one for each Serial number of the CA cert. Puppet 6 agent is working correctly 
Downgrade Puppet Agent to 5.5.7 (This keeps the SSL dir intact) At this point 'puppet agent -t' fails with a CRL verification error Error: Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=error: certificate verify failed: [unable to get certificate CRL for /CN=Puppet Enterprise CA generated on n7yftyzqgmyz5wy.delivery.puppetlabs.net at +2018-10-30 00:56:12 +] 
Delete the crl.pem file and run 'puppet agent -t' This recreates/redownloads the crl.pem file. The puppet agent now works correctly, but note 

Jira (PUP-1214) File resources: Make source/content parameters and the file/template functions consistent.

2018-10-30 Thread Rob Reus (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Reus commented on  PUP-1214  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: File resources: Make source/content parameters and the file/template functions consistent.   
 

  
 
 
 
 

 
 Nicholas Fagerlund this is incorrect. Both functions (file() and template()) have not been changed according to git history. The original idea is to have the template() function also accept an array like the source parameter does. The first existing file in the array would then be used as template file. Right now, concatenation of multiple templates into one by providing multiple template files separated by commas still work. The proposed change has not been applied. Example: module dir  
 
 
 
 
 .  
 
 
 └── test  
 
 
 ├── files  
 
 
 │   ├── foobar  
 
 
 │   └── foobaz  
 
 
 ├── manifests  
 
 
 │   └── init.pp  
 
 
 └── templates  
 
 
 ├── foobar.erb  
 
 
 └── foobaz.erb  
 
 
 
  init.pp  
 
 
 
 
 class test {  
 

Jira (BOLT-921) Updates to Bolt installation docs

2018-10-30 Thread Gene Liverman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gene Liverman commented on  BOLT-921  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Updates to Bolt installation docs   
 

  
 
 
 
 

 
 Looks good now   
 

  
 
 
 
 

 
 
 

 
 
 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-9270) puppet 5.5.7 causes a stacktrace with puppetlabs-mysql 5.x series

2018-10-30 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg assigned an issue to Josh Cooper  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9270  
 
 
  puppet 5.5.7 causes a stacktrace with puppetlabs-mysql 5.x series   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Assignee: 
 Henrik Lindberg Josh Cooper  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9289) lookup_options/convert_to should be able to convert values in hashes

2018-10-30 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9289  
 
 
  lookup_options/convert_to should be able to convert values in hashes   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Component/s: 
 Hiera & Lookup  
 

  
 
 
 
 

 
 
 

 
 
 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-9289) lookup_options/convert_to should be able to convert values in hashes

2018-10-30 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-9289  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: lookup_options/convert_to should be able to convert values in hashes   
 

  
 
 
 
 

 
 That would require a different kind of transformation than what the basic data types perform, or a convert_to that takes a data type specifically designed to do that transformation. It would then produce an instance of that data type (not a hash) as the value returned from a lookup.  
 

  
 
 
 
 

 
 
 

 
 
 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-9290) `puppet facts upload` always uses environment "production" ignoring setting from puppet.conf

2018-10-30 Thread Greg Dubicki (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Greg Dubicki commented on  PUP-9290  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: `puppet facts upload` always uses environment "production" ignoring setting from puppet.conf   
 

  
 
 
 
 

 
 Running `/opt/puppetlabs/puppet/bin/puppet facts upload --environment qa` does not 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-954) Add support for bolt apply to BoltSpec::Run

2018-10-30 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-954  
 
 
  Add support for bolt apply to BoltSpec::Run   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/10/30 5:44 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Lucy Wyman  
 

  
 
 
 
 

 
 *As a* developer using the BoltSpec::Run library *I want* to be able to apply Puppet code directly to targets from a rake task *So that* I can use existing forge modules to provision targets to use for testing. We should include a function apply in the BoltSpec::Run module that allows users to apply a manifest or block of Puppet code to a list of targets.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

Jira (PUP-9290) `puppet facts upload` always uses environment "production" ignoring setting from puppet.conf

2018-10-30 Thread Greg Dubicki (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Greg Dubicki updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9290  
 
 
  `puppet facts upload` always uses environment "production" ignoring setting from puppet.conf   
 

  
 
 
 
 

 
Change By: 
 Greg Dubicki  
 

  
 
 
 
 

 
 We have nodes with environment different than default "production", in here it's "qa":{code}[r...@app03.xxx:~]# cat /etc/puppet/puppet.conf(...)[agent]report      = trueruninterval = 1800environment = qasplay = true{code}But if we upload facts using `puppet facts upload` always environment "production" is being used:{code}[r...@app03.xxx:~]# /opt/puppetlabs/puppet/bin/puppet facts upload --debugDebug: Runtime environment: puppet_version=5.5.2, ruby_version=2.4.4, run_mode=user, default_encoding=UTF-8Debug: Evicting cache entry for environment 'production'(...){code} We observe than then in In  puppetdb , because  facts from such nodes have "facts_environment" set to "production", while "report_environment" and "catalog_environment" are set correctly to "qa".If you simply run "puppet agent -t" facts with correct environment, "qa", are being uploaded.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 
   

Jira (BOLT-953) Add file_upload support to BoltSpec

2018-10-30 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-953  
 
 
  Add file_upload support to BoltSpec   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/10/30 5:39 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Lucy Wyman  
 

  
 
 
 
 

 
 We should add a function to BoltSpec::Run that allows users to upload files to the remote systems.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 
  

Jira (PUP-9290) `puppet facts upload` always uses environment "production" ignoring setting from puppet.conf

2018-10-30 Thread Greg Dubicki (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Greg Dubicki created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9290  
 
 
  `puppet facts upload` always uses environment "production" ignoring setting from puppet.conf   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 5.5.2  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/10/30 5:37 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Greg Dubicki  
 

  
 
 
 
 

 
 We have nodes with environment different than default "production", in here it's "qa":  
 
 
 
 
 [r...@app03.xxx:~]# cat /etc/puppet/puppet.conf  
 
 
 (...)  
 
 
 [agent]  
 
 
 report      = true  
 
 
 runinterval = 1800  
 
 
 environment = qa