Jira (PUP-6330) puppet uninstall exe resource fails on windows due to missing quotes

2016-06-14 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6330 
 
 
 
  puppet uninstall exe resource fails on windows due to missing quotes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Scrum Team:
 
 Windows 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6330) puppet uninstall exe resource fails on windows due to missing quotes

2016-06-14 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6330 
 
 
 
  puppet uninstall exe resource fails on windows due to missing quotes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Sprint:
 
 Windows Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-3077) When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment

2016-06-14 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-3077 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment  
 
 
 
 
 
 
 
 
 
 
Shane Madden since 3.x is on maintenance only, this will probably take a community-driven backport to move it forward. Also, note that there is no scheduled 3.x release at this time (although, since as you say, it will be around for a bit longer, I won't be surprised if there does end up being another 3.x release at some point.) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-2819) Managed files on FUSE without chmod/chown functionality

2016-06-14 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2819 
 
 
 
  Managed files on FUSE without chmod/chown functionality  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-2819) Managed files on FUSE without chmod/chown functionality

2016-06-14 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-2819 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Managed files on FUSE without chmod/chown functionality  
 
 
 
 
 
 
 
 
 
 
Alex Hart thanks for testing this out with 4.5; I'll update the affected version. 
But alas, no updates. Since this ticket doesn't have much in the way of votes or watchers, it'll probably take a community contribution to move it forward. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-2819) Managed files on FUSE without chmod/chown functionality

2016-06-14 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2819 
 
 
 
  Managed files on FUSE without chmod/chown functionality  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Affects Version/s:
 
 PUP 4.5.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-3077) When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment

2016-06-14 Thread Shane Madden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shane Madden commented on  PUP-3077 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment  
 
 
 
 
 
 
 
 
 
 
Thanks a lot for getting this fixed, but is there any word on whether this will be fixed in the 3.8 maintenance releases? We've had compatibility issues blocking the 4.x upgrade, so we're still forced to run with `ignorecache` as a workaround. 
We were very surprised today when a catalog from an environment that had never been run without `-

noop` applied itself without warning or user input and took down a production system; confidence in the `
-noop` flag is extremely important for confidence in Puppet in general, so it'd be great if this made fix made it into the 3.x releases which will be around at least a little while longer. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-2785) spec tests failing against puppet master

2016-06-14 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2785 
 
 
 
  spec tests failing against puppet master  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/14 4:13 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
see: https://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_mergely-master/244/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
  

Jira (PUP-6347) new function (String): programmatic representation escapes for Ruby language and not Puppet

2016-06-14 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6347 
 
 
 
  new function (String): programmatic representation escapes for Ruby language and not Puppet  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Fix Version/s:
 
 PUP 4.5.3 
 
 
 

Fix Version/s:
 
 PUP 4.5.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6314) Numeric.new (and subtypes) does not accept whitespace between sign and leading digit

2016-06-14 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6314 
 
 
 
  Numeric.new (and subtypes) does not accept whitespace between sign and leading digit  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Fix Version/s:
 
 PUP 4.5.3 
 
 
 

Fix Version/s:
 
 PUP 4.5.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6346) new function (String): not all string-based conversions respect width and precision

2016-06-14 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6346 
 
 
 
  new function (String): not all string-based conversions respect width and precision  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Fix Version/s:
 
 PUP 4.5.3 
 
 
 

Fix Version/s:
 
 PUP 4.5.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6358) Set strict_variables = true, if strict = error is set

2016-06-14 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6358 
 
 
 
  Set strict_variables = true, if strict = error is set  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Fix Version/s:
 
 PUP 4.5.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6398) Executing parallel specs on Windows is not reliable

2016-06-14 Thread Daniel Lu (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Lu updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6398 
 
 
 
  Executing parallel specs on Windows is not reliable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Lu 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6407) Explore implemenation of Environment Isolation - resource type in pcore

2016-06-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6407 
 
 
 
  Explore implemenation of Environment Isolation - resource type in pcore  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Henrik Lindberg 
 
 
 

Created:
 

 2016/06/14 3:05 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6310) Specify the PCore Serialization formats

2016-06-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6310 
 
 
 
  Specify the PCore Serialization formats  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 Language 2016- 06 07 - 29 13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6255) Add documentation for Object.new in function new

2016-06-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6255 
 
 
 
  Add documentation for Object.new in function new  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 Language 2016- 06 07 - 29 13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6083) Use --strict option to deprecate Class[] where begins with a capital letter.

2016-06-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6083 
 
 
 
  Use --strict option to deprecate Class[] where  begins with a capital letter.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 Language 2016- 06 07 - 29 13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6252) reorganize documentation of function 'new'

2016-06-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6252 
 
 
 
  reorganize documentation of function 'new'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 Language 2016- 06 07 - 29 13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-3170) Cap integer and float sizes

2016-06-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3170 
 
 
 
  Cap integer and float sizes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 Language 2016- 06 07 - 29 13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6312) Load XPP instead of .pp if present and feature flag is on

