Jira (PUP-6909) useradd.rb report error

2016-11-09 Thread stonelai (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 stonelai created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6909 
 
 
 
  useradd.rb report error  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.8.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Modules 
 
 
 

Created:
 

 2016/11/09 8:34 PM 
 
 
 

Environment:
 
 
SUSE Linux Enterprise Server 12 SP1 (x86_64) ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-linux-gnu] 
some of the hosts have this problem, some of the same host not. 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 stonelai 
 
 
 
 
 
 
 
 
 
 
Error: /Stage[main]/xxx::Userlistt/Resources[user]: Failed to generate additional resources using 'generate': expected numeric [250/1815] /usr/lib64/ruby/vendor_ruby/2.1.0/puppet/provider/user/useradd.rb:40:in `+' /usr/lib64/ruby/vendor_ruby/2.1.0/puppet/provider/user/useradd.rb:40:in `block (2 levels) in ' /usr/lib64/ruby/vendor_ruby/2.1.0/puppet/provider/nameservice.rb:218:in `call' /usr/lib64/ruby/vendor_ruby/2.1.0/puppet/provider/nameservice.rb:218:in `unmunge' /usr/lib64/ruby/vendor_ruby/2.1.0/puppet/provider/user/useradd.rb:208:in `block (3 levels) 

Jira (PDOC-132) Blog post: documenting new (or old) modules with puppet-strings

2016-11-09 Thread Lindsey Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lindsey Smith commented on  PDOC-132 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Blog post: documenting new (or old) modules with puppet-strings  
 
 
 
 
 
 
 
 
 
 
LGTM and I made some suggestions in the doc. Also, I created https://github.com/puppetlabs/puppet-strings/pull/124 to include modern PE instructions in installation instructions. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-132) Blog post: documenting new (or old) modules with puppet-strings

2016-11-09 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-132 
 
 
 
  Blog post: documenting new (or old) modules with puppet-strings  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 
 
 
 
 
 
 
 Post should contain stuff along the lines I think this post is sort  of :- Converting an existing module  meant  to  be a demo of what  strings - Add strings docs  can do for anyone who isn't familiar. I plan  to  basically go over how to document some of the major components of  a module with  no docs- Includes using strings as a docs coverage toolAnd of course, lots of  examples. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-132) Blog post: documenting new (or old) modules with puppet-strings

2016-11-09 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  PDOC-132 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Blog post: documenting new (or old) modules with puppet-strings  
 
 
 
 
 
 
 
 
 
 
I've got a rough draft mostly fleshed out here: https://docs.google.com/a/puppet.com/document/d/14CZGJJ_lbrHTZXyTGy9VTawSC9mN_NoZ61u7FScOF5A/edit?usp=sharing 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6908) selmodule syncversion => false behavior incorrect

