Jira (PUP-1020) PR (2153): (#18342) WIP - Iristyle

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2153): (#18342) WIP - Iristyle 










Iristyle commented:
Original commit 61c91cf ditched in favor of an updated version.. as the original, while seemingly correct, broke a number of tests on Windows












   

 Add Comment











 













 Puppet /  PUP-1020



  PR (2153): (#18342) WIP - Iristyle 







 h2. (#18342) WIP   * Author: Ethan J. Brown <>  * Company:   * Github ID: [Iristyle|https://github.com/Iristyle]  * [Pull Request 2153 Discussion|https://github.com/puppetlabs/puppet/pull/2153]  * [Pull Request 2153 File Diff|https://github.com/puppetlabs/puppet/pull/2153/files]  h2. Pull Request Description  (webhooks-id: 4b89fe99d8f9a009b680...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1020) PR (2153): (#18342) WIP - Iristyle

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2153): (#18342) WIP - Iristyle 










Iristyle commented:
Built on #2173 that must be merged in first..












   

 Add Comment











 













 Puppet /  PUP-1020



  PR (2153): (#18342) WIP - Iristyle 







 h2. (#18342) WIP   * Author: Ethan J. Brown <>  * Company:   * Github ID: [Iristyle|https://github.com/Iristyle]  * [Pull Request 2153 Discussion|https://github.com/puppetlabs/puppet/pull/2153]  * [Pull Request 2153 File Diff|https://github.com/puppetlabs/puppet/pull/2153/files]  h2. Pull Request Description  (webhooks-id: 4b89fe99d8f9a009b680...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-984) Review the acceptance failures with --parser=future.

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Review the acceptance failures with --parser=future. 










And down to 2, and we think we know what the cause is. And there are pull requests for those to try.












   

 Add Comment











 













 Puppet /  PUP-984



  Review the acceptance failures with --parser=future. 







 And fix up if straight forward.















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-941) PR (209): Fix prefix exception message (Closes #23364) - francocatena

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: PR (209): Fix prefix exception message (Closes #23364) - francocatena 










Adrien Thebo Nope, completely missed that. What version should it have? Should this be moved to a different project besides PUP?












   

 Add Comment











 













 Puppet /  PUP-941



  PR (209): Fix prefix exception message (Closes #23364) - francocatena 







 h2. Fix prefix exception message (Closes #23364)   * Author: Franco Catena <>  * Company: Cirope S.A.  * Github ID: [francocatena|https://github.com/francocatena]  * [Pull Request 209 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/209]  * [Pull Request 209 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/209/files]  h2. Pull...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-941) PR (209): Fix prefix exception message (Closes #23364) - francocatena

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-941



  PR (209): Fix prefix exception message (Closes #23364) - francocatena 










Change By:

 Joshua Cooper




Fix Version/s:

 3.5.0












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1194) PR (2177): Add guide to running local acceptance tests. - aperiodic

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2177): Add guide to running local acceptance tests. - aperiodic 










aperiodic commented:
@zaphod42 I've consolidated the vagrant guide into the acceptance README.












   

 Add Comment











 













 Puppet /  PUP-1194



  PR (2177): Add guide to running local acceptance tests. - aperiodic 







 h2. Add guide to running local acceptance tests.   * Author: Dan Lidral-Porter <>  * Company:   * Github ID: [aperiodic|https://github.com/aperiodic]  * [Pull Request 2177 Discussion|https://github.com/puppetlabs/puppet/pull/2177]  * [Pull Request 2177 File Diff|https://github.com/puppetlabs/puppet/pull/2177/files]  h2. Pull Request Description   Poin...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1215) PR (2180): (maint) Check package build status earlier in bootstrap - kylog

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2180): (maint) Check package build status earlier in bootstrap - kylog 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 Puppet /  PUP-1215



  PR (2180): (maint) Check package build status earlier in bootstrap - kylog 







 h2. (maint) Check package build status earlier in bootstrap   * Author: Kylo Ginsberg <>  * Company:   * Github ID: [kylog|https://github.com/kylog]  * [Pull Request 2180 Discussion|https://github.com/puppetlabs/puppet/pull/2180]  * [Pull Request 2180 File Diff|https://github.com/puppetlabs/puppet/pull/2180/files]  h2. Pull Request Description   I thi...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-850) Puppet 3.6 Deprecations in Preparation for Puppet 4

[Eric Sorenson (JIRA)]

Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-850



  Puppet 3.6 Deprecations in Preparation for Puppet 4 










Change By:

 Eric Sorenson




Epic Name:

 Deprecation 3. 5 6 .0 












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-850) Puppet 3.6 Deprecations in Preparation for Puppet 4

[Eric Sorenson (JIRA)]

Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-850



  Puppet 3.6 Deprecations in Preparation for Puppet 4 










Change By:

 Eric Sorenson




Summary:

 Puppet 3. 5 6  Deprecations in Preparation for Puppet 4












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-941) PR (209): Fix prefix exception message (Closes #23364) - francocatena

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: PR (209): Fix prefix exception message (Closes #23364) - francocatena 










Joshua Cooper this is a stdlib pull request, should it have a fix version of 3.5.0?












   

 Add Comment











 













 Puppet /  PUP-941



  PR (209): Fix prefix exception message (Closes #23364) - francocatena 







 h2. Fix prefix exception message (Closes #23364)   * Author: Franco Catena <>  * Company: Cirope S.A.  * Github ID: [francocatena|https://github.com/francocatena]  * [Pull Request 209 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/209]  * [Pull Request 209 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/209/files]  h2. Pull...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-536) Create endpoint for enumerating environments

[Eric Sorenson (JIRA)]

Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-536



  Create endpoint for enumerating environments 










Change By:

 Eric Sorenson









 Much of the  ENC/CD  Node Classifier and Continuous Delivery  work is predicated on improved support for environments, and one significant gap is the absence of a way to enumerate the environments known to a puppet master. 












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-798) New Evaluator does not cache parse results

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg assigned an issue to Henrik Lindberg











 






 Puppet /  PUP-798



  New Evaluator does not cache parse results 










Change By:

 Henrik Lindberg




Assignee:

 Henrik Lindberg












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-941) PR (209): Fix prefix exception message (Closes #23364) - francocatena

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-941



  PR (209): Fix prefix exception message (Closes #23364) - francocatena 










Change By:

 Joshua Cooper




Fix Version/s:

 3.5.0












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1200) [meta] please stop arbitrarily changing systemd service unit names

[Moses Mendoza (JIRA)]

Title: Message Title










 

 Moses Mendoza commented on an issue











 






  Re: [meta] please stop arbitrarily changing systemd service unit names 










What was originally a service called 'puppet' was unfortunately renamed to 'puppetagent' in our systemd files around the time we shipped them for the first time (see http://projects.puppetlabs.com/issues/16144 and https://projects.puppetlabs.com/issues/22660). We decided then to go back to calling it 'puppet.service' for historical consistency, and symlinking puppetagent.service to puppet.service. So in 3.4.0 rpms, we ship both puppet.service and puppetagent.service. For me doing both
systemctl status puppet and systemcl status puppetagent
works fine. Sam Kottler is this not the case for you?












   

 Add Comment











 













 Puppet /  PUP-1200



  [meta] please stop arbitrarily changing systemd service unit names 







 In 3.4, what was previously puppetagent.service is now puppet.service. Now every person who was managing the puppet service and used systemd has to add a case statement based on version. I understand that puppet is a better (and more consistent) name, but the change seems unfounded. Instead of fixing any problem it just introduces yet another complexity i...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 

 

Jira (PUP-798) New Evaluator does not cache parse results

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-798



  New Evaluator does not cache parse results 










Change By:

 Henrik Lindberg




Sprint:

 Week 2013-12-19 to 2014-1-2












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-798) New Evaluator does not cache parse results

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-798



  New Evaluator does not cache parse results 










Change By:

 Henrik Lindberg




Story Points:

 2 1









 The new evaluator does not cache parse result; everything is reparsed on every request.In the previous version the "future parser" also used an instance of the "old parser" to perform imports and to handle caching of parse results.This was obviously inefficient and was removed. The support for caching should be added. It should however not be implemented in the actual parser - the new e4 parser adapter is probably the right place. The problem is worse. Since the layer above assume that once it has parsed a file, it only needs to be checked if it is in the cache of "watched files". 












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-941) PR (209): Fix prefix exception message (Closes #23364) - francocatena

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (209): Fix prefix exception message (Closes #23364) - francocatena 










adrienthebo commented:
Merged into master in b50385b; thanks for the contribution!












   

 Add Comment











 













 Puppet /  PUP-941



  PR (209): Fix prefix exception message (Closes #23364) - francocatena 







 h2. Fix prefix exception message (Closes #23364)   * Author: Franco Catena <>  * Company: Cirope S.A.  * Github ID: [francocatena|https://github.com/francocatena]  * [Pull Request 209 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/209]  * [Pull Request 209 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/209/files]  h2. Pull...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PDB-243) PR (779): Remove illegal keys from fact payload - grimradical

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (779): Remove illegal keys from fact payload - grimradical 










puppetlabs-jenkins commented:
:green_heart: Test passed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/109/












   

 Add Comment











 













 PuppetDB /  PDB-243



  PR (779): Remove illegal keys from fact payload - grimradical 







 h2. Remove illegal keys from fact payload   * Author: Deepak Giridharagopal <>  * Company:   * Github ID: [grimradical|https://github.com/grimradical]  * [Pull Request 779 Discussion|https://github.com/puppetlabs/puppetdb/pull/779]  * [Pull Request 779 File Diff|https://github.com/puppetlabs/puppetdb/pull/779/files]  h2. Pull Request Description   Thi...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-941) PR (209): Fix prefix exception message (Closes #23364) - francocatena

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (209): Fix prefix exception message (Closes #23364) - francocatena 










Pull request Fix prefix exception message (Closes #23364) has been closed.












   

 Add Comment











 













 Puppet /  PUP-941



  PR (209): Fix prefix exception message (Closes #23364) - francocatena 







 h2. Fix prefix exception message (Closes #23364)   * Author: Franco Catena <>  * Company: Cirope S.A.  * Github ID: [francocatena|https://github.com/francocatena]  * [Pull Request 209 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/209]  * [Pull Request 209 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/209/files]  h2. Pull...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1215) PR (2180): (maint) Check package build status earlier in bootstrap - kylog

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot created an issue











 






 Puppet /  PUP-1215



  PR (2180): (maint) Check package build status earlier in bootstrap - kylog 










Issue Type:

  Task




Assignee:


 Unassigned




Components:


 Community




Created:


 20/Dec/13 3:03 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










(maint) Check package build status earlier in bootstrap


Author: Kylo Ginsberg <>


Company:


Github ID: kylog


Pull Request 2180 Discussion


Pull Request 2180 File Diff


Pull Request Description

Jira (PUP-1213) PR (2179): (maint) Provide option to 4x->3x convert to handle :undef differently - hlindberg

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2179): (maint) Provide option to 4x->3x convert to handle :undef differently - hlindberg 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 Puppet /  PUP-1213



  PR (2179): (maint) Provide option to 4x->3x convert to handle :undef differently - hlindberg 







 h2. (maint) Provide option to 4x->3x convert to handle :undef differently   * Author: Henrik Lindberg <>  * Company: Cloudsmith Inc.  * Github ID: [hlindberg|https://github.com/hlindberg]  * [Pull Request 2179 Discussion|https://github.com/puppetlabs/puppet/pull/2179]  * [Pull Request 2179 File Diff|https://github.com/puppetlabs/puppet/pull/2179/files]  h...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PDB-243) PR (779): Remove illegal keys from fact payload - grimradical

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (779): Remove illegal keys from fact payload - grimradical 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 PuppetDB /  PDB-243



  PR (779): Remove illegal keys from fact payload - grimradical 







 h2. Remove illegal keys from fact payload   * Author: Deepak Giridharagopal <>  * Company:   * Github ID: [grimradical|https://github.com/grimradical]  * [Pull Request 779 Discussion|https://github.com/puppetlabs/puppetdb/pull/779]  * [Pull Request 779 File Diff|https://github.com/puppetlabs/puppetdb/pull/779/files]  h2. Pull Request Description   Thi...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (FACT-79) Facter built-in legacy facts are inconsistent in type - convert to string and add simple schema

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg assigned an issue to Kylo Ginsberg











 






 Facter /  FACT-79



  Facter built-in legacy facts are inconsistent in type - convert to string and add simple schema 










Change By:

 Kylo Ginsberg




Assignee:

 Kylo Ginsberg












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PDB-243) PR (779): Remove illegal keys from fact payload - grimradical

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (779): Remove illegal keys from fact payload - grimradical 










Pull request Remove illegal keys from fact payload has been closed.












   

 Add Comment











 













 PuppetDB /  PDB-243



  PR (779): Remove illegal keys from fact payload - grimradical 







 h2. Remove illegal keys from fact payload   * Author: Deepak Giridharagopal <>  * Company:   * Github ID: [grimradical|https://github.com/grimradical]  * [Pull Request 779 Discussion|https://github.com/puppetlabs/puppetdb/pull/779]  * [Pull Request 779 File Diff|https://github.com/puppetlabs/puppetdb/pull/779/files]  h2. Pull Request Description   Thi...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (FACT-107) Define valid outputs for structured data

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo updated an issue











 






 Facter /  FACT-107



  Define valid outputs for structured data 










Change By:

 Adrien Thebo




Issue Type:

 Improvement Task












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (FACT-163) Fact loading logic is overly complicated

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Fact loading logic is overly complicated 










Verified by creating lib/facter/osfamily/test.rb with a high weight resolution. Testing against stable returns that fact, testing against facter-2 behaves as expected.












   

 Add Comment











 













 Facter /  FACT-163



  Fact loading logic is overly complicated 







 The present fact file location and loading logic does a number of clever things like looking for a directory under each search path that matches the facts name and recursively loading directories (except for an exclusion list). An inspection of all current forge modules shows that no existing module is using this behavior and AFAIK, this level of magic w...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

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

[redmine.exporter (JIRA)]

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1214



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










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 20/Dec/13 2:23 PM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










We have four main ways we can specify file content in a file resource.
1. The source parameter 2. The content parameter 3. The file function 4. The template function
These behave inconsistently in the following ways.
The source parameter, file function and template function all can take an array. For source/file, the first file that exists will be used. For the template function, we concatenate the templates instead, and it's a comma separated string "array", not a real array.
The file function takes fully qualified paths only. The template function takes fully qualified paths, or dereferences relative paths as follows. 'foo/bar.erb' -> modules/foo/templates/bar.erb
The latter problem is relatively easily solved, particularly if we implement #4885
We are going to have to break backwards compatibility to solve the first problem however.
My feeling is that more people make use of the multi-select logic in the source parameter/file function than make use of the concatenation of the template function.

Jira (PUP-661) macauthorization provider is broken on 10.9 (mavericks)

[Gary Larizza (JIRA)]

Title: Message Title










 

 Gary Larizza commented on an issue











 






  Re: macauthorization provider is broken on 10.9 (mavericks) 










Can you guys give this a shot --> https://github.com/glarizza/puppet-authorization 
I'm thinking it's probably better to eventually rip these types out of core so we can work on them much faster than tying them to Puppet releases












   

 Add Comment











 













 Puppet /  PUP-661



  macauthorization provider is broken on 10.9 (mavericks) 







 In OS X 10.9, `/etc/authorization` has been "deprecated"; as of the GM, the update will move `/etc/authorization` to `/etc/authorization.deprecated`.   There is now `/System/Library/Security/authorization.plist` but it seems to just be the defaults; changing a right with the `security authorizationdb` command doesn't change that file, but instead updates...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@google

Jira (FACT-163) Fact loading logic is overly complicated

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo updated an issue











 






 Facter /  FACT-163



  Fact loading logic is overly complicated 










Change By:

 Adrien Thebo









 The present fact file location and loading logic does a number of  cleaver  clever  things like looking for a directory under each search path that matches the facts name and recursively loading directories (except for an exclusion list).  An inspection of all current forge modules shows that no existing module is using this behavior and AFAIK, this level of magic was not documented anywhere.  The cutting down the complexity of this logic will both simply the code and reduce the amount of work facter (and the filesystem) does.












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PDB-243) PR (779): Remove illegal keys from fact payload - grimradical

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-243



  PR (779): Remove illegal keys from fact payload - grimradical 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 20/Dec/13 2:16 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Remove illegal keys from fact payload


Author: Deepak Giridharagopal <>


Company:


Github ID: grimradical


Pull Request 779 Discussion


Pull Request 779 File Diff


Pull Request Description

This patch makes us strict about the exact set of keys we want to include in the payload when we submit facts to puppetdb. The wire format only allows for "name" and "values" keys, so that's all we should allow.

(webhooks-id: d65e03ad95ce3d55ac99fdeebc4d517e)
  

Jira (FACT-172) PR (584): Issue/fact 79/facter 2/add facter schema - kylog

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (584): Issue/fact 79/facter 2/add facter schema - kylog 










kylog commented:
@jhoblitt, thanks for trying it out on some other platforms. I wondered if just alphanumeric was enough for interface names ...












   

 Add Comment











 













 Facter /  FACT-172



  PR (584): Issue/fact 79/facter 2/add facter schema - kylog 







 h2. Issue/fact 79/facter 2/add facter schema   * Author: Kylo Ginsberg <>  * Company:   * Github ID: [kylog|https://github.com/kylog]  * [Pull Request 584 Discussion|https://github.com/puppetlabs/facter/pull/584]  * [Pull Request 584 File Diff|https://github.com/puppetlabs/facter/pull/584/files]  h2. Pull Request Description   This is to replace pull ...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1213) PR (2179): (maint) Provide option to 4x->3x convert to handle :undef differently - hlindberg

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot created an issue











 






 Puppet /  PUP-1213



  PR (2179): (maint) Provide option to 4x->3x convert to handle :undef differently - hlindberg 










Issue Type:

  Task




Assignee:


 Unassigned




Components:


 Community




Created:


 20/Dec/13 1:43 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










(maint) Provide option to 4x->3x convert to handle :undef differently


Author: Henrik Lindberg <>


Company: Cloudsmith Inc.


Github ID: hlindberg


Pull Request 2179 Discussion


Pull Request 2179 File Diff


Pull Request Description
   

Jira (PUP-1212) runtime errors in future evaluator has uninformative backtrace

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg created an issue











 






 Puppet /  PUP-1212



  runtime errors in future evaluator has uninformative backtrace 










Issue Type:

  Bug




Assignee:


 Unassigned




Components:


 DSL




Created:


 20/Dec/13 1:39 PM




Fix Versions:


 3.5.0




Priority:

  Normal




Reporter:

 Henrik Lindberg










Runtime errors (that are caught by EvaluatorImpl.evaluate) raise a ParseError, and pass the original exception. When this reaches the top level and is reported to the user, it is always the location of the raised (wrapping) ParseError that is shown (which is quite useless to everyone, except possibly that it was caught there).
Investigate how to best make the cause be shown and implement it.












   

 Add Comment


 

Jira (FACT-172) PR (584): Issue/fact 79/facter 2/add facter schema - kylog

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (584): Issue/fact 79/facter 2/add facter schema - kylog 










jhoblitt commented:
The schema validation seems to stop at the first error which needs to be fixed before it'll continue on to the next (observation only).
These two facts were missing from the schema for Fedora 19. ``` The property '#/' contains additional properties ["macaddress_virbr0_nic", "lsbrelease"] outside of the schema when none are allowed in schema dff1b569-e384-53d1-be0d-be7224eb22a0# ``` ``` The property '#/' contains additional properties ["lsbrelease"] outside of the schema when none are allowed in schema ec014dfb-ec09-5ae6-a06d-1fb8d0459607# Failed validation. ```
``` diff --git a/schema/facter.json b/schema/facter.json index 2c90536..a454cb4 100644 — a/schema/facter.json +++ b/schema/facter.json @@ -12,7 +12,7 @@ "^netmask_[A-Za-z0-9]+$" :  { "type": "string" }
, "^network_[A-Za-z0-9]+$" :  { "type": "string" }
, "^ipaddress_[A-Za-z0-9]+$" :  { "type": "string" }
,


"^macaddress_[A-Za-z0-9]+$" : { "type": "string" }
, + "^macaddress_[A-Za-z0-9_]+$" :  { "type": "string" }
, "^processor[0-9]+" :  { "type": "string" }
 }, "properties": { @@ -47,6 +47,7 @@ "lsbdistid" :  { "type": "string" }
, "lsbdistrelease" :  { "type": "string" }
, "lsbmajdistrelease" :  { "type": "string" }
, + "lsbrelease" :  { "type": "string" }
, "macaddress" :  { "type": "string" }
, "macosx_buildversion" :  { "type": "string" }
, "macosx_productname" :  { "type": "string" }
, ```














   

 Add Comment











 













 Facter / 

Jira (FACT-172) PR (584): Issue/fact 79/facter 2/add facter schema - kylog

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (584): Issue/fact 79/facter 2/add facter schema - kylog 










jhoblitt commented:
It won't work for the dynamic facts but we could probably walk the collection after a load_all for a listing of all possible static fact names.












   

 Add Comment











 













 Facter /  FACT-172



  PR (584): Issue/fact 79/facter 2/add facter schema - kylog 







 h2. Issue/fact 79/facter 2/add facter schema   * Author: Kylo Ginsberg <>  * Company:   * Github ID: [kylog|https://github.com/kylog]  * [Pull Request 584 Discussion|https://github.com/puppetlabs/facter/pull/584]  * [Pull Request 584 File Diff|https://github.com/puppetlabs/facter/pull/584/files]  h2. Pull Request Description   This is to replace pull ...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (FACT-172) PR (584): Issue/fact 79/facter 2/add facter schema - kylog

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (584): Issue/fact 79/facter 2/add facter schema - kylog 










jhoblitt commented:
Scratch that observation... I'm blind.












   

 Add Comment











 













 Facter /  FACT-172



  PR (584): Issue/fact 79/facter 2/add facter schema - kylog 







 h2. Issue/fact 79/facter 2/add facter schema   * Author: Kylo Ginsberg <>  * Company:   * Github ID: [kylog|https://github.com/kylog]  * [Pull Request 584 Discussion|https://github.com/puppetlabs/facter/pull/584]  * [Pull Request 584 File Diff|https://github.com/puppetlabs/facter/pull/584/files]  h2. Pull Request Description   This is to replace pull ...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1211) Puppet Resource Package fails

[Michelle Johansen (JIRA)]

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1211



  Puppet Resource Package fails 










Change By:

 Michelle Johansen




Sprint:

 Week 2013-12-19 to 2014-1-2












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1211) Puppet Resource Package fails

[Ethan Brown (JIRA)]

Title: Message Title










 

 Ethan Brown updated an issue











 






 Puppet /  PUP-1211



  Puppet Resource Package fails 










Change By:

 Ethan Brown




Story Points:

 2












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1211) Puppet Resource Package fails

[Michelle Johansen (JIRA)]

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1211



  Puppet Resource Package fails 










Change By:

 Michelle Johansen




Assignee:

 Michelle Johansen Joshua Cooper












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1211) Puppet Resource Package fails

[Michelle Johansen (JIRA)]

Title: Message Title










 

 Louis Mayorga created an issue











 






 Puppet /  PUP-1211



  Puppet Resource Package fails 










Issue Type:

  Bug




Assignee:

 Michelle Johansen




Components:


 PE




Created:


 20/Dec/13 1:21 PM




Environment:


Windows 7




Labels:


 windows




Priority:

  Normal




Reporter:

 Louis Mayorga










Trying to get all windows package resources i get the following error



ruby 1.9.3p448 (2013-06-27) [i386-mingw32]

C:\Windows\system32>puppet resource package
Error: Could not run: invalid byte sequence in US-ASCII















   

Jira (PUP-1210) authentication_authority key is not set when managing root's password using the puppet user provider

[redmine.exporter (JIRA)]

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1210



  authentication_authority key is not set when managing root's password using the puppet user provider 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 20/Dec/13 1:20 PM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










If you try to set the root password on OS X using the Puppet user provider, there are two bugs:
1. /var/db/dslocal/nodes/Default/users/root.plist has the 'passwd' key set incorrectly. It sets:
passwd 
when it should be:
passwd   
This causes 'dscl . read /Users/root' to not display the contents of the 'Password' attribute. If you use 'dsenableroot' to enable root, you can see how the passwd key should be set (both in dscl and reading the .plist in dslocal).
2. The root user cannot log in via the loginwindow (GUI login). SSH works, but the GUI does not. The major differences I see between root and other puppet-made accounts is that root lacks the 'KerberosKeys' and 'authentication_authority' keys in its dslocal plist.

Jira (PUP-1209) Exec provider should support environment variables with empty values

[redmine.exporter (JIRA)]

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1209



  Exec provider should support environment variables with empty values 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 20/Dec/13 1:10 PM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










The exec provider takes an environment parameter that takes either a string or an array of variables. Each variable is expressed as a pair, like "KEY=value" for example. The problem is that the code that parses this string requires a value whereas this is not strictly necessary, like "KEY=" should be perfectly acceptable. The code in Puppet::Provider::Exec.run looks like this:
 if setting =~ /^(\w+)=((.|\n)+)$/ env_name = $1 value = $2 
Simply changing the regular _expression_ to use "*" instread of "+" for the value should work just fine:
 irb(main):001:0> setting = 'KEY=' => "KEY=" irb(main):002:0> setting =~ /^(\w+)=((.|\n)+)$/ => nil irb(main):003:0> setting =~ /^(\w+)=((.|\n)*)$/ => 0 irb(main):004:0> $1 => "KEY" irb(main):005:0> $2 => "" 
So, the value of empty string is exactly what was requested.












   
   

Jira (FACT-154) PR (574): Backport non-functional changes from master to facter-2 - adrienthebo

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (574): Backport non-functional changes from master to facter-2 - adrienthebo 










Pull request Backport non-functional changes from master to facter-2 has been closed.












   

 Add Comment











 













 Facter /  FACT-154



  PR (574): Backport non-functional changes from master to facter-2 - adrienthebo 







 h2. Backport non-functional changes from master to facter-2   * Author: Adrien Thebo git...@somethingsinistral.net>  * Company: Puppet Labs  * Github ID: [adrienthebo|https://github.com/adrienthebo]  * [Pull Request 574 Discussion|https://github.com/puppetlabs/facter/pull/574]  * [Pull Request 574 File Diff|https://github.com/puppetlabs/facter/pull/5...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (FACT-172) PR (584): Issue/fact 79/facter 2/add facter schema - kylog

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (584): Issue/fact 79/facter 2/add facter schema - kylog 










kylog commented:
@jhoblitt I took up some of your suggestions in pull #581:


added a check that there is a schema for each fact (easier than I was thinking)


improved output from validate.rb and added an explanatory README.md


Extending this to spec tests is interesting but outside the scope of the current ticket. Meanwhile, I want to do some CI work to expand the platforms that it runs acceptance tests on, since that will broaden the real-world coverage.












   

 Add Comment











 













 Facter /  FACT-172



  PR (584): Issue/fact 79/facter 2/add facter schema - kylog 







 h2. Issue/fact 79/facter 2/add facter schema   * Author: Kylo Ginsberg <>  * Company:   * Github ID: [kylog|https://github.com/kylog]  * [Pull Request 584 Discussion|https://github.com/puppetlabs/facter/pull/584]  * [Pull Request 584 File Diff|https://github.com/puppetlabs/facter/pull/584/files]  h2. Pull Request Description   This is to replace pull ...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
   

Jira (PUP-1208) md5lite, mtime not honoured for file type/provider

[redmine.exporter (JIRA)]

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1208



  md5lite, mtime not honoured for file type/provider 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 20/Dec/13 12:46 PM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










It seems I can't get the puppetmaster to honour the checksum => mtime setting, or the md5lite setting. So the following example has no performance improvement over just using md5:
 file { "/testtransfer": ensure => directory, recurse => remote, purge => true, checksum => mtime, source => "puppet:///modules/$ {module_name}
/bigfileshere", }
The problem seems to be in multiple places. The first place, I can't get the file_server/metadata to respond with mtime, md5lite checksums:


curl -k --cert /etc/puppetlabs/pupem --key /etc/puppetlabs/puppet/ssl/private_keys/puppetclient2.vm.pem --cacert /etc/puppetlabs/puppet/ssl/certs/ca.pem -H 'Accept: yaml' 'https://puppet:8140/production/file_metadatas/modules/filetransfer/sles/SLES-11-SP1-DVD-x86_64-GM-DVD1.iso checksum_type=md5lite'








  

Jira (PUP-1207) Setting a status command on a service calls the status command even when hasstatus=true

[redmine.exporter (JIRA)]

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1207



  Setting a status command on a service calls the status command even when hasstatus=true 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 20/Dec/13 12:17 PM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










The agent runs a service's status command even when hasstatus is explicitly set to true on that service. Based on the type reference, it seems setting hasstatus=true should force the agent to use the service's init script instead of the custom status command.
provider/service/redhat.rb seems like it's doing the right thing, so I'm not sure where the problem lies.
– Declare whether the service’s init script has a functional status command; defaults to true. This attribute’s default value changed in Puppet 2.7.0. [...] If a service’s init script does not support any kind of status command, you should set hasstatus to false and either provide a specific command using the status attribute or expect that Puppet will look for the service name in the process table. –
[jwm@hsph02:pts/1 ~> lsb_release -d Description: CentOS release 5.7 (Final) [jwm@hsph02:pts/1 ~> rpm -q puppet puppet-3.2.2-1.el5 [jwm@hsph02:pts/1 ~> cat service-status.pp  service  { 'snmpd': ensure => running, hasstatus => true, status => 'touch /tmp/foo', }
[jwm@hsph02:pts/1 ~> sudo puppet apply -vd service-status.pp  [...] Debug: Loaded state in 0.23 seconds Info: Applying configuration version '1371763702' [...] Debug: Executing 'touch /tmp/foo'


  

Jira (MCO-7) PR (1): Show details of whats changed in puppet summary report - gtmtech

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (1): Show details of whats changed in puppet summary report - gtmtech 










matthewbarr commented:
This probably needs some help on puppet 3.3. It's not working there.  
Not sure if it was ever working on puppet 3, over all. 
(I'm also using mco 2.2.X)












   

 Add Comment











 













 MCollective /  MCO-7



  PR (1): Show details of whats changed in puppet summary report - gtmtech 







 h2. Show details of whats changed in puppet summary report   * Author: Geoff Meakin   * Company: GTMTECH Ltd  * Github ID: [gtmtech|https://github.com/gtmtech]  * [Pull Request 1 Discussion|https://github.com/puppetlabs/mcollective-puppet-agent/pull/1]  * [Pull Request 1 File Diff|https://github.com/puppetlabs/mcollective-puppet-agent...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1192) PR (2176): (maint) Windows file provider :links => :follow - Iristyle

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: PR (2176): (maint) Windows file provider :links => :follow - Iristyle 










Merged in e327840 to be released in 3.5.0












   

 Add Comment











 













 Puppet /  PUP-1192



  PR (2176): (maint) Windows file provider :links => :follow - Iristyle 







 h2. (maint) Windows file provider :links => :follow   * Author: Ethan J. Brown <>  * Company:   * Github ID: [Iristyle|https://github.com/Iristyle]  * [Pull Request 2176 Discussion|https://github.com/puppetlabs/puppet/pull/2176]  * [Pull Request 2176 File Diff|https://github.com/puppetlabs/puppet/pull/2176/files]  h2. Pull Request Description   - Prev...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1192) PR (2176): (maint) Windows file provider :links => :follow - Iristyle

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1192



  PR (2176): (maint) Windows file provider :links => :follow - Iristyle 










Change By:

 Joshua Cooper




Story Points:

 1












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1192) PR (2176): (maint) Windows file provider :links => :follow - Iristyle

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1192



  PR (2176): (maint) Windows file provider :links => :follow - Iristyle 










Change By:

 Joshua Cooper




Fix Version/s:

 3.5.0












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1192) PR (2176): (maint) Windows file provider :links => :follow - Iristyle

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1192



  PR (2176): (maint) Windows file provider :links => :follow - Iristyle 










Change By:

 Joshua Cooper




Affects Version/s:

 3.4.0












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1192) PR (2176): (maint) Windows file provider :links => :follow - Iristyle

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper assigned an issue to Joshua Cooper











 






 Puppet /  PUP-1192



  PR (2176): (maint) Windows file provider :links => :follow - Iristyle 










Change By:

 Joshua Cooper




Assignee:

 Joshua Cooper












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1192) PR (2176): (maint) Windows file provider :links => :follow - Iristyle

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1192



  PR (2176): (maint) Windows file provider :links => :follow - Iristyle 










Change By:

 Joshua Cooper




Sprint:

 Week 2013-12-19 to 2014-1-2












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1206) Augeas lenses in modules are not loaded when using puppet apply

[redmine.exporter (JIRA)]

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1206



  Augeas lenses in modules are not loaded when using puppet apply 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 20/Dec/13 12:03 PM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










When you have custom lenses in your modules lib/augeas/lenses, these are not loaded by augeas when doing a puppet apply run.












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

Jira (PUP-1192) PR (2176): (maint) Windows file provider :links => :follow - Iristyle

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2176): (maint) Windows file provider :links => :follow - Iristyle 










Pull request (maint) Windows file provider :links => :follow has been closed.












   

 Add Comment











 













 Puppet /  PUP-1192



  PR (2176): (maint) Windows file provider :links => :follow - Iristyle 







 h2. (maint) Windows file provider :links => :follow   * Author: Ethan J. Brown <>  * Company:   * Github ID: [Iristyle|https://github.com/Iristyle]  * [Pull Request 2176 Discussion|https://github.com/puppetlabs/puppet/pull/2176]  * [Pull Request 2176 File Diff|https://github.com/puppetlabs/puppet/pull/2176/files]  h2. Pull Request Description   - Prev...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (FACT-172) PR (584): Issue/fact 79/facter 2/add facter schema - kylog

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (584): Issue/fact 79/facter 2/add facter schema - kylog 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 Facter /  FACT-172



  PR (584): Issue/fact 79/facter 2/add facter schema - kylog 







 h2. Issue/fact 79/facter 2/add facter schema   * Author: Kylo Ginsberg <>  * Company:   * Github ID: [kylog|https://github.com/kylog]  * [Pull Request 584 Discussion|https://github.com/puppetlabs/facter/pull/584]  * [Pull Request 584 File Diff|https://github.com/puppetlabs/facter/pull/584/files]  h2. Pull Request Description   This is to replace pull ...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (MCO-143) Windows agents stop working when the mcollective service cannot be restarted

[Nick Walker (JIRA)]

Title: Message Title










 

 Nick Walker updated an issue











 






 MCollective /  MCO-143



  Windows agents stop working when the mcollective service cannot be restarted 










Change By:

 Nick Walker




Labels:

 customer support












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (MCO-143) Windows agents stop working when the mcollective service cannot be restarted

[Nick Walker (JIRA)]

Title: Message Title










 

 Nick Walker updated an issue











 






 MCollective /  MCO-143



  Windows agents stop working when the mcollective service cannot be restarted 










Change By:

 Nick Walker









 The windows mcollective service fails to restart from puppet after multiple restarts in a row. The easiest way I found to reproduce the issue is the following: 1.  Install PE3.1 with one windows agent2.  Run `puppet agent -t` on the windows agent and make sure the pe_mcollective module has been applied3.  Change `/etc/puppetlabs/mcollective/credentials` on the master4.  Run `puppet agent -t` on the windows agent and the mcollective/activemq password should be updated and restart the mcollective service.  5.  Repeat steps 3 and 4 until eventually the mcollective service will fail to restart and your puppet agent will not be able to complete runs.  












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-522) Port final test changes from tmpfosstestsforpe back into puppet.

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Port final test changes from tmpfosstestsforpe back into puppet. 










No, of the ci-tooling tickets have made it into our Sprints, and things are very tight right now for 3.5; so I don't expect this will get pulled in by us any time soon.












   

 Add Comment











 













 Puppet /  PUP-522



  Port final test changes from tmpfosstestsforpe back into puppet. 







 There are a few tests that have been added to https://github.com/puppetlabs/tmpfosstestsforpe since we began the testing from packages saga and started the port of pe-puppet acceptance changes back into puppet.   Once we have the current integration/acceptance work merged in, and things are running on the https://jenkins.puppetlabs.com/job/PE-Puppet-Acce...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1133) Windows generates test failures when %ALLUSERSPROFILE%\PuppetLabs\puppet doesn't exist

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper assigned an issue to Joshua Cooper











 






 Puppet /  PUP-1133



  Windows generates test failures when %ALLUSERSPROFILE%\PuppetLabs\puppet doesn't exist 










Change By:

 Joshua Cooper




Assignee:

 Joshua Cooper












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PDB-242) PuppetDB fact terminus code should only include name/values

[Ryan Senior (JIRA)]

Title: Message Title










 

 Ryan Senior created an issue











 






 PuppetDB /  PDB-242



  PuppetDB fact terminus code should only include name/values 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 20/Dec/13 10:02 AM




Priority:

  Normal




Reporter:

 Ryan Senior










Currently extra fields from the Puppet facts object is being serialized and sent to PuppetDB. Specifically Schema cause a timestamp field and an expiration field in storage.clj. name/values are the only two fields specified in the wire format, so we should limit the message to only including those.












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 

   

Jira (PUP-1200) [meta] please stop arbitrarily changing systemd service unit names

[Michael Stahnke (JIRA)]

Title: Message Title










 

 Michael Stahnke assigned an issue to Moses Mendoza











 






 Puppet /  PUP-1200



  [meta] please stop arbitrarily changing systemd service unit names 










Change By:

 Michael Stahnke




Assignee:

 Moses Mendoza












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1200) [meta] please stop arbitrarily changing systemd service unit names

[Michael Stahnke (JIRA)]

Title: Message Title










 

 Michael Stahnke updated an issue











 






 Puppet /  PUP-1200



  [meta] please stop arbitrarily changing systemd service unit names 










Change By:

 Michael Stahnke




Labels:

 systemd












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1201) Renaming puppetagent.service to puppet.service causes puppetagent.service to be left running after upgrading to 3.4

[Michael Stahnke (JIRA)]

Title: Message Title










 

 Michael Stahnke updated an issue











 






 Puppet /  PUP-1201



  Renaming puppetagent.service to puppet.service causes puppetagent.service to be left running after upgrading to 3.4 










Change By:

 Michael Stahnke




Labels:

 systemd












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1201) Renaming puppetagent.service to puppet.service causes puppetagent.service to be left running after upgrading to 3.4

[Michael Stahnke (JIRA)]

Title: Message Title










 

 Michael Stahnke commented on an issue











 






  Re: Renaming puppetagent.service to puppet.service causes puppetagent.service to be left running after upgrading to 3.4 










Hey Releng, let's fix some stuff.












   

 Add Comment











 













 Puppet /  PUP-1201



  Renaming puppetagent.service to puppet.service causes puppetagent.service to be left running after upgrading to 3.4 







 Because of https://tickets.puppetlabs.com/browse/PUP-1200, users who are utilizing systemd as their init system will be left with two agents running forever.   As part of the upgrade process, we need to:  1. stop puppetagent.service  2. disable puppetagent.service  3. remove puppetagent.service from the system  4. enable puppet.service  5. start puppet.s...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (HI-119) PR (168): (maint) Adding beaker gem required items - ferventcoder

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (168): (maint) Adding beaker gem required items - ferventcoder 










Pull request (maint) Adding beaker gem required items has been closed.












   

 Add Comment











 













 Hiera /  HI-119



  PR (168): (maint) Adding beaker gem required items - ferventcoder 







 h2. (maint) Adding beaker gem required items   * Author: Rob Reynolds <>  * Company:   * Github ID: [ferventcoder|https://github.com/ferventcoder]  * [Pull Request 168 Discussion|https://github.com/puppetlabs/hiera/pull/168]  * [Pull Request 168 File Diff|https://github.com/puppetlabs/hiera/pull/168/files]  h2. Pull Request Description   This will all...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1015) Error: Could not intialize global default settings: undefined method `mode=' for #

[Reid Vandewiele (JIRA)]

Title: Message Title










 

 Reid Vandewiele updated an issue











 






 Puppet /  PUP-1015



  Error: Could not intialize global default settings: undefined method `mode=' for # 










Change By:

 Reid Vandewiele









 Follow-on from #23349... regression from 3.3.x to 3.4.0-rc2.  This affects all Foreman users, since it's the default installer configuration (https://github.com/theforeman/puppet-puppet/blob/master/templates/puppet.conf.erb#L21).With this in puppet.conf:  {code} [main]autosign   = $confdir/autosign.conf { mode = 664 }  {code}   {code} # puppet --versionError: Could not intialize global default settings: undefined method `mode=' for ## rpm -q puppetpuppet-3.4.0-0.1rc2.el6.noarch  {code} Sorry for not including the full puppet.conf entry in the earlier bug report, we could have avoided a round trip.












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1205) Relative namespacing of class/define names results in big surprises

[Reid Vandewiele (JIRA)]

Title: Message Title










 

 Reid Vandewiele updated an issue











 






 Puppet /  PUP-1205



  Relative namespacing of class/define names results in big surprises 










Change By:

 Reid Vandewiele









 Due to Puppet's relative namespacing of class names, `include bar` does not mean "declare class `bar`." It actually means "try to declare class `::bar`, class `::bar`, and so on, declaring class `bar` only as a last resort." {code} class bar {  notice("From class bar")}class foo::bar {  notice("From class foo::bar")}class foo {  include bar}include foo {code}   This is maximally surprising, especially considering the prevalence of things like: {code} class apache::nagios {  include nagios # joke's on you, because this just includes apache::nagios again} {code}   (Test code from original report: )












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Could not autoload puppet /util /instrumentation /listeners /log 










Just waiting to hear whether the patch worked for the customer.












   

 Add Comment











 













 Puppet /  PUP-724



  Could not autoload puppet /util /instrumentation /listeners /log 














 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (FACT-167) PR (581): Issue/fact 79/stable/add facter schema - kylog

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (581): Issue/fact 79/stable/add facter schema - kylog 










Pull request Issue/fact 79/stable/add facter schema has been closed.












   

 Add Comment











 













 Facter /  FACT-167



  PR (581): Issue/fact 79/stable/add facter schema - kylog 







 h2. Issue/fact 79/stable/add facter schema   * Author: Kylo Ginsberg <>  * Company:   * Github ID: [kylog|https://github.com/kylog]  * [Pull Request 581 Discussion|https://github.com/puppetlabs/facter/pull/581]  * [Pull Request 581 File Diff|https://github.com/puppetlabs/facter/pull/581/files]  h2. Pull Request Description  (webhooks-id: be8b3...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (FACT-167) PR (581): Issue/fact 79/stable/add facter schema - kylog

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (581): Issue/fact 79/stable/add facter schema - kylog 










kylog commented:
Continued in pull #584 












   

 Add Comment











 













 Facter /  FACT-167



  PR (581): Issue/fact 79/stable/add facter schema - kylog 







 h2. Issue/fact 79/stable/add facter schema   * Author: Kylo Ginsberg <>  * Company:   * Github ID: [kylog|https://github.com/kylog]  * [Pull Request 581 Discussion|https://github.com/puppetlabs/facter/pull/581]  * [Pull Request 581 File Diff|https://github.com/puppetlabs/facter/pull/581/files]  h2. Pull Request Description  (webhooks-id: be8b3...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (FACT-172) PR (584): Issue/fact 79/facter 2/add facter schema - kylog

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot created an issue











 






 Facter /  FACT-172



  PR (584): Issue/fact 79/facter 2/add facter schema - kylog 










Issue Type:

  Task




Assignee:

 Eric Sorenson




Components:


 Community




Created:


 20/Dec/13 9:09 AM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Issue/fact 79/facter 2/add facter schema


Author: Kylo Ginsberg <>


Company:


Github ID: kylog


Pull Request 584 Discussion


Pull Request 584 File Diff


Pull Request Description

This is to replace pull #581 which was pointed at the wrong branch (stable)

Jira (PUP-1205) Relative namespacing of class/define names results in big surprises

[redmine.exporter (JIRA)]

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1205



  Relative namespacing of class/define names results in big surprises 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 20/Dec/13 8:54 AM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










Due to Puppet's relative namespacing of class names, `include bar` does not mean "declare class `bar`." It actually means "try to declare class `::bar`, class `::bar`, and so on, declaring class `bar` only as a last resort."
 class bar  { notice("From class bar") }
 class foo::bar  { notice("From class foo::bar") }
 class foo  { include bar }
 include foo
This is maximally surprising, especially considering the prevalence of things like:
 class apache::nagios  { include nagios # joke's on you, because this just includes apache::nagios again }
(Test code from original report: )












   

 Add 

Jira (PUP-1176) Add feature switch for evaluator

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg assigned an issue to Henrik Lindberg











 






 Puppet /  PUP-1176



  Add feature switch for evaluator 










Change By:

 Henrik Lindberg




Assignee:

 Henrik Lindberg












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1200) [meta] please stop arbitrarily changing systemd service unit names

[Michael Stahnke (JIRA)]

Title: Message Title










 

 Michael Stahnke commented on an issue











 






  Re: [meta] please stop arbitrarily changing systemd service unit names 










Matthaus Owens and Moses Mendoza can you weigh in here?












   

 Add Comment











 













 Puppet /  PUP-1200



  [meta] please stop arbitrarily changing systemd service unit names 







 In 3.4, what was previously puppetagent.service is now puppet.service. Now every person who was managing the puppet service and used systemd has to add a case statement based on version. I understand that puppet is a better (and more consistent) name, but the change seems unfounded. Instead of fixing any problem it just introduces yet another complexity i...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1195) PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-1195



  PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar 










Change By:

 Henrik Lindberg




Labels:

 github  stdlib












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1015) Error: Could not intialize global default settings: undefined method `mode=' for #

[Mike Plugge (JIRA)]

Title: Message Title










 

 Mike Plugge commented on an issue











 






  Re: Error: Could not intialize global default settings: undefined method `mode=' for # 










Commenting the autosign configuration line in the [main] section while keeping the autosign line in the [master] section appears to resolve this.
Not sure if this is intended behavior, but hopefully this is helpful to someone.
My environment: $ rpm -q puppet puppet-3.4.0-1.el6.noarch  $ rpm -q foreman foreman-1.2.3-1.el6.noarch












   

 Add Comment











 













 Puppet /  PUP-1015



  Error: Could not intialize global default settings: undefined method `mode=' for # 







 Follow-on from #23349... regression from 3.3.x to 3.4.0-rc2. This affects all Foreman users, since it's the default installer configuration (https://github.com/theforeman/puppet-puppet/blob/master/templates/puppet.conf.erb#L21).   With this in puppet.conf:[main]  autosign = $confdir/autosign.conf { mode = 664 }   # pup...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To uns

Jira (PUP-1204) Puppet Master (3.2.2/CentOs) -> Puppet Agent (3.2.2/W2008)

[Jasper Lievisse Adriaanse (JIRA)]

Title: Message Title










 

 Jasper Lievisse Adriaanse commented on an issue











 






  Re: Puppet Master (3.2.2/CentOs) -> Puppet Agent (3.2.2/W2008) 










With Puppet 3.4 on the master (OpenBSD) and the agent (Win7 / x86_64) I did not run into this issue anymore.
Could someone confirm this?












   

 Add Comment











 













 Puppet /  PUP-1204



  Puppet Master (3.2.2/CentOs) -> Puppet Agent (3.2.2/W2008) 







 Hello,   I am experiencing this issue.   Could not retrieve domain: undefined method `gsub' for nil:NilClass  Could not retrieve domain: undefined method `gsub' for nil:NilClass  Could not retrieve domain: undefined method `gsub' for nil:NilClass  Error: Failed to apply catalog: SSL_connect SYSCALL returned=5 errno=0 state=SSL  v2/v3 read server hello A...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1204) Puppet Master (3.2.2/CentOs) -> Puppet Agent (3.2.2/W2008)

[redmine.exporter (JIRA)]

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1204



  Puppet Master (3.2.2/CentOs) -> Puppet Agent (3.2.2/W2008) 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 20/Dec/13 6:35 AM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










Hello,
I am experiencing this issue.
Could not retrieve domain: undefined method `gsub' for nil:NilClass Could not retrieve domain: undefined method `gsub' for nil:NilClass Could not retrieve domain: undefined method `gsub' for nil:NilClass Error: Failed to apply catalog: SSL_connect SYSCALL returned=5 errno=0 state=SSL v2/v3 read server hello A
With PMaster -> PAgent = 3.2.2 and CentOs, no issue.
Please advise.












   

 Add Comment








   

Jira (PUP-1203) Ordering with chaining arrows and collectors is not working

[redmine.exporter (JIRA)]

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1203



  Ordering with chaining arrows and collectors is not working 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 20/Dec/13 6:32 AM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










Consider the following scenario: An anchor that marks the start of a class needs to have ordering statements so the Anchor is processed before any package in that class.
According to the lang docs, tags section, :
Every resource automatically receives the following tags:  Its resource type  The full name of the class and/or defined type in which the resource was declared  Every namespace segment of the resource’s class and/or defined type 
Therefore, it would make sense to use the following code to establish ordering relationships between start anchors and class resources:  class testmod { anchor  { 'testmod::begin': }
 Anchor['testmod::begin'] -> Package <| tag == 'testmod' |>
 package  { 'htop': }
 package  { 'vim': }
} 
However, the outcome is that the expressed order relationship is missing. For this example class, using Puppet version:3.2.2, I get the following dot file generated by Puppet, which clearly shows that the DAG is missing the connection between the Anchor and the package resources: http://pastebin.ca/2478032
This, of course, unfortunately results in broken puppet runs. (Or worse, you ar

Jira (PUP-1202) ENC should instantiate defines

[redmine.exporter (JIRA)]

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1202



  ENC should instantiate defines 










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 20/Dec/13 5:20 AM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










It would be great if Puppets ENC could instantiate defines. A simple example:
site.pp cleanup_2::cleanup  {"/var/log/php/": matches => "*", recurse => false, size => "300m", age => "6w", rmdirs => false, }
 cleanup_2::cleanup  {"/appserver/mapbender/log/": matches => "*", recurse => true, size => "100m", age => "2w", rmdirs => false, }
cleanup_2/init.pp
class cleanup_2 { 
define cleanup ($matches, $age, $size, $recurse, $rmdirs) { tidy  {"$name": matches => $matches, age => $age, size => $size, recurse => $recurse, backup => false, rmdirs => $rmdirs, type => mtime; }
} }
This can not be done with the current ENC, you just can add one define to a node... .












   

Jira (PUP-1201) Renaming puppetagent.service to puppet.service causes puppetagent.service to be left running after upgrading to 3.4

[Sam Kottler (JIRA)]

Title: Message Title










 

 Sam Kottler created an issue











 






 Puppet /  PUP-1201



  Renaming puppetagent.service to puppet.service causes puppetagent.service to be left running after upgrading to 3.4 










Issue Type:

  Bug




Affects Versions:


 3.4.0




Assignee:

 Sam Kottler




Components:


 Packaging




Created:


 20/Dec/13 5:07 AM




Priority:

  Major




Reporter:

 Sam Kottler










Because of https://tickets.puppetlabs.com/browse/PUP-1200, users who are utilizing systemd as their init system will be left with two agents running forever.
As part of the upgrade process, we need to: 1. stop puppetagent.service 2. disable puppetagent.service 3. remove puppetagent.service from the system 4. enable puppet.service 5. start puppet.service












   

 Add Comment



 

Jira (PUP-1200) [meta] please stop arbitrarily changing systemd service unit names

[Sam Kottler (JIRA)]

Title: Message Title










 

 Sam Kottler commented on an issue











 






  Re: [meta] please stop arbitrarily changing systemd service unit names 










Also, I'm considering installing puppet.service as puppetagent.service in the official Fedora packages. Can we agreed to do that in the PL packages, too?












   

 Add Comment











 













 Puppet /  PUP-1200



  [meta] please stop arbitrarily changing systemd service unit names 







 In 3.4, what was previously puppetagent.service is now puppet.service. Now every person who was managing the puppet service and used systemd has to add a case statement based on version. I understand that puppet is a better (and more consistent) name, but the change seems unfounded. Instead of fixing any problem it just introduces yet another complexity i...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1200) [meta] please stop arbitrarily changing systemd service unit names

[Sam Kottler (JIRA)]

Title: Message Title










 

 Sam Kottler created an issue











 






 Puppet /  PUP-1200



  [meta] please stop arbitrarily changing systemd service unit names 










Issue Type:

  Improvement




Affects Versions:


 3.4.0




Assignee:


 Unassigned




Created:


 20/Dec/13 4:31 AM




Priority:

  Normal




Reporter:

 Sam Kottler










In 3.4, what was previously puppetagent.service is now puppet.service. Now every person who was managing the puppet service and used systemd has to add a case statement based on version. I understand that puppet is a better (and more consistent) name, but the change seems unfounded. Instead of fixing any problem it just introduces yet another complexity in end-user interaction with packaged versions of puppet.












   

 Add Comment











 

Jira (PUP-1199) Check for immutable files managed by Puppet

[redmine.exporter (JIRA)]

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1199



  Check for immutable files managed by Puppet 










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 20/Dec/13 4:31 AM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










Puppet should be able to override files it manages that are made immutable with chattr/chflags, perhaps by updating the File resource and determining what environment it's being run on.












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
 

Jira (PUP-1198) Package type and provider need to consider `purged` and `absent` packages identical for yum and similar providers

[redmine.exporter (JIRA)]

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1198



  Package type and provider need to consider `purged` and `absent` packages identical for yum and similar providers 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 20/Dec/13 1:38 AM




Labels:


 redmine customer




Priority:

  Normal




Reporter:

 redmine.exporter










I have a package resource that I want to remove, including all of its dependencies. On Red Hat systems, this is done by "yum -y erase ". 
The corresponding puppet code is:
 package  { : ensure => purged }

However, puppet prints this into the logs:
 debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm -q abrt --nosignature --nodigest --qf % {NAME}
 %|EPOCH?{%{EPOCH}}: {0}
| % {VERSION}
 % {RELEASE}
 % {ARCH}
' debug: Puppet::Type::Package::ProviderYum: Executing '/usr/bin/yum -y erase abrt' notice: /Stage[main]/Global/Package[abrt]/ensure: created 
The notice is clearly incorrect, as there's nothing that's been created. In fact, it repeatedly prints this notice and runs the "yum erase" command long after the package has actually been removed. 
Both of these behaviors are incorrect, and are caused by the RAL returning `absent` as the package state, while `purged` is required for the resource to settle.