2016-06-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6312 
 
 
 
  Load XPP instead of .pp if present and feature flag is on  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 Language 2016- 06 07 - 29 13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-1364) Yum package arch and version ensuring failing

2016-06-14 Thread Peter Souter (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Souter updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1364 
 
 
 
  Yum package arch and version ensuring failing  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Souter 
 
 
 

Fix Version/s:
 
 PUP 4.5.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDOC-79) [SPIKE] Define the set of tickets needed to get strings working for docs needs

2016-06-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-79 
 
 
 
  [SPIKE] Define the set of tickets needed to get strings working for docs needs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 Language 2016-06-01, Language 2016- 06 07 - 29 13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6385) No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs

2016-06-14 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6385 
 
 
 
  No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Scope Change Category:
 
 Found 
 
 
 

Scope Change Reason:
 
 Community reported major issue. "Found" because blocked release. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-3827) Errors from indirected routes don't match error schema

2016-06-14 Thread Erik Dasher (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Dasher assigned an issue to Erik Dasher 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3827 
 
 
 
  Errors from indirected routes don't match error schema  
 
 
 
 
 
 
 
 
 

Change By:
 
 Erik Dasher 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Assignee:
 
 qa Erik Dasher 
 
 
 

Status:
 
 Ready for Test Resolved 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6383) Acceptance: test that failover information is added to the report

2016-06-14 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6383 
 
 
 
  Acceptance: test that failover information is added to the report  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Labels:
 
 ha-dep 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6384) Acceptance: test that agent failover behavior works correctly

2016-06-14 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6384 
 
 
 
  Acceptance: test that agent failover behavior works correctly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Labels:
 
 ha-dep 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-2819) Managed files on FUSE without chmod/chown functionality

2016-06-14 Thread Alex Hart (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Hart commented on  PUP-2819 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Managed files on FUSE without chmod/chown functionality  
 
 
 
 
 
 
 
 
 
 
This is apparently still an issue in 4.5. Any updates? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-2784) (maint) Add a basic acceptance test

2016-06-14 Thread Andrew Roetker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Roetker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2784 
 
 
 
  (maint) Add a basic acceptance test  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Roetker 
 
 
 

Sprint:
 
 Hopper 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-2784) (maint) Add a basic acceptance test

2016-06-14 Thread Andrew Roetker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Roetker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2784 
 
 
 
  (maint) Add a basic acceptance test  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Roetker 
 
 
 

Fix Version/s:
 
 PDB CLI 1.1.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-2784) (maint) Add a basic acceptance test

2016-06-14 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2784 
 
 
 
  (maint) Add a basic acceptance test  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/14 2:10 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
This commit adds a basic acceptance test for the CLI that can be shared by FOSS and PE. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
   

Jira (PUP-6394) Allow service resources to come from other code ids

2016-06-14 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6394 
 
 
 
  Allow service resources to come from other code ids  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-2783) Revisit command versioning

2016-06-14 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2783 
 
 
 
  Revisit command versioning  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/14 1:18 PM 
 
 
 

Fix Versions:
 

 PDB 4.2.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Ryan Senior 
 
 
 
 
 
 
 
 
 
 
We currently require incrementing the command version with any change (including the addition of new fields). Incrementing versions is a significant amount of work with not a lot of benefits. We revisited versioning of the query endpoints a while back (that resulted in the creation of this document, we should do that same thing with commands. 
This ticket involves 
 

Sending out a proposal to the team
 

Might need a facilitate a face to face meeting to talk it through
 

Update the version policy
 
 
 
 
 
 
 
 
 
 
 
 
   

Jira (PDB-2782) Producer should be a queryable entity

2016-06-14 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2782 
 
 
 
  Producer should be a queryable entity  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/14 1:08 PM 
 
 
 

Labels:
 

 ha-dep 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Ryan Senior 
 
 
 
 
 
 
 
 
 
 
Similar to environment we should have an endpoint for it, PQL support etc. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 

Jira (PUP-6406) HA: Client Failover

2016-06-14 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6406 
 
 
 
  HA: Client Failover  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Epic Colour:
 
 ghx-label- 5 6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6406) HA: Client Failover

2016-06-14 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6406 
 
 
 
  HA: Client Failover  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Labels:
 
 ha-dep 
 
 
 

Scrum Team/s:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6406) HA: Client Failover

2016-06-14 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6406 
 
 
 
  HA: Client Failover  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Epic 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/14 1:03 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Steve Barlow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-2781) Rust CLI - Config should use over String

2016-06-14 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2781 
 
 
 
  Rust CLI - Config should use  over String  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/14 1:02 PM 
 
 
 

Fix Versions:
 

 PDB CLI 1.1.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Ryan Senior 
 
 
 
 
 
 
 
 
 
 
There are currently many places where we create mutable Strings just so that they conform to our struct. We should instead be using an immutable string slice (i.e. ). This is more efficient and it will remove some cruft. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
   

Jira (PDB-2780) Consider making stockpile durable on OS X