2016-11-09 Thread AJ Zmudosky (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 AJ Zmudosky created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6908 
 
 
 
  selmodule syncversion => false behavior incorrect  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Types and Providers 
 
 
 

Created:
 

 2016/11/09 3:31 PM 
 
 
 

Environment:
 
 
Puppet Open Source 3.8.5 (Issue applies to 3.8.5 and latest version of Puppet) 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 AJ Zmudosky 
 
 
 
 
 
 
 
 
 
 
The documentation for the 'selmodule' type states that the default value of 'syncversion' is 'false'. However it is actually 'undef' (the type does not set 'defaultto' for this parameter). 
If 'syncversion' is explicitly set to false, Puppet runs on RHEL <=7.2 fail because the semodule provider still calls the syncversion method which raises an exception when '/usr/sbin/semodule --upgrade ...' fails because the module is the same version on disk and loaded. 
However, in RHEL7.3, Red Hat updated SELinux's policycoreutils which changed the behavior of the semodule utility that Puppet's selmodule provider depends on. The utility no longer reports the version of loaded SELinux modules. This has been reported in = 23" class="issue-link" data-issue-key="PUP-5649" style="color: #3b73af; text-decoration: none">PUP-5649. 
The effect is that every Puppet run on RHEL7.3 reports a 

Jira (PUP-6907) Don't provide $name (and perhaps others) in EPP scope

2016-11-09 Thread Alex Jurkiewicz (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Jurkiewicz updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6907 
 
 
 
  Don't provide $name (and perhaps others) in EPP scope  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Jurkiewicz 
 
 
 

Summary:
 
 Don't provide $name (and perhaps others)  into  in  EPP scope 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6907) Don't provide $name (and perhaps others) into EPP scope

2016-11-09 Thread Alex Jurkiewicz (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Jurkiewicz created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6907 
 
 
 
  Don't provide $name (and perhaps others) into EPP scope  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Language 
 
 
 

Created:
 

 2016/11/09 3:24 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Alex Jurkiewicz 
 
 
 
 
 
 
 
 
 
 
I was just bitten by some unexpected behaviour. In EPP, $name refers to the node scope name, and resolves to (in our case) __node_regexp__. 
This was surprising. I was expecting to get the name of the defined type that this EPP template was defined in. 
This behaviour is documented on https://docs.puppet.com/puppet/latest/reference/lang_template_epp.html 
 
A template works like a defined type: 
 

It has its own anonymous local scope.
 

The parent scope is set to node scope (or top scope if there’s no node definition).
 
 
 
I think this behaviour will bite more users than it will be expected, and so suggest that the scope for EPP templates should omit $name (and possibly other variables ($title?)). 

Jira (PUP-6876) Puppet::Settings::IniFile doesn't handle Unicode keys / sections properly - can cause `config set` / `config print` failures

2016-11-09 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6876 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet::Settings::IniFile doesn't handle Unicode keys / sections properly - can cause `config set` / `config print` failures  
 
 
 
 
 
 
 
 
 
 
Passed CI in master at; https://jenkins.puppetlabs.com/view/puppet-agent/view/master/view/puppet/job/platform_puppet_pkg-van-promote_master/368/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-3177) Dead links in the PuppetDB Documentation pages

2016-11-09 Thread Isaac Eldridge (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Isaac Eldridge moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3177 
 
 
 
  Dead links in the PuppetDB Documentation pages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Isaac Eldridge 
 
 
 

Workflow:
 
 Documentation Scrum Teams  Workflow 
 
 
 

Key:
 
 DOC PDB - 2992 3177 
 
 
 

Project:
 
 Documentation [Internal] PuppetDB 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-3042) If a catalog has a dependency cycle, it does not count as failed

2016-11-09 Thread Scott Walker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Scott Walker commented on  PUP-3042 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: If a catalog has a dependency cycle, it does not count as failed  
 
 
 
 
 
 
 
 
 
 
Not in Overview across the fleet. I think we already do this when you open a single node's graph - we show the warnings. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6777) regression: incompatible character encodings: UTF-8 and ASCII-8BIT

2016-11-09 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6777 
 
 
 
  regression: incompatible character encodings: UTF-8 and ASCII-8BIT  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Story Points:
 
 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6777) regression: incompatible character encodings: UTF-8 and ASCII-8BIT

2016-11-09 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6777 
 
 
 
  regression: incompatible character encodings: UTF-8 and ASCII-8BIT  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP  Grooming  2016-12-14 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6777) regression: incompatible character encodings: UTF-8 and ASCII-8BIT

2016-11-09 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6777 
 
 
 
  regression: incompatible character encodings: UTF-8 and ASCII-8BIT  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Acceptance Criteria:
 
 - Tests- Fix passes CI all platforms   
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6875) [Spike] Investigate usage of ReGex \w character class in Puppet

2016-11-09 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6875 
 
 
 
  [Spike] Investigate usage of ReGex \w character class in Puppet  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Story Points:
 
 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6875) [Spike] Investigate usage of ReGex \w character class in Puppet

2016-11-09 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6875 
 
 
 
  [Spike] Investigate usage of ReGex \w character class in Puppet  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP 2016- 11 12 - 30 28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6875) [Spike] Investigate usage of ReGex \w character class in Puppet

2016-11-09 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6875 
 
 
 
  [Spike] Investigate usage of ReGex \w character class in Puppet  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP  Grooming  2016-11-30 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6875) [Spike] Investigate usage of ReGex \w character class in Puppet

2016-11-09 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6875 
 
 
 
  [Spike] Investigate usage of ReGex \w character class in Puppet  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 
 
 
 
 
 
 
 The {{\w}} character class in Ruby does not support Unicode and will only match on {{[a-zA-z0-9_]}} which is limiting.Instead, we should generally be using {{[[:word:]]}} where Unicode is important within a regex.  This ticket involves auditing the existing code to identify critically important areas where this may be a problem in types / providers, gems, etc.  Note that the Unicode compliant word character class will be slower than the ASCII version, so it would be good to keep an eye on performance as changes are proposed / madeThis could also extend to supported modules, but should probably be a new ticket. h5. In scope for Agent + Platform Team- Identify areas of concern, file tickets, assess impact and priority.- Analysis of gems should limit scope (using {{--without development}} flag to bundler). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6865) puppet 4.8.0 breaks code that uses strftime()

2016-11-09 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown commented on  PUP-6865 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet 4.8.0 breaks code that uses strftime()  
 
 
 
 
 
 
 
 
 
 
FWIW, I don't think that the agent should have any awareness of the master or influence it's behavior in any way - so I would generally be opposed to puppet-agent packages performing a HUP against the server. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6885) Remove warning about server_list and server conflicting