2016-06-14 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2780 
 
 
 
  Consider making stockpile durable on OS X  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 PDB 4.2.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/14 12:55 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Browning 
 
 
 
 
 
 
 
 
 
 
On OS X, fsync() doesn't actually push the data all the way to disk. For that you have to call fcntl(fd, F_FULLSYNC), and the JVM (currently) doesn't. 
So if we want stockpile to provide durability on OS X, we'll need to do that, or perhaps just wait for JDK 9: https://bugs.openjdk.java.net/browse/JDK-8080589 
If we do want to pursue this, it should be possible via JNA. Vague hackish sketch: 
 
 
 
 
 
 
;; project.clj 
 
 
 
 
(def dependencies 
 
 
 
 

Jira (PDOC-77) Create an easy way to modify the rake task to include/exclude certain files/folders.

2016-06-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-77 
 
 
 
  Create an easy way to modify the rake task to include/exclude certain files/folders.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Release Notes Summary:
 
 A new rake The  task  was added that allows configuring the  `  strings  generation :generate` which is provided by including `puppet-strings/rake_tasks` will scan the manifests and lib directory from your single module. If you need to document a complete, or part of a, puppet tree, you can use the `PuppetStrings::RakeTasks::Generate`  task.  The existing  This rake  task  was quite inflexible  will by default overwrite strings:generate unless you specify a custom name . See the  example in the puppet strings readme and the  rake task  itself  for more information. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-2779) stockpile: satisfy ourselves that the durability approach reliable, or adjust it

2016-06-14 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2779 
 
 
 
  stockpile: satisfy ourselves that the durability approach reliable, or adjust it  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Browning 
 
 
 
 
 
 
 
 
 
 The current approach assumes that {code}(stockpile/fsync some-file ...){code} guarantees that all data targeted toward the inode of some-file before the call (ignoring unflushed data in any in-process buffers) will be made durable before the function returns  i.e. be pushed all the way to the underlying storage.To some extent this may depend on whether or not FileChannel force() always bottoms out in an fsync or fdatasync on the relevant file descriptor.References:http://docs.oracle.com/javase/7/docs/api/java/nio/channels/FileChannel.html#force%28boolean%29 http://blog.httrack.com/blog/2013/11/15/everything-you-always-wanted-to-know-about-fsync/ https://en.wikipedia.org/wiki/File_descriptorhttp://linux.die.net/man/2/fsync 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-2779) stockpile: satisfy ourselves that the durability approach reliable, or adjust it

2016-06-14 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2779 
 
 
 
  stockpile: satisfy ourselves that the durability approach reliable, or adjust it  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 PDB 4.2.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/14 12:44 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Browning 
 
 
 
 
 
 
 
 
 
 
The current approach assumes that 
 
 
 
 
 
 
(stockpile/fsync some-file ...) 
 
 
 
 
 
 guarantees that all data targeted toward the inode of some-file before the call (ignoring unflushed data in any in-process buffers) will be made durable before the function returns i.e. be pushed all the way to the underlying storage. 
To some extent this may depend on whether or not FileChannel force() always bottoms out in an fsync or fdatasync on the relevant file descriptor. 
References: 
http://docs.oracle.com/javase/7/docs/api/java/nio/channels/FileChannel.html#force%28boolean%29 

Jira (PDOC-77) Create an easy way to modify the rake task to include/exclude certain files/folders.

2016-06-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-77 
 
 
 
  Create an easy way to modify the rake task to include/exclude certain files/folders.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Acceptance Criteria:
 
 That it is possible to generate a rake task for running strings that is based on user input. 
 
 
 

Story Points:
 
 1 
 
 
 

Release Notes Summary:
 
 A new rake task was added that allows configuring the strings generation task. The existing task was quite inflexible. See the rake task for more information. 
 
 
 

Release Notes:
 
 New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 

Jira (PDOC-77) Create an easy way to modify the rake task to include/exclude certain files/folders.

2016-06-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-77 
 
 
 
  Create an easy way to modify the rake task to include/exclude certain files/folders.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PDOC 0.5.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-2778) stockpile: consider transferTo/transferFrom support

2016-06-14 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2778 
 
 
 
  stockpile: consider transferTo/transferFrom support  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/14 12:20 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Browning 
 
 
 
 
 
 
 
 
 
 
See if using transferTo/transferFrom in the store/stream functions provides any benefit, and if so consider adding it. Though at the moment, this is likely low-priority since (as far as we know), stockpile only client at the moment (PDB) can't benefit from it, because (for one thing) jetty doesn't provide the necessary access. 
http://docs.oracle.com/javase/7/docs/api/java/nio/channels/FileChannel.html#transferTo%28long,%20long,%20java.nio.channels.WritableByteChannel%29 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 


Jira (PDB-2777) Make sure stockpile tests have some coverage of the "no metadata" case

2016-06-14 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning commented on  PDB-2777 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make sure stockpile tests have some coverage of the "no metadata" case  
 
 
 
 
 
 
 
 
 
 
In particular, this bit definitely wasn't being exercised: 
 
 
 
 
 
 
(if (= -1 dash) 
 
 
 
 
  (parse-integer name) ;; FIXME: ensure we test this case
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-2776) Add stockpile tests for custom meta encoder/decoder

2016-06-14 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2776 
 
 
 
  Add stockpile tests for custom meta encoder/decoder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Browning 
 
 
 

Affects Version/s:
 
 PDB 4.2.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (HI-518) make hiera_xxx functions delegate to lookup()

2016-06-14 Thread Brett Swift (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brett Swift commented on  HI-518 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: make hiera_xxx functions delegate to lookup()  
 
 
 
 
 
 
 
 
 
 
Well that is a simple work around.  
Adding functions into pp files is one of those things that never popped into my head.. we never do it, and never thought you could just do that. 
I will give this a go. Thanks Henrik, Mike & Reid!  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-2775) Fix intermittent failures in admin-clean-test

2016-06-14 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2775 
 
 
 
  Fix intermittent failures in admin-clean-test  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Browning 
 
 
 

Affects Version/s:
 
 PDB 4.2.0 
 
 
 

Fix Version/s:
 
 PDB 4.2.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-2777) Make sure stockpile tests have some coverage of the "no metadata" case

2016-06-14 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2777 
 
 
 
  Make sure stockpile tests have some coverage of the "no metadata" case  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 PDB 4.2.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/14 12:12 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Browning 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 

Jira (PUP-5604) Add journalctl command when service fails for systemd

2016-06-14 Thread Ranjit Viswakumar (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ranjit Viswakumar commented on  PUP-5604 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add journalctl command when service fails for systemd  
 
 
 
 
 
 
 
 
 
 
Work around in the meantime. 
 
 
 
 
 
 
service { 'foo': 
 
 
 
 
 ensure => running, 
 
 
 
 
 start  => '/usr/bin/systemctl start foo || (journalctl -xn; exit 1)', 
 
 
 
 
}
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDB-2776) Add stockpile tests for custom meta encoder/decoder

2016-06-14 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2776 
 
 
 
  Add stockpile tests for custom meta encoder/decoder  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/14 12:07 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Browning 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-3827) Errors from indirected routes don't match error schema

2016-06-14 Thread Justin Stoller (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Justin Stoller assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3827 
 
 
 
  Errors from indirected routes don't match error schema  
 
 
 
 
 
 
 
 
 

Change By:
 
 Justin Stoller 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 Justin Stoller qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-2775) Fix intermittent failures in admin-clean-test

2016-06-14 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2775 
 
 
 
  Fix intermittent failures in admin-clean-test  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Rob Browning 
 
 
 

Created:
 

 2016/06/14 11:17 AM 
 
 
 

Fix Versions:
 

 PDB 4.2.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Browning 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups 

Jira (PUP-6349) mailalias doesn't need to quote e-mails with + character

2016-06-14 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6349 
 
 
 
  mailalias doesn't need to quote e-mails with + character  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6349) mailalias doesn't need to quote e-mails with + character

2016-06-14 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6349 
 
 
 
  mailalias doesn't need to quote e-mails with + character  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Story Points:
 
 1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6349) mailalias doesn't need to quote e-mails with + character

2016-06-14 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6349 
 
 
 
  mailalias doesn't need to quote e-mails with + character  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6269) Backport PUP-3341 to 3.x

2016-06-14 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6269 
 
 
 
  Backport PUP-3341 to 3.x  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 

Scope Change Reason:
 
 PR triage merge 
 
 
 

Story Points:
 
 1 
 
 
 

Sprint:
 
 Client 2016-06-15 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6269) Backport PUP-3341 to 3.x

2016-06-14 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6269 
 
 
 
  Backport PUP-3341 to 3.x  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Story Points:
 
 1 0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6349) mailalias doesn't need to quote e-mails with + character

2016-06-14 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6349 
 
 
 
  mailalias doesn't need to quote e-mails with + character  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Story Points:
 
 1 0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6349) mailalias doesn't need to quote e-mails with + character

2016-06-14 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6349 
 
 
 
  mailalias doesn't need to quote e-mails with + character  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Scope Change Reason:
 
 PR Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6349) mailalias doesn't need to quote e-mails with + character

2016-06-14 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6349 
 
 
 
  mailalias doesn't need to quote e-mails with + character  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Sprint:
 
 Client 2016-06-15 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6258) Update Puppet OID lists to add new authorized extensions

2016-06-14 Thread Erik Dasher (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Dasher assigned an issue to Erik Dasher 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6258 
 
 
 
  Update Puppet OID lists to add new authorized extensions  
 
 
 
 
 
 
 
 
 

Change By:
 
 Erik Dasher 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Assignee:
 
 qa Erik Dasher 
 
 
 

Status:
 
 Ready for Test Resolved 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6258) Update Puppet OID lists to add new authorized extensions

2016-06-14 Thread Erik Dasher (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Dasher commented on  PUP-6258 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update Puppet OID lists to add new authorized extensions  
 
 
 
 
 
 
 
 
 
 
Resolving. QA intends to test the modifications in this epic in ticket SERVER-1359. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6258) Update Puppet OID lists to add new authorized extensions