2016-11-09 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6885 
 
 
 
  Remove warning about server_list and server conflicting  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Fix Version/s:
 
 PUP 4.8.1 
 
 
 

Fix Version/s:
 
 PUP 4.9.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6865) puppet 4.8.0 breaks code that uses strftime()

2016-11-09 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens commented on  PUP-6865 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet 4.8.0 breaks code that uses strftime()  
 
 
 
 
 
 
 
 
 
 
I've opened https://tickets.puppetlabs.com/browse/PA-681 and linked it to this ticket. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6865) puppet 4.8.0 breaks code that uses strftime()

2016-11-09 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens commented on  PUP-6865 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet 4.8.0 breaks code that uses strftime()  
 
 
 
 
 
 
 
 
 
 
Thomas Hallgren I think it probably makes more sense to add something to the puppet-agent packaging to HUP the server if it is present/running on package upgrades. I'll open a ticket in PA and link it to this one. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6865) puppet 4.8.0 breaks code that uses strftime()

2016-11-09 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6865 
 
 
 
  puppet 4.8.0 breaks code that uses strftime()  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenn Hussey 
 
 
 

Fix Version/s:
 
 PUP 4.8.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-3042) If a catalog has a dependency cycle, it does not count as failed

2016-11-09 Thread Verne Lindner (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Verne Lindner commented on  PUP-3042 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: If a catalog has a dependency cycle, it does not count as failed  
 
 
 
 
 
 
 
 
 
 
Scott Walker Would we not be able to identify it to report on it? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6865) puppet 4.8.0 breaks code that uses strftime()

2016-11-09 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6865 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet 4.8.0 breaks code that uses strftime()  
 
 
 
 
 
 
 
 
 
 
Closing this as won't fix. If a ticket is needed for Puppet Server to do better when the world has changed please create one. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-5704) The "posix" provider of the "exec" resource seems to invoke a shell even though the documentation says it doesn't

2016-11-09 Thread Alexander Kurtz (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexander Kurtz updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5704 
 
 
 
  The "posix" provider of the "exec" resource seems to invoke a shell even though the documentation says it doesn't  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alexander Kurtz 
 
 
 

Affects Version/s:
 
 PUP 4.8.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-5704) The "posix" provider of the "exec" resource seems to invoke a shell even though the documentation says it doesn't

2016-11-09 Thread Alexander Kurtz (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexander Kurtz commented on  PUP-5704 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The "posix" provider of the "exec" resource seems to invoke a shell even though the documentation says it doesn't  
 
 
 
 
 
 
 
 
 
 
Still happens with Puppet 4.8.0: 
{{ root@shepard:~# puppet --version 4.8.0 root@shepard:~# cat manifest.pp  $input = 'foo; if false; then exit 23; else exit 42; fi' 
exec { "/bin/echo $ {input} 
": provider => 'posix', } root@shepard:~# puppet apply manifest.pp  Notice: Compiled catalog for shepard.informatik.tu-muenchen.de in environment production in 0.17 seconds Notice: /Stage[main]/Main/Exec[/bin/echo foo; if false; then exit 23; else exit 42; fi]/returns: foo Error: /bin/echo foo; if false; then exit 23; else exit 42; fi returned 42 instead of one of [0] Error: /Stage[main]/Main/Exec[/bin/echo foo; if false; then exit 23; else exit 42; fi]/returns: change from notrun to 0 failed: /bin/echo foo; if false; then exit 23; else exit 42; fi returned 42 instead of one of [0] Notice: Applied catalog in 0.05 seconds root@shepard:~#  }} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-3042) If a catalog has a dependency cycle, it does not count as failed

2016-11-09 Thread Scott Walker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Scott Walker commented on  PUP-3042 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: If a catalog has a dependency cycle, it does not count as failed  
 
 
 
 
 
 
 
 
 
 
Verne Lindner I don't think SR team can address this - it's really change to Puppet agent. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6906) ensure => absent and recurse => true results in error

2016-11-09 Thread Loop (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Loop created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6906 
 
 
 
  ensure => absent and recurse => true results in error  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.2.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/11/09 5:18 AM 
 
 
 

Environment:
 
 
Fedora Linux 24 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Loop 
 
 
 
 
 
 
 
 
 
 
To reproduce: 
 
 
 
 
 
 
$ mkdir /tmp/a 
 
 
 
 
$ touch /tmp/a/b 
 
 
 
 
$ cat > test.pp << 'EOF' 
 

Jira (PUP-6780) modify the lookup helper implementation to support v5 features

2016-11-09 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6780 
 
 
 
  modify the lookup helper implementation to support v5 features  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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