2016-06-14 Thread Nathaniel Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nathaniel Smith assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6258 
 
 
 
  Update Puppet OID lists to add new authorized extensions  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nathaniel Smith 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 Nathaniel Smith qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6150) Don't include IP address in returned error messages

2016-06-14 Thread Ruth Linehan (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ruth Linehan commented on  PUP-6150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Don't include IP address in returned error messages  
 
 
 
 
 
 
 
 
 
 
puppet-agent tests passed in https://jenkins.puppetlabs.com/view/puppet-agent/view/master/view/puppet-agent/job/platform_puppet-agent_intn-van-sys_suite-daily-puppet-master/144/ (puppet-agent 425401267 includes puppet 14f9a6e, which is the merge-commit for this PR). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6405) Pip package provider runs every time when updating setuptools

2016-06-14 Thread William Yardley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Yardley commented on  PUP-6405 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pip package provider runs every time when updating setuptools  
 
 
 
 
 
 
 
 
 
 
And obviously, the package installing itself over and over on each run isn't necessarily a huge problem. However, it does show up as a change in puppet dashboard, which is why we're looking at changing the behavior. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6405) Pip package provider runs every time when updating setuptools

2016-06-14 Thread William Yardley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Yardley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6405 
 
 
 
  Pip package provider runs every time when updating setuptools  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Yardley 
 
 
 
 
 
 
 
 
 
 Similar to PUP-6120, I see a problem with 'setuptools' (which also doesn't show up in pip output). The current workaround seems kind of cumbersome. While this is with 3.8.7, I imagine the setuptools problem might be reproducible in newer puppet.How common is pip < 1.2.2? Seems like "pip freeze --all" would also work, but appears to also not be implemented in 1.0.x.Maybe pip could just update itself first (or require a minimum version), then use 'pip list' or 'pip freeze --all' for determining versions of everything else?  Or determine pip version first, then add the '--all' flag in cases where it's supported? Then at least it would "see" pip and setuptools if the version of pip is recent enough. This is with older Puppet (3.8) without the fix for 6120, but same {noformat}Debug: Executing '/bin/pip freeze'Debug: Executing '/bin/pip install -q --upgrade setuptools'Notice: /Stage[main]/Role::Dp/Package[setuptools]/ensure: created{noformat}{noformat}  package { 'pip':  ensure   => latest,  install_options => '--upgrade',  provider => 'pip' } ->  package { 'setuptools':  ensure   => latest,  install_options => '--upgrade',  provider => 'pip' } ->{noformat}{noformat}# pip --versionpip 8.1.2 from /usr/lib/python2.7/site-packages (python 2.7)# pip freeze | grep ^setuptools# pip freeze --all | grep ^setuptoolssetuptools==23.0.0# pip list | grep ^setuptoolssetuptools (23.0.0){noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
  

Jira (PUP-6405) Pip package provider runs every time when updating setuptools

2016-06-14 Thread William Yardley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Yardley commented on  PUP-6405 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pip package provider runs every time when updating setuptools  
 
 
 
 
 
 
 
 
 
 
Sorry if the weird clone (without clone+ or clone++) messed up anything in terms of organization. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6405) Pip package provider runs every time when updating setuptools

2016-06-14 Thread William Yardley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Yardley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6405 
 
 
 
  Pip package provider runs every time when updating setuptools  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Yardley 
 
 
 
 
 
 
 
 
 
 Similar to PUP-6120, I see a problem with 'setuptools' (which also doesn't show up in pip output). The current workaround seems kind of cumbersome.  While this is with 3.8.7, I imagine the setuptools problem might be reproducible in newer puppet. How common is pip < 1.2.2? Seems like "pip freeze --all" would also work, but appears to also not be implemented in 1.0.x.Maybe pip could just update itself first (or require a minimum version), then use 'pip list' or 'pip freeze --all' for determining versions of everything else?This is with older Puppet (3.8) without the fix for 6120, but same {noformat}Debug: Executing '/bin/pip freeze'Debug: Executing '/bin/pip install -q --upgrade setuptools'Notice: /Stage[main]/Role::Dp/Package[setuptools]/ensure: created{noformat}{noformat}  package { 'pip':  ensure   => latest,  install_options => '--upgrade',  provider => 'pip' } ->  package { 'setuptools':  ensure   => latest,  install_options => '--upgrade',  provider => 'pip' } ->{noformat}{noformat}# pip --versionpip 8.1.2 from /usr/lib/python2.7/site-packages (python 2.7)# pip freeze | grep ^setuptools# pip freeze --all | grep ^setuptoolssetuptools==23.0.0# pip list | grep ^setuptoolssetuptools (23.0.0){noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the 

Jira (PUP-6405) Pip package provider runs every time when updating setuptools

2016-06-14 Thread William Yardley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Yardley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6405 
 
 
 
  Pip package provider runs every time when updating setuptools  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Yardley 
 
 
 

Affects Version/s:
 
 PUP 4.4.1 
 
 
 

Affects Version/s:
 
 PUP 3.8.7 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6405) Pip package provider runs every time when updating setuptools

2016-06-14 Thread William Yardley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Yardley assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6405 
 
 
 
  Pip package provider runs every time when updating setuptools  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Yardley 
 
 
 

Assignee:
 
 Jon Skarpeteig 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6405) Pip package provider runs every time when updating setuptools

2016-06-14 Thread William Yardley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Yardley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6405 
 
 
 
  Pip package provider runs every time when updating setuptools  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Yardley 
 
 
 
 
 
 
 
 
 
 Similar to PUP-6120, I see a problem with 'setuptools' (which also doesn't show up in pip output). The current workaround seems kind of cumbersome.How common is pip < 1.2.2? Seems like "pip freeze --all" would also work, but appears to also not be implemented in 1.0.x.Maybe pip could just update itself first  (or require a minimum version) , then use 'pip list' or 'pip freeze --all' for determining versions of everything else?This is with older Puppet (3.8) without the fix for 6120, but same {noformat}Debug: Executing '/bin/pip freeze'Debug: Executing '/bin/pip install -q --upgrade setuptools'Notice: /Stage[main]/Role::Dp/Package[setuptools]/ensure: created{noformat}{noformat}  package { 'pip':  ensure   => latest,  install_options => '--upgrade',  provider => 'pip' } ->  package { 'setuptools':  ensure   => latest,  install_options => '--upgrade',  provider => 'pip' } ->{noformat}{noformat}# pip --versionpip 8.1.2 from /usr/lib/python2.7/site-packages (python 2.7)# pip freeze | grep ^setuptools# pip freeze --all | grep ^setuptoolssetuptools==23.0.0# pip list | grep ^setuptoolssetuptools (23.0.0){noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 

Jira (PUP-6405) Pip package provider runs every time when updating setuptools

2016-06-14 Thread William Yardley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Yardley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6405 
 
 
 
  Pip package provider runs every time when updating setuptools  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Yardley 
 
 
 
 
 
 
 
 
 
 Similar to PUP-6120, I see a problem with 'setuptools' (which also doesn't show up in pip output). The current workaround seems kind of cumbersome.How common is pip < 1.2.2? Seems like "pip freeze --all" would also work, but appears to also not be implemented in 1.0.x.Maybe pip could just update itself first, then use 'pip list' or 'pip freeze --all' for determining versions of everything else?This is with older Puppet (3.8) without the fix for 6120, but same {noformat}Debug: Executing '/bin/pip freeze'Debug: Executing '/bin/pip install -q --upgrade setuptools'Notice: /Stage[main]/Role::Dp/Package[setuptools]/ensure: created{noformat}{noformat}  package { 'pip':  ensure   => latest,  install_options => '--upgrade',  provider => 'pip' } ->  package { 'setuptools':  ensure   => latest,  install_options => '--upgrade',  provider => 'pip' } ->{noformat}{noformat} adv1 [prod] root@dp-i-0c25bb8252bd5b882:~  # pip --versionpip 8.1.2 from /usr/lib/python2.7/site-packages (python 2.7) adv1 [prod] root@dp-i-0c25bb8252bd5b882:~  # pip freeze | grep ^setuptools adv1 [prod] root@dp-i-0c25bb8252bd5b882:~  # pip freeze --all | grep ^setuptoolssetuptools==23.0.0 adv1 [prod] root@dp-i-0c25bb8252bd5b882:~  # pip list | grep ^setuptoolssetuptools (23.0.0){noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received 

Jira (PUP-6405) Pip package provider runs every time when updating setuptools

2016-06-14 Thread William Yardley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Yardley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6405 
 
 
 
  Pip package provider runs every time when updating setuptools  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Yardley 
 
 
 
 
 
 
 
 
 
 Similar to PUP-6120, I see a problem with 'setuptools' (which also doesn't show up in pip output). The  current workaround seems kind of cumbersome.How common is  pip  package provider currently polls PyPI directly  < 1.2.2? Seems like "pip freeze --all" would also work ,  instead  but appears to also not be implemented in 1.0.x.Maybe pip could just update itself first, then use 'pip list' or 'pip freeze --all' for determining versions  of  relying on  everything else?This is with older Puppet (3.8) without the fix for 6120, but same {noformat}Debug: Executing '/bin/  pip  from CLI to look up  freeze'Debug: Executing '/bin/pip install -q --upgrade setuptools'Notice: /Stage[main]/Role::Dp/Package[setuptools]/ensure: created{noformat}{noformat}  package { 'pip':  ensure   =>  latest ,  install_options => '--upgrade',  provider => 'pip' } ->  package { 'setuptools':  ensure   => latest,  install_options => '--upgrade',  provider => 'pip' } ->{noformat}{noformat}adv1 [prod] root@dp-i-0c25bb8252bd5b882:~ # pip --  version pip 8 . 1.2 from /usr/lib/python2.7/site-packages (python 2.7)  adv1 [prod] root@dp-i-0c25bb8252bd5b882:~ # pip freeze | grep ^setuptools  This makes it impossible to configure adv1 [prod] root@dp-i-0c25bb8252bd5b882:~ #  pip  to use a custom PyPI repository  freeze --all | grep ^setuptoolssetuptools==23.0.0adv1 [prod] root@dp-i-0c25bb8252bd5b882:~ # pip list | grep ^setuptoolssetuptools (23.0.0){noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 

Jira (PUP-6405) Pip package provider runs every time when updating setuptools

2016-06-14 Thread William Yardley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Yardley created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6405 
 
 
 
  Pip package provider runs every time when updating setuptools  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.4.1 
 
 
 

Assignee:
 
 Jon Skarpeteig 
 
 
 

Components:
 

 Types and Providers 
 
 
 

Created:
 

 2016/06/14 10:24 AM 
 
 
 

Fix Versions:
 

 PUP 4.5.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 William Yardley 
 
 
 
 
 
 
 
 
 
 
The pip package provider currently polls PyPI directly, instead of relying on pip from CLI to look up latest version. 
This makes it impossible to configure pip to use a custom PyPI repository 
 
 
 
 
 
 
 
 
 
 
 
 


Jira (HI-518) make hiera_xxx functions delegate to lookup()

2016-06-14 Thread Mike Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mike Smith commented on  HI-518 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: make hiera_xxx functions delegate to lookup()  
 
 
 
 
 
 
 
 
 
 
Brett Swift 
I was working with Reid, and we tested these function overrides (Thanks Henrik Lindberg). You can place this in your site.pp (not a module) and it will override the hiera_XXX() functions to use lookup().  function hiera($key,$def = undef, $level = undef) { 
 
 
 
 
 
 
function hiera($key,$def = undef, $level = undef) { 
 
 
 
 
  if $level != undef { fail('Lookup does not support hiera level override') } 
 
 
 
 
  lookup ($key,{'default_value' =>  $def}) 
 
 
 
 
} 
 
 
 
 
  
 
 
 
 
function hiera_array($key,$def = undef, $level = undef) { 
 
 
 
 
  if $level != undef { fail('Lookup does not support hiera level override') } 
 
 
 
 
  lookup ($key,{'default_value' => $def, 'merge' => 'unique'}) 
 
 
 
 
} 
 
 
 
 

Jira (PUP-6401) deprecated symbol monkey patch code path is always executed when running puppet under jruby

2016-06-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6401 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: deprecated symbol monkey patch code path is always executed when running puppet under jruby  
 
 
 
 
 
 
 
 
 
 
Rip the band aid and remove the monkeypatch for the betterment of mankind? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6403) puppetlabs-stdlib(file_line) is not compatible with puppet agent 3.8.7

2016-06-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6403 
 
 
 
  puppetlabs-stdlib(file_line) is not compatible with puppet agent 3.8.7  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Scrum Team:
 
 Modules 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6404) Puppetlabs mysql module, max_allowed_packet parameter

2016-06-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6404 
 
 
 
  Puppetlabs mysql module, max_allowed_packet parameter  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Scrum Team:
 
 Modules 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6257) Add --allow-authorization-extensions to puppet cert sign

2016-06-14 Thread Nathaniel Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nathaniel Smith commented on  PUP-6257 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add --allow-authorization-extensions to puppet cert sign  
 
 
 
 
 
 
 
 
 
 
yeah, i think that is covered elsewhere now. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6257) Add --allow-authorization-extensions to puppet cert sign

2016-06-14 Thread Nathaniel Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nathaniel Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6257 
 
 
 
  Add --allow-authorization-extensions to puppet cert sign  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nathaniel Smith 
 
 
 
 
 
 
 
 
 
 In Scope* Support a new flag in the "puppet cert sign" tool, "--allow-authorization-extensions"* Determine if a cert given to "puppet cert sign" has any extensions under the puppet.1.3 OID arc* Fail the signing unless the --allow-authorization-extensions flag is present* Audit the cert-related tools in puppet to see if any need to be updated with respect to this work; ca, certificate, certificate-request, certificate-revocation-list. Hopefully they don't need to be updated.* Update the internal signing policy in the ruby CA code to allow the new puppet.3 arc (in certificate_authority.rb:323 in puppet) * Update clojure CA code to respect new arc   Out of Scope* Worrying about any extensions other than those under puppet.1.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6257) Add --allow-authorization-extensions to puppet cert sign

2016-06-14 Thread Kevin Corcoran (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kevin Corcoran commented on  PUP-6257 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add --allow-authorization-extensions to puppet cert sign  
 
 
 
 
 
 
 
 
 
 
Nathaniel Smith - From the description: 

Update clojure CA code to respect new arc
 
I'm not sure exactly what "respect" means in that context. Is that not covered by other tickets? Maybe just cruft that need to be deleted at this point? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (HI-518) make hiera_xxx functions delegate to lookup()

2016-06-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-518 
 
 
 
  make hiera_xxx functions delegate to lookup()  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Story Points:
 
 1 
 
 
 

Scrum Team:
 
 Language 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (HI-518) make lookup() function work with classic hiera

2016-06-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  HI-518 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: make lookup() function work with classic hiera  
 
 
 
 
 
 
 
 
 
 
it is really simple to work around by defining puppet functions with the same name and signature as the hiera_xxx functions by placing them in the site.pp. These function can then delegate to the lookup() function. 
While this works it is not ideal, and does not help migrating off the hiera_xxx functions. To do that, we need to change the implementation of the functions to always go via lookup rather than directly calling classic hiera. If we do this there are a couple of decision to make: 
 

Is it ok to turn this on by default in puppet 4.6, or do we need an opt-in (setting).
 

Can we deprecate the hiera_xxx if using --strict ?
 
 
Ping Eric Sorenson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (HI-518) make hiera_xxx functions delegate to lookup()

2016-06-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-518 
 
 
 
  make hiera_xxx functions delegate to lookup()  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Summary:
 
 make  hiera_xxx functions delegate to  lookup()  function work with classic hiera 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (HI-518) make lookup() function work with classic hiera

2016-06-14 Thread Brett Swift (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brett Swift created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-518 
 
 
 
  make lookup() function work with classic hiera  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/14 7:23 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Brett Swift 
 
 
 
 
 
 
 
 
 
 
Using the hiera per environment feature, is a bit difficult right now. With 80+ forge modules, most of them use hiera_xx functions, which don't work with the new hiera version - as you are required to use the lookup() function. 
Adoption of this new experimental feature is limited because there isn't backwards compatibility with the ubiquitous hiera() hiera_array() and hiera_hash() functions. 
It would be beneficial for us to use the new hiera per environment, and new hiera 4 configuration. Reid Vandewiele / Reid Vandewiele has been experimenting with this.  This ticket created at the request of Henrik Lindberg.  
Thanks! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


Jira (PUP-6404) Puppetlabs mysql module, max_allowed_packet parameter

2016-06-14 Thread Christian Fasnacht (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Fasnacht updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6404 
 
 
 
  Puppetlabs mysql module, max_allowed_packet parameter  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Fasnacht 
 
 
 
 
 
 
 
 
 
 We at Swisscom implemented a max_allowed_packet parameter for the puppetlab mysql module backup dump script. I will make a merge request from our modifications. The default value is 1M as it is default for mysql. Pull request:https://github.com/puppetlabs/puppetlabs-mysql/pull/856 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6404) Puppetlabs mysql module, max_allowed_packet parameter

2016-06-14 Thread Christian Fasnacht (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Fasnacht updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6404 
 
 
 
  Puppetlabs mysql module, max_allowed_packet parameter  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Fasnacht 
 
 
 

Summary:
 
 We at Swisscom implemented a max_allowed_packet parameter for the puppetlab Puppetlabs  mysql module . , max_allowed_packet parameter 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6404) We at Swisscom implemented a max_allowed_packet parameter for the puppetlab mysql module.

2016-06-14 Thread Christian Fasnacht (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Fasnacht created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6404 
 
 
 
  We at Swisscom implemented a max_allowed_packet parameter for the puppetlab mysql module.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/14 4:52 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Christian Fasnacht 
 
 
 
 
 
 
 
 
 
 
We at Swisscom implemented a max_allowed_packet parameter for the puppetlab mysql module backup dump script. I will make a merge request from our modifications. The default value is 1M as it is default for mysql. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
 

Jira (PUP-3827) Errors from indirected routes don't match error schema

2016-06-14 Thread Kevin Corcoran (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kevin Corcoran assigned an issue to Justin Stoller 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3827 
 
 
 
  Errors from indirected routes don't match error schema  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kevin Corcoran 
 
 
 

Assignee:
 
 Justin Stoller 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6387) Puppet agent hung waiting on read from puppetmaster

2016-06-14 Thread Christopher Tapp (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Tapp commented on  PUP-6387 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet agent hung waiting on read from puppetmaster  
 
 
 
 
 
 
 
 
 
 
I created a new puppetmaster nearer to the managed nodes and I haven't seen the problem since. Must have been something on the network as you suggest. Thanks. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6403) puppetlabs-stdlib(file_line) is not compatible with puppet agent 3.8.7

2016-06-14 Thread Stefan Sobea (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Sobea created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6403 
 
 
 
  puppetlabs-stdlib(file_line) is not compatible with puppet agent 3.8.7  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.8.7 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 

Components:
 

 Community 
 
 
 

Created:
 

 2016/06/14 1:06 AM 
 
 
 

Environment:
 
 
puppet client is installed in windows server 2012. puppet server is on centos  
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Stefan Sobea 
 
 
 
 
 
 
 
 
 
 
Hello guys, I tried to use file_line with puppet agent 3.8.7, but is not working. In resources.txt you will not see any step done related file_line, but in client_data->catalog-> 'yourname.json' this instruction is visible . After I reverted my puppet agent to 3.8.6 all steps are good . For both I used puppet sever version 3.8.7. puppetlabs-stdlib version = 4.12.0 
Kind regards, Stefan