date:20140318

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1932



  systemd reports transient (in-memory) services 










Change By:

 Kylo Ginsberg




Affects Version/s:

 3.5.0 RC












   

 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/d/optout.

Jira (PUP-1932) systemd reports transient (in-memory) services

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1932



  systemd reports transient (in-memory) services 










Change By:

 Kylo Ginsberg




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/d/optout.

Jira (PUP-1932) systemd reports transient (in-memory) services

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1932



  systemd reports transient (in-memory) services 










Change By:

 Kylo Ginsberg




Component/s:

 Types and Providers












   

 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/d/optout.

Jira (PUP-1932) systemd reports transient (in-memory) services

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1932



  systemd reports transient (in-memory) services 










Change By:

 Kylo Ginsberg




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/d/optout.

Jira (PUP-1932) systemd reports transient (in-memory) services

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1932



  systemd reports transient (in-memory) services 










Change By:

 Kylo Ginsberg




Sprint:

 Week 2014-3-19 to 2014-3-26












   

 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/d/optout.

Jira (PUP-1952) Run specs against jruby

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Run specs against jruby 










Let's keep this ticket open. The jruby specs are still not successfully running in travis (travis is green because the jruby job is under allow_failure), so it still needs some work.












   

 Add Comment











 













 Puppet /  PUP-1952



  Run specs against jruby 














 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/d/optout.

Jira (PDB-517) PR (889): Add jdk8 tests to travis-ci - grimradical

2014-03-18 Thread gepetto-bot (JIRA)

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (889): Add jdk8 tests to travis-ci - grimradical 










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












   

 Add Comment











 













 PuppetDB /  PDB-517



  PR (889): Add jdk8 tests to travis-ci - grimradical 







 h2. Add jdk8 tests to travis-ci   * Author: Deepak Giridharagopal <>  * Company:   * Github ID: [grimradical|https://github.com/grimradical]  * [Pull Request 889 Discussion|https://github.com/puppetlabs/puppetdb/pull/889]  * [Pull Request 889 File Diff|https://github.com/puppetlabs/puppetdb/pull/889/files]  h2. Pull Request Description  (webho...















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

Jira (PUP-1978) future parser doesn't accept empty array as title

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: future parser doesn't accept empty array as title 










merged to stable: 92ae79c1c798887be858c5445b44eceba7cf25bd merged to master: 7807591405af849da2ad6534c66bd2d4efff604f












   

 Add Comment











 













 Puppet /  PUP-1978



  future parser doesn't accept empty array as title 







 When passed an empty array the future parser ends up giving an unhelpful error message {{Error: Evaluation Error: Group[] accepts 1 argument. Got 0 on node super-secret-foo}}   {noformat}  /usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/runtime3_support.rb:19:in `fail'  /usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/access_operator.rb:443:in `access_PRe...















 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/d/optout.

Jira (PUP-996) future evaluator should warn/error if relationship is formed with empty set

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: future evaluator should warn/error if relationship is formed with empty set 










There is yet another way to create an empty set in 3x (but that already raises an error in future parser).



File[a] -> File[[]] -> File[b]















   

 Add Comment











 













 Puppet /  PUP-996



  future evaluator should warn/error if relationship is formed with empty set 







 If a relationship is formed with an empty set of references,, there will be no relationships created. In practice this becomes a problem when a set is empty as in the following example:  {code}  File[a] -> [] -> File[b]  {code}   Which is the same as:  {code}  File[a] -> []  [] -> File[b]  {code}  (I.e. it is not just a problem in a chaining operation). ...















 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

Jira (HI-225) allow interleaved querying of backends

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: allow interleaved querying of backends 










So this will break everyone that relies on the current behavior...












   

 Add Comment











 













 Hiera /  HI-225



  allow interleaved querying of backends 







 When Hiera processes the sources, it will iterate through them completely, first with the first backend, then the next backend.   Given a hiera.yaml like     :hierarchy:  - site-%{::site}  - common    :backends:  - yaml  - json   and the files site-external.json and common.yaml, the value in common.yaml will override the value in site-e...















 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/d/optout.

Jira (PUP-1540) Puppet should support compilation failure if a variable is undefined

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Puppet should support compilation failure if a variable is undefined 










Does the option in Puppet 3.5.0 --strict_variables = true do what is wanted? It works for both --parser-future and regular parser.



puppet apply -e 'notice $a' --strict_variables
Error: Undefined variable "a" at line 1 on node kermit.example.local



For 4x, the idea is to make this option default to true.












   

 Add Comment











 













 Puppet /  PUP-1540



  Puppet should support compilation failure if a variable is undefined 







 Currently, if a variable is undefined in puppet code, compilation succeeds, and the value is undef. E.g.  {noformat}  notify { $foo: }  {noformat}   results in   {noformat}  Notice: /Stage[main]//Notify[undef]/message: defined 'message' as 'undef'  {noformat}   Similarly, if you try to use an undefined variable inside a template, in interpolates to an ...















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

Jira (PUP-1978) future parser doesn't accept empty array as title

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-1978



  future parser doesn't accept empty array as title 










Change By:

 Henrik Lindberg




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/d/optout.

Jira (PUP-1978) future parser doesn't accept empty array as title

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-1978



  future parser doesn't accept empty array as title 










Change By:

 Henrik Lindberg




Sprint:

 Week 2014-3-12 to 2014-3-19












   

 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/d/optout.

Jira (PUP-1978) future parser doesn't accept empty array as title

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: future parser doesn't accept empty array as title 










PR is now available - found a number of small glitches wrt. error reporting involving the [] operator and types. The reported issue and a handful of others; reporting the wrong number of accepted arguments, or passing the wrong reference object for source positioning are now fixed.












   

 Add Comment











 













 Puppet /  PUP-1978



  future parser doesn't accept empty array as title 







 When passed an empty array the future parser ends up giving an unhelpful error message {{Error: Evaluation Error: Group[] accepts 1 argument. Got 0 on node super-secret-foo}}   {noformat}  /usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/runtime3_support.rb:19:in `fail'  /usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/access_operator.rb:443:in `access_PRe...















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

Jira (PUP-1978) future parser doesn't accept empty array as title

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-1978



  future parser doesn't accept empty array as title 










Change By:

 Henrik Lindberg




Component/s:

 DSL












   

 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/d/optout.

Jira (PDB-517) PR (889): Add jdk8 tests to travis-ci - grimradical

2014-03-18 Thread gepetto-bot (JIRA)

Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-517



  PR (889): Add jdk8 tests to travis-ci - grimradical 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 18/Mar/14 7:12 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Add jdk8 tests to travis-ci


Author: Deepak Giridharagopal <>


Company:


Github ID: grimradical


Pull Request 889 Discussion


Pull Request 889 File Diff


Pull Request Description


(webhooks-id: e32f89ddd2615f67231e43c491f2e174)

Jira (PUP-1975) Environment & transaction_uuid is not passed to facts indirector during compilation

Title: Message Title










 

 Kenneth Barber updated an issue











 






 Puppet /  PUP-1975



  Environment & transaction_uuid is not passed to facts indirector during compilation 










Change By:

 Kenneth Barber




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/d/optout.

Jira (PUP-1975) Environment & transaction_uuid is not passed to facts indirector during compilation

Title: Message Title










 

 Kenneth Barber updated an issue











 






 Puppet /  PUP-1975



  Environment & transaction_uuid is not passed to facts indirector during compilation 










Change By:

 Kenneth Barber




Component/s:

 DSL












   

 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/d/optout.

Jira (PUP-1978) future parser doesn't accept empty array as title

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: future parser doesn't accept empty array as title 










The bug here is that it passed the wrong reference object from which the error reporting logic could not compute a location.












   

 Add Comment











 













 Puppet /  PUP-1978



  future parser doesn't accept empty array as title 







 When passed an empty array the future parser ends up giving an unhelpful error message {{Error: Evaluation Error: Group[] accepts 1 argument. Got 0 on node super-secret-foo}}   {noformat}  /usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/runtime3_support.rb:19:in `fail'  /usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/access_operator.rb:443:in `access_PRe...















 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/d/optout.

Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Make modulepath, manifest, and config_version configurable per-environment 










Merged into master in 8e1ebb












   

 Add Comment











 













 Puppet /  PUP-1596



  Make modulepath, manifest, and config_version configurable per-environment 







 In order to make the new environment system fully usable, the default modulepath, manifest, and config_version needs to be overridable on a per-environment basis. This is possible in the current system with the environment stanzas and similar flexibility needs to be retained in the directory environments.   Each environment should optionally have an {{en...















 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/d/optout.

Jira (PUP-1914) PR (232): Readd location_for - apenney

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: PR (232): Readd location_for - apenney 










Merged into stdlib's master in e382c0












   

 Add Comment











 













 Puppet /  PUP-1914



  PR (232): Readd location_for - apenney 







 h2. Readd location_for   * Author: Ashley Penney   * Company: Puppetlabs  * Github ID: [apenney|https://github.com/apenney]  * [Pull Request 232 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/232]  * [Pull Request 232 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/232/files]  h2. Pull Request ...















 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/d/optout.

Jira (PUP-1952) Run specs against jruby

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Run specs against jruby 










It was passing in travis, so I think it is good to just add it in. Merged support in Travis into master in a6aa573d. 
Kylo Ginsberg, should this stay open until we have it running in jenkins?












   

 Add Comment











 













 Puppet /  PUP-1952



  Run specs against jruby 














 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/d/optout.

Jira (PUP-1974) Mechanism for securing sensitive catalog data

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Mechanism for securing sensitive catalog data 










I think it is reasonable to add requirements on the new Catalog Builder that it should be designed to be capable of handling encrypted attributes of resources.












   

 Add Comment











 













 Puppet /  PUP-1974



  Mechanism for securing sensitive catalog data 







 Sensitive information such as passwords or key files contained within Puppet catalogs leaks into locations such as PuppetDB or syslog. This elevates the necessary security that must be enforced on these external systems.   It would be valuable to give manifest/module authors the ability to specify resource properties (such as attributes or titles) which...















 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/d/opt

Jira (PDB-509) Document plan and design for environments

Title: Message Title










 

 Kenneth Barber assigned an issue to Kenneth Barber











 






 PuppetDB /  PDB-509



  Document plan and design for environments  










Change By:

 Kenneth Barber




Assignee:

 Kenneth Barber












   

 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/d/optout.

Jira (PDB-453) Update terminus to include environment information

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Update terminus to include environment information 










WIP PR is here: https://github.com/puppetlabs/puppetdb/pull/888
Possibly waiting on PUP-1975 to merge before this one can be merged.












   

 Add Comment











 













 PuppetDB /  PDB-453



  Update terminus to include environment information 







 Terminus data submission should include environment in submitted facts, catalogs and reports.















 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/d/optout.

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

2014-03-18 Thread Nate Walck (JIRA)

Title: Message Title










 

 Nate Walck commented on an issue











 






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










Andy Parker, I think the provider should outright fail if Iterations or salt are missing on a 10.8+ machine. Obviously you cannot predict a bad iterations value, but if one of the two is missing it should behave as if you are missing a required parameter (because you are).
If you try to manage the root user exactly as you would a regular user, you cannot log in via the GUI, which is the issue that this bug is referencing. Something different happens with the root user to enable it that is not required for non-root users. 
Perhaps this functionality isn't even necessary as using root is bad practice, but it was a noted bug that gave no indication that it hadn't actually worked.












   

 Add Comment











 













 Puppet /  PUP-1210



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







 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:   {code:xml}  passwd    {code}   when it should be:   {code:xml}  passwd **...















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

Jira (PUP-1540) Puppet should support compilation failure if a variable is undefined

Title: Message Title










 

 Andy Parker updated an issue











 






 Puppet /  PUP-1540



  Puppet should support compilation failure if a variable is undefined 










Change By:

 Andy Parker




Fix Version/s:

 4.x












   

 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/d/optout.

Jira (PUP-1540) Puppet should support compilation failure if a variable is undefined

Title: Message Title










 

 Andy Parker assigned an issue to Andy Parker











 






 Puppet /  PUP-1540



  Puppet should support compilation failure if a variable is undefined 










Change By:

 Andy Parker




Assignee:

 Eric Sorenson Andy Parker












   

 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/d/optout.

Jira (PUP-1932) systemd reports transient (in-memory) services

Title: Message Title










 

 Kylo Ginsberg assigned an issue to Kylo Ginsberg











 






 Puppet /  PUP-1932



  systemd reports transient (in-memory) services 










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/d/optout.

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

Title: Message Title

Andy Parker commented on an issue

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

When dealing with the root user, there is an extra complication to all of this. The root user can be disabled, independent of managing its password. The password can be set, and set correct, but nobody will be able to log in as root until dsenableroot has been run. I wasn't able to see the same problem with a split between the GUI and the command line. I was able to (after using dsenableroot) log in via the GUI, su, and ssh.

Manage root's password to be "puppet"

user { 'root':
ensure => 'present',
iterations => '25641',
password => 'b876573f7c16c2e6ff541b7b41e4749daff39da335c76f0348ad8820aab8aa0ce1eb2e8b11c8b0fd801025e601832c3040a25ea1dc0cc532496919d8c601da71c4780d056a7c1fe0cc073ee70b1c9bead9282feaaa3dcdb8bd981150535f918b096adcdf258ef0f7b56379568e2ca53c98ce9cdd80dc8e8babb4a94132a6cdd7',
salt => 'ae4752864f88f934365109b5ac4e65cf1d0ac8a13b778e5e1a2354e54c320b31',
}

The above code needs to be run after dsenableroot has bee used to enable the root account. If it is done before it has no effect on anyone's ability to log in.

Add Comment

Puppet / PUP-1210

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

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: {code:xml} passwd {code} when it should

Jira (PUP-1624) PR (2342) Cron handles crontab's equality of target and user strangely

2014-03-18 Thread Tony Vu (JIRA)

Title: Message Title










 

 Tony Vu commented on an issue











 






  Re: PR (2342) Cron handles crontab's equality of target and user strangely 










Looks good with just the target key set, setting this and 

PUP-1585
 to resolved.












   

 Add Comment











 













 Puppet /  PUP-1624



  PR (2342) Cron handles crontab's equality of target and user strangely 







 When managing the target property of a cronjob, the user property uses its default instead (which is the user running puppet). To the crontab provider, these are basically the same, and there is code to handle them equally. Through the mixtures of defaults and actual supplied values, though, bizarre behaviors come up:   {code}  # HEADER: This file was au...















 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

Jira (PUP-389) Support ruby 2.0 x64 on windows

2014-03-18 Thread Lindsey Smith PO (JIRA)

Title: Message Title










 

 Lindsey Smith PO updated an issue











 






 Puppet /  PUP-389



  Support ruby 2.0 x64 on windows 










Change By:

 Lindsey Smith PO









 Ruby x64 builds have been available as of ruby 2.0, and the win32 gem community is catching up. It is important to support puppet on x64, because it eliminates the filesystem redirection nonsense that customers have to deal with when writing manifests and modules on Windows. From Monsanto:{quote}The big issues are being able to access the 64-bit areas of the registry and file system.  When running a 32-bit agent, Windows will by default redirect: · Registry “HKEY_LOCAL_MACHINE\SOFTWARE” to “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node”· File system “C:\Windows\System32” to “C:\windows\SysWOW64” That means there are difficulties trying access registry settings from “HKEY_LOCAL_MACHINE\SOFTWARE” and files from “C:\Windows\System32” unless it is a 64-bit agent.  Examples: · File check:  How do I check the version of file C:\windows\system32\qmgr.dll on a 64-bit Windows server· Script Launch:  Launching powershell.exe from a 32-bit process runs the 32-bit version of PowerShell which would also have the redirection going on.  How do I launch a 64-bit powershell.exe process so it can access the full registry and file system from that PowerShell process.· Facter:  I was trying to add facts for other agents in our environment that are 64-bit on 64-bit servers and 32-bit on 32-bit servers.  This normally requires reading registry settings from keys such as  HKLM\Software\\ (the native HKLM\Software portion of the registry).  I think I finally got this to work after fishing through ruby scripts until I found something that was helpful.  But my solution was completely undocumented, and required me to jump through hoops that would not exist if the agent were 64-bit.   Although I found a solution for facter, registry redirection will be a big problem for powershell scripts if they are always operating in a 32-bit environment.{quote}












   

 Add Comment











 










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

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

Title: Message Title










 

 Andy Parker commented on an issue











 






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










I haven't been able to reproduce the problem where either the root user or any other user, can log in via the GUI, but not any command line. What I have been able to reproduce, I think, is the issue that is provided in the pe-users thread linked to by Eric Sorenson. What seems to be happening there is that on 10.8 and 10.9 all three of password, salt, and iterations need to be provided in order to end up with a working password. I've confirmed this with the following working manifest, which creates a user with the password of "puppet":


Valid user



user { 'otheruser':
  ensure => 'present',
  comment=> 'Puppet Test User',
  gid=> '20',
  groups => ['com.apple.sharepoint.group.1'],
  home   => '/Users/otheruser',
  iterations => '25641',
  password   => 'b876573f7c16c2e6ff541b7b41e4749daff39da335c76f0348ad8820aab8aa0ce1eb2e8b11c8b0fd801025e601832c3040a25ea1dc0cc532496919d8c601da71c4780d056a7c1fe0cc073ee70b1c9bead9282feaaa3dcdb8bd981150535f918b096adcdf258ef0f7b56379568e2ca53c98ce9cdd80dc8e8babb4a94132a6cdd7',
  salt   => 'ae4752864f88f934365109b5ac4e65cf1d0ac8a13b778e5e1a2354e54c320b31',
  shell  => '/bin/bash',
  uid=> '503',
}



Variations on this all end up creating user accounts that can't be logged into.


Invalid user (iterations given, salt missing)



user { 'iterationsuser':
  ensure => 'present',
  comment=> 'Iterations Test User',
  gid=> '20',
  groups => ['com.apple.sharepoint.group.1'],
  home   => '/Users/iterationsuser',
  iterations => '25641',
  password   => 'b876573f7c16c2e6ff541b7b41e4749daff39da335c76f0348ad8820aab8aa0ce1eb2e8b11c8b0fd801025e601832c3040a25ea1dc0cc532496919d8c601da71c4780d056a7c1fe0cc073ee70b1c9bead9282feaaa3dcdb8bd981150535f918b096adcdf258ef0f7b56379568e2ca53c98ce9cdd80dc8e8babb4a94132a6cdd7',
  #salt   => 'ae4752864f88f934365109b5ac4e65cf1d0ac8a13b778e5e1a2354e54c320b31',
  shell  => '/bin/bash',
  uid=> '506',
}





Invalid user (salt given, iterations missing)



user { 'saltuser':
  ensure => 'present',
  comment=> 'Salt Test User',
  gid=> '20',
  groups => ['com.apple.sharepoint.group.1'],
  home   => '/Users/saltuser',
  password   => 'b876573f7c16c2e6ff541b7b41e4749daff39da335c76f0348ad8820aab8aa0ce1eb2e8b11c8b0fd801025e601832c3040a25ea1dc0cc532496919d8c601da71c4780d056a7c1fe0cc073ee70b1c9bead9282feaaa3dcdb8bd981150535f918b096adcdf258ef0f7b56379568e2ca53c98ce9cdd80dc8e8babb4a94132a6cdd7',
  salt   => 'ae4752864f88f934365109b5ac4e65cf1d0ac8a13b778e5e1a2354e54c320b31',
  shell  => '/bin/bash',
  uid=> '507',
}

Jira (PUP-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1977



  `puppet module build` should create `metadata.json` instead of `Modulefile` 










Change By:

 Michelle Johansen




Fix Version/s:

 3.5.1




Fix Version/s:

 3.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/d/optout.

Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1976



  `puppet module build` should use `metadata.json` as input format 










Change By:

 Michelle Johansen




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/d/optout.

Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1976



  `puppet module build` should use `metadata.json` as input format 










Change By:

 Michelle Johansen




Fix Version/s:

 3.5.1




Fix Version/s:

 3.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/d/optout.

Jira (PUP-1979) future parser Class reference with leading :: doesn't work

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: future parser Class reference with leading :: doesn't work 










merged to stable: dc41d16c95c009bfb05f5f5a5cf2ebe12cc0e966 merged to master: e427904ae286efce18118480f6f75636418c6fc5












   

 Add Comment











 













 Puppet /  PUP-1979



  future parser Class reference with leading :: doesn't work 







 If you have a class that does something like this:   {noformat}  class iptables {     class { '::iptables::packages': } ->     class { '::iptables::configs': } ->     class { '::iptables::update': } ->    class { '::iptables::services': } ->    Class['::iptables']  }  {noformat}   This works with current parser and avoid the need to use an explicit ...















 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/d/optout.

Jira (PUP-1751) PR (2383): Suse chkconfig --check boot. always returns 1 whether the service is enabled/disabled. - m4ce

2014-03-18 Thread Peter Huene (JIRA)

Title: Message Title










 

 Peter Huene updated an issue











 






 Puppet /  PUP-1751



  PR (2383): Suse chkconfig --check boot. always returns 1 whether the service is enabled/disabled. - m4ce 










Change By:

 Peter Huene




Issue Type:

 Task Bug












   

 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/d/optout.

Jira (PUP-748) PR (2067): Zypper provider install options - darix

2014-03-18 Thread Peter Huene (JIRA)

Title: Message Title










 

 Peter Huene updated an issue











 






 Puppet /  PUP-748



  PR (2067): Zypper provider install options - darix 










Change By:

 Peter Huene




Issue Type:

 Task Bug












   

 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/d/optout.

Jira (PUP-1981) Can't use :: in contain

Title: Message Title










 

 Daniele Sluijters commented on an issue











 






  Re: Can't use :: in contain 










I would prefer a solution that strips them. include and class are fine with ::, as is calling a defined type with :: and I'm betting it's also working for native types. It would get confusing if contain doesn't.












   

 Add Comment











 













 Puppet /  PUP-1981



  Can't use :: in contain 







 Works:  {noformat}  class test {    class { '::test::a': }    contain test::a     class test::a {  notice('a')    }  }  include ::test  {noformat}   Fails:  {noformat}  class test {    class { '::test::a': }    contain ::test::a       class test::a {  notice('a')    }  }  include ::test  {noformat}















 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/d/optout.

Jira (PUP-1981) Can't use :: in contain

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-1981



  Can't use :: in contain 










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/d/optout.

Jira (PUP-1981) Can't use :: in contain

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Can't use :: in contain 










This is probably related to PUP-1279 (same problem as in PUP-1279 even if that is for the future parser). The lookup basically does not handle class references starting with ::. The contain function should either just strip them (and document that references are absolute), or resolve them against the context it is in.












   

 Add Comment











 













 Puppet /  PUP-1981



  Can't use :: in contain 







 Works:  {noformat}  class test {    class { '::test::a': }    contain test::a     class test::a {  notice('a')    }  }  include ::test  {noformat}   Fails:  {noformat}  class test {    class { '::test::a': }    contain ::test::a       class test::a {  notice('a')    }  }  include ::test  {noformat}















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

Jira (PUP-1981) Can't use :: in contain

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-1981



  Can't use :: in contain 










Change By:

 Henrik Lindberg




Component/s:

 DSL












   

 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/d/optout.

Jira (PUP-1981) Can't use :: in contain

Title: Message Title










 

 Daniele Sluijters updated an issue











 






 Puppet /  PUP-1981



  Can't use :: in contain 










Change By:

 Daniele Sluijters









 Works:{noformat}class test {  class { '::test::a': }  contain test::a  class test::a {notice('a')  } }   include ::test } {noformat}Fails:{noformat}class test {  class { '::test::a': }  contain ::test::a   class test::a {notice('a')  } }   include ::test } {noformat}












   

 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/d/optout.

Jira (PUP-1981) Can't use :: in contain

Title: Message Title










 

 Daniele Sluijters updated an issue











 






 Puppet /  PUP-1981



  Can't use :: in contain 










Change By:

 Daniele Sluijters









 Works:{noformat}class test {  class { '::test::a': }  contain test::a  }  class test::a {notice('a')  }  include ::test}{noformat}Fails:{noformat}class test {  class { '::test::a': }  contain ::test::a   }   class test::a {notice('a')  }  include ::test}{noformat}












   

 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/d/optout.

Jira (PUP-1981) Can't use :: in contain

Title: Message Title










 

 Daniele Sluijters updated an issue











 






 Puppet /  PUP-1981



  Can't use :: in contain 










Change By:

 Daniele Sluijters









 Works:{noformat}class test {  class { '::test::a': }  contain test::a } class test::a {notice('a')  }include ::test } {noformat}Fails:{noformat}class test {  class { '::test::a': }  contain ::test::a  }  class test::a {notice('a')  }include ::test } {noformat}












   

 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/d/optout.

Jira (PUP-1981) Can't use :: in contain

Title: Message Title










 

 Daniele Sluijters updated an issue











 






 Puppet /  PUP-1981



  Can't use :: in contain 










Change By:

 Daniele Sluijters









 Works:{noformat}class test {  class { '::test::a': }contain test::a } class test::a {notice('a')  }include ::test{noformat}Fails:{noformat}class test {  class { '::test::a': }contain ::test::a  }  class test::a {notice('a')  }include ::test{noformat}












   

 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/d/optout.

Jira (PUP-1981) Can't use :: in contain

Title: Message Title










 

 Daniele Sluijters created an issue











 






 Puppet /  PUP-1981



  Can't use :: in contain 










Issue Type:

  Bug




Affects Versions:


 3.4.3




Assignee:

 Henrik Lindberg




Created:


 18/Mar/14 2:56 PM




Priority:

  Major




Reporter:

 Daniele Sluijters










Works:


class test {
  class { '::test::a': }
contain test::a
 }
 class test::a {
notice('a')
  }
include ::test



Fails:


class test {
  class { '::test::a': }
contain ::test::a
  }
  class test::a {
notice('a')
  }
include ::test















   

 Add Comment

Jira (PUP-1979) future parser Class reference with leading :: doesn't work

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-1979



  future parser Class reference with leading :: doesn't work 










Change By:

 Henrik Lindberg




Sprint:

 Week 2014-3-12 to 2014-3-19












   

 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/d/optout.

Jira (PUP-1603) puppet apply failure if puppet is upgraded

2014-03-18 Thread Dan Carley (JIRA)

Title: Message Title










 

 Dan Carley commented on an issue











 






  Re: puppet apply failure if puppet is upgraded 










This makes upgrading to >= 3.4 a bit of a pain. I've also seen it fail to backup files, although I can't reproduce it reliably. We're using the following hack to workaround it during our upgrade:
https://gist.github.com/dcarley/9630094












   

 Add Comment











 













 Puppet /  PUP-1603



  puppet apply failure if puppet is upgraded 







 I am testing an update from puppet 3.2.4 to 3.4.2 and I am receiving a failure that I have found in a few different places on the internet but that has no bug and no reproducer (for reference, I believe these are related links: https://groups.google.com/forum/#!topic/puppet-users/318TmfkO9Js and https://github.com/purpleidea/puppet-puppet/commit/8b7dae5ca...















 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 th

Jira (PUP-1979) future parser Class reference with leading :: doesn't work

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-1979



  future parser Class reference with leading :: doesn't work 










Change By:

 Henrik Lindberg




Component/s:

 DSL




Story Points:

 1




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/d/optout.

Jira (PUP-1979) future parser Class reference with leading :: doesn't work

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: future parser Class reference with leading :: doesn't work 










reproducible with:



class foo::f1 {
 notify { 'me first': }
}
class foo {
  class { 'foo::f1': } ->
  Class['::foo']
  notify { 'me last': }
}
include foo















   

 Add Comment











 













 Puppet /  PUP-1979



  future parser Class reference with leading :: doesn't work 







 If you have a class that does something like this:   {noformat}  class iptables {     class { '::iptables::packages': } ->     class { '::iptables::configs': } ->     class { '::iptables::update': } ->    class { '::iptables::services': } ->    Class['::iptables']  }  {noformat}   This works with current parser and avoid the need to use an explicit ...















 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 ema

Jira (PUP-1979) future parser Class reference with leading :: doesn't work

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-1979



  future parser Class reference with leading :: doesn't work 










Change By:

 Henrik Lindberg




Summary:

 future parser  class  Class  reference  inside class  with leading ::  doesn't work












   

 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/d/optout.

Jira (PUP-1979) future parser class reference inside class doesn't work

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-1979



  future parser class reference inside class doesn't work 










Change By:

 Henrik Lindberg




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/d/optout.

Jira (PDB-453) Update terminus to include environment information

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-453



  Update terminus to include environment information 










Change By:

 Kenneth Barber









 Terminus data submission should : - Include  include  environment in submitted  catalogs - Include environment in submitted  facts  , catalogs and reports.












   

 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/d/optout.

Jira (PUP-1975) Environment & transaction_uuid is not passed to facts indirector during compilation

Title: Message Title










 

 Kenneth Barber updated an issue











 






 Puppet /  PUP-1975



  Environment & transaction_uuid is not passed to facts indirector during compilation 










Change By:

 Kenneth Barber









 The class Puppet::Indirector::Catalog::Compiler contains a method 'extract_facts_from_request' which extracts facts from the request to be stored in a cache indirector. We utilise this This  call  as part of  is used in  the  flow for the  PuppetDB terminus to save facts.The problem however, is that the environment is not passed through to the indirector, which means we cannot preserve facts with the environment they were created from so we can complete PDB-453.I have a patch that remedies this, and it is forthcoming.[~eric.sorenson], [~andy] ... I'm not sure if this is strictly a bug or non-feature, what do you think? I simply ask because I'm not sure what branch/fix version to target this for.












   

 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/d/optout.

Jira (PUP-1978) future parser doesn't accept empty array as title

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-1978



  future parser doesn't accept empty array as title 










Change By:

 Henrik Lindberg




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/d/optout.

Jira (PUP-1980) Uppercase tags in exported resource

2014-03-18 Thread JIRA

Title: Message Title










 

 Frank Grötzner created an issue











 






 Puppet /  PUP-1980



  Uppercase tags in exported resource 










Issue Type:

  Bug




Affects Versions:


 3.4.3




Assignee:


 Unassigned




Created:


 18/Mar/14 12:38 PM




Environment:


Linux




Priority:

  Normal




Reporter:

 Frank Grötzner










Hi!
As already mentioned in this 4 years old bug https://projects.puppetlabs.com/issues/3045 (for some reason it's not possible to export it to Jira), it's still not possible to use tags with uppercase characters with exported resources.
You can test this easily by applying the following class to multiple nodes - if the tag contains uppercase characters, the exporting node will never realize it's own exported file.
class test {
 @@file { "/tmp/export-$ {fqdn}
":  content => 'a', tag => "tEst", }
 File <<| tag == "tEst" |>>
}

Jira (PUP-1973) future parser doesn't bind variables from inherited scope

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: future parser doesn't bind variables from inherited scope 










Also merged to master: eb09ae7dd2e7946796a27ab428f5c660459e368d












   

 Add Comment











 













 Puppet /  PUP-1973



  future parser doesn't bind variables from inherited scope 







 If you run the puppetlabs-ntp module with parser=future on 3.5.0-rc1 it will break complaining that it can't call {{flatten}} on {{nil:NilClass}} in the ntp.conf template.   This happens because for some reason {{@restrict}} and every other variable in the template isn't bound, ergo nil.   If I explicitly add a {{$restricted = $::ntp::restricted}} to co...















 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/d/optout.

Jira (PUP-1979) future parser class reference inside class doesn't work

Title: Message Title










 

 Daniele Sluijters updated an issue











 






 Puppet /  PUP-1979



  future parser class reference inside class doesn't work 










Change By:

 Daniele Sluijters









 If you have  a class that does something like this:{noformat}   class  iptables  {    class {  '::iptables::packages': } ->   class { '::iptables::configs': }  ->   class { '::iptables::update': }   ->  class { '::iptables::services': } ->  Class['::iptables'] } {noformat}This works with current parser and avoid the need to use an explicit anchor resource. However, future parser doesn't accept this and throws the following error:{noformat}Debug: Adding relationship from Class[Iptables::Configs] to Class[Iptables::Services] with 'before'Error: Could not find resource 'Class[::Iptables]' for relationship from 'Class[Iptables::Services]' on node super-secret-foo{noformat}












   

 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/d/optout.

Jira (PUP-1978) future parser doesn't accept empty array as title

Title: Message Title










 

 Daniele Sluijters updated an issue











 






 Puppet /  PUP-1978



  future parser doesn't accept empty array as title 










Change By:

 Daniele Sluijters




Priority:

 Major Normal












   

 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/d/optout.

Jira (PUP-1978) future parser doesn't accept empty array as title

Title: Message Title










 

 Daniele Sluijters commented on an issue











 






  Re: future parser doesn't accept empty array as title 










I was mostly hoping it would be possible for Puppet to tell me where this is being triggered from. Similar to evaluator a manifest/line or a 'calling resource' that triggered this.












   

 Add Comment











 













 Puppet /  PUP-1978



  future parser doesn't accept empty array as title 







 When passed an empty array the future parser ends up giving an unhelpful error message {{Error: Evaluation Error: Group[] accepts 1 argument. Got 0 on node super-secret-foo}}   {noformat}  /usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/runtime3_support.rb:19:in `fail'  /usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/access_operator.rb:443:in `access_PRe...















 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

Jira (PUP-1978) future parser doesn't accept empty array as title

Title: Message Title










 

 Daniele Sluijters updated an issue











 






 Puppet /  PUP-1978



  future parser doesn't accept empty array as title 










Change By:

 Daniele Sluijters









 When passed an empty array the future parser ends up giving an unhelpful error message {{Error: Evaluation Error: Group[] accepts 1 argument. Got 0 on node super-secret-foo}}{noformat}/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/runtime3_support.rb:19:in `fail'/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/access_operator.rb:443:in `access_PResourceType'/usr/lib/ruby/vendor_ruby/puppet/pops/visitor.rb:74:in `visit_this_2'/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/access_operator.rb:25:in `access'/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/evaluator_impl.rb:484:in `eval_AccessExpression'/usr/lib/ruby/vendor_ruby/puppet/pops/visitor.rb:64:in `visit_this_1'{noformat}The current parser accepts an empty array as an  regiment  argument  to Group (I have no idea what it does with it though , probably ignores it ).












   

 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/d/optout.

Jira (PUP-179) Puppet needs to delegate all fact loading to Facter

2014-03-18 Thread Eric Sorenson (JIRA)

Title: Message Title










 

 Eric Sorenson commented on an issue











 






  Re: Puppet needs to delegate all fact loading to Facter 










As noted in 

PUP-1570
, a fix for this should take into account the unreliability of facter's returning facts in a timely way.












   

 Add Comment











 













 Puppet /  PUP-179



  Puppet needs to delegate all fact loading to Facter 














 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/d/optout.

Jira (PUP-1570) Puppet Agent hanging on applying configuration

2014-03-18 Thread Eric Sorenson (JIRA)

Title: Message Title










 

 Eric Sorenson commented on an issue











 






  Re: Puppet Agent hanging on applying configuration 










I'm going to mark this closed/wontfix unless someone is experiencing the problem and can NOT trace it to network connections from facts.
I think the relevant issue and place to fix it is PUP-179, so I'm marking this related; please add yourself as a watcher there to see this through to resolution.












   

 Add Comment











 













 Puppet /  PUP-1570



  Puppet Agent hanging on applying configuration 







 Probably worth noting, I run a setup with a puppetmaster and the agents connecting to that to get their manifests.   My puppet agents get stuck applying configuration every once and awhile. For example:   root 769 0.0 2.8 42616 29292 ? S Jan16 0:02 puppet agent: applying configurat  root 28554 0.4 2.5 38244 25996 ? Ss...















 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 pu

Jira (FACT-185) No EC2 facts shown on newly-built Amazon Linux host

Title: Message Title










 

 Adrien Thebo updated an issue











 






 Facter /  FACT-185



  No EC2 facts shown on newly-built Amazon Linux host 










Change By:

 Adrien Thebo




Story Points:

 3












   

 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/d/optout.

Jira (PUP-1892) PR (2420) Puppet remote fileserver facility for file resources.

2014-03-18 Thread Roger Spencer (JIRA)

Title: Message Title










 

 Roger Spencer commented on an issue











 






  Re: PR (2420) Puppet remote fileserver facility for file resources. 










I've been banging my head on this bug for a few days until I realized the file_content was going to the wrong master.
If I downgrade the client to 2.7.22 the remote master file source works. Apparently anything 3.x doesn't work.












   

 Add Comment











 













 Puppet /  PUP-1892



  PR (2420) Puppet remote fileserver facility for file resources. 







 As of current release, due to the use of source_or_content.full_path, the hostname is stripped from attempts to handle file_content calls in type/file.rb. Because of this, it correctly calls file_metadata from the proper server, but then calls the puppetmaster instead of the remote fileserver for content retrieval, which fails.   This resolution might st...















 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 p

Jira (PDB-516) Store transaction_uuid with fact submission

Title: Message Title










 

 Kenneth Barber created an issue











 






 PuppetDB /  PDB-516



  Store transaction_uuid with fact submission 










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 18/Mar/14 11:08 AM




Priority:

  Normal




Reporter:

 Kenneth Barber










With PUP-1975 we discovered that environment and transaction_uuid was not being sent to the terminus. This FR covers the inclusion of transaction_uuid during fact submission so we can marry facts/catalogs/reports later on.












   

 Add Comment











 










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

Jira (PUP-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1977



  `puppet module build` should create `metadata.json` instead of `Modulefile` 










Change By:

 Michelle Johansen




Fix Version/s:

 3.6.0




Fix Version/s:

 3.5.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/d/optout.

Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1976



  `puppet module build` should use `metadata.json` as input format 










Change By:

 Michelle Johansen




Fix Version/s:

 3.6.0




Fix Version/s:

 3.5.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/d/optout.

Jira (PUP-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`

Title: Message Title










 

 Pieter van de Bruggen commented on an issue











 






  Re: `puppet module build` should create `metadata.json` instead of `Modulefile` 










Code for this can be found in https://github.com/puppetlabs/puppet/pull/2440.












   

 Add Comment











 













 Puppet /  PUP-1977



  `puppet module build` should create `metadata.json` instead of `Modulefile` 







 Since we're moving away from the {{Modulefile}} as the canonical source of metadata, we should do our users the favor of no longer generating a {{Modulefile}} – instead, we should generate the {{metadata.json}} file we expect them to use.















 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/d/optout.

Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1976



  `puppet module build` should use `metadata.json` as input format 










Change By:

 Michelle Johansen




Component/s:

 PE












   

 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/d/optout.

Jira (PUP-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1977



  `puppet module build` should create `metadata.json` instead of `Modulefile` 










Change By:

 Michelle Johansen




Component/s:

 PE












   

 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/d/optout.

Jira (PUP-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1977



  `puppet module build` should create `metadata.json` instead of `Modulefile` 










Change By:

 Michelle Johansen




Assignee:

 Pieter van de Bruggen












   

 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/d/optout.

Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format

Title: Message Title










 

 Pieter van de Bruggen commented on an issue











 






  Re: `puppet module build` should use `metadata.json` as input format 










Code can be found in https://github.com/puppetlabs/puppet/pull/2436.












   

 Add Comment











 













 Puppet /  PUP-1976



  `puppet module build` should use `metadata.json` as input format 







 `puppet module build`   This action is most impacted by this change though we will maintain compatibility with users still using Modulefile as their input format. Here's how that will work when a user initiates build.   - If the user provides a Modulefile at the root of their module, PMT will use it exclusively to build the release and issue a deprecati...















 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/d/optout.

Jira (PUP-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1977



  `puppet module build` should create `metadata.json` instead of `Modulefile` 










Change By:

 Michelle Johansen




Affects Version/s:

 3.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/d/optout.

Jira (PUP-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1977



  `puppet module build` should create `metadata.json` instead of `Modulefile` 










Change By:

 Michelle Johansen




Fix Version/s:

 3.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/d/optout.

Jira (PUP-1979) future parser class reference inside class doesn't work

Title: Message Title










 

 Daniele Sluijters created an issue











 






 Puppet /  PUP-1979



  future parser class reference inside class doesn't work 










Issue Type:

  Bug




Affects Versions:


 3.5.0 RC




Assignee:

 Henrik Lindberg




Created:


 18/Mar/14 10:56 AM




Priority:

  Normal




Reporter:

 Daniele Sluijters










If you have a class that does something like this:


   class { '::iptables::packages': } ->
   class { '::iptables::configs': }  ->
   class { '::iptables::update': }   ->
  class { '::iptables::services': } ->
  Class['::iptables']



This works with current parser and avoid the need to use an explicit anchor resource. However, future parser doesn't accept this and throws the following error:


Debug: Adding relationship from Class[Iptables::Configs] to Class[Iptables::Services] with 'before'
Error: Could not find resource 'Class[::Iptables]' for relationship from 'Class[Iptables::Services]' on node super-secret-foo

Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1976



  `puppet module build` should use `metadata.json` as input format 










Change By:

 Michelle Johansen




Fix Version/s:

 3.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/d/optout.

Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1976



  `puppet module build` should use `metadata.json` as input format 










Change By:

 Michelle Johansen




Affects Version/s:

 3.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/d/optout.

Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1976



  `puppet module build` should use `metadata.json` as input format 










Change By:

 Michelle Johansen




Assignee:

 Pieter van de Bruggen












   

 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/d/optout.

Jira (PUP-1975) Environment & transaction_uuid is not passed to facts indirector during compilation

Title: Message Title










 

 Kenneth Barber updated an issue











 






 Puppet /  PUP-1975



  Environment & transaction_uuid is not passed to facts indirector during compilation 










Change By:

 Kenneth Barber




Affects Version/s:

 3.5.0 RC




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/d/optout.

Jira (HI-225) allow interleaved querying of backends

2014-03-18 Thread Kjetil Torgrim Homme (JIRA)

Title: Message Title










 

 Kjetil Torgrim Homme commented on an issue











 






  Re: allow interleaved querying of backends 










as indicated by Time Tracking, I have a patch ready, but I haven't updated the rspec tests yet. will add pull request when tests pass again 












   

 Add Comment











 













 Hiera /  HI-225



  allow interleaved querying of backends 







 When Hiera processes the sources, it will iterate through them completely, first with the first backend, then the next backend.   Given a hiera.yaml like     :hierarchy:  - site-%{::site}  - common    :backends:  - yaml  - json   and the files site-external.json and common.yaml, the value in common.yaml will override the value in site-e...















 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/d/optout.

Jira (PUP-1978) future parser doesn't accept empty array as title

Title: Message Title










 

 Daniele Sluijters created an issue











 






 Puppet /  PUP-1978



  future parser doesn't accept empty array as title 










Issue Type:

  Bug




Affects Versions:


 3.5.0 RC




Assignee:

 Henrik Lindberg




Created:


 18/Mar/14 10:41 AM




Priority:

  Major




Reporter:

 Daniele Sluijters










When passed an empty array the future parser ends up giving an unhelpful error message Error: Evaluation Error: Group[] accepts 1 argument. Got 0 on node super-secret-foo


/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/runtime3_support.rb:19:in `fail'
/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/access_operator.rb:443:in `access_PResourceType'
/usr/lib/ruby/vendor_ruby/puppet/pops/visitor.rb:74:in `visit_this_2'
/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/access_operator.rb:25:in `access'
/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/evaluator_impl.rb:484:in `eval_AccessExpression'
/usr/lib/ruby/vendor_ruby/puppet/pops/visitor.rb:64:in `visit_this_1'



The current parser accepts an empty array as an regiment to Group (I have no idea what it does with it though).

Jira (PUP-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`

Title: Message Title










 

 Pieter van de Bruggen created an issue











 






 Puppet /  PUP-1977



  `puppet module build` should create `metadata.json` instead of `Modulefile` 










Issue Type:

  Improvement




Affects Versions:


 3.6.0




Assignee:

 Pieter van de Bruggen




Created:


 18/Mar/14 10:40 AM




Priority:

  Normal




Reporter:

 Pieter van de Bruggen










Since we're moving away from the Modulefile as the canonical source of metadata, we should do our users the favor of no longer generating a Modulefile – instead, we should generate the metadata.json file we expect them to use.












   

 Add Comment











 










 This message w

Jira (PUP-1624) PR (2342) Cron handles crontab's equality of target and user strangely

2014-03-18 Thread Charlie Sharpsteen (JIRA)

Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: PR (2342) Cron handles crontab's equality of target and user strangely 










Thanks for looking into this Tony!
I think the real heart of this issue is that the "user" and "target" properties are redundant. Both properties try to manage which crontab a job gets written into. Given the redundancy, users shouldn't be setting both "user" and "target" on a single job and definitely shouldn't be setting them to different values — we need to update the docs to make this clear. I've created DOCUMENT-53 to track this task.
I think this patch still resolves the main symptom: setting "target" alone was buggy and caused the resource to "loop" or "flicker".












   

 Add Comment











 













 Puppet /  PUP-1624



  PR (2342) Cron handles crontab's equality of target and user strangely 







 When managing the target property of a cronjob, the user property uses its default instead (which is the user running puppet). To the crontab provider, these are basically the same, and there is code to handle them equally. Through the mixtures of defaults and actual supplied values, though, bizarre behaviors come up:   {code}  # HEADER: This file was au...















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

Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format

Title: Message Title










 

 Pieter van de Bruggen created an issue











 






 Puppet /  PUP-1976



  `puppet module build` should use `metadata.json` as input format 










Issue Type:

  Improvement




Affects Versions:


 3.6.0




Assignee:

 Pieter van de Bruggen




Created:


 18/Mar/14 10:37 AM




Priority:

  Normal




Reporter:

 Pieter van de Bruggen










`puppet module build`
This action is most impacted by this change though we will maintain compatibility with users still using Modulefile as their input format. Here's how that will work when a user initiates build.


If the user provides a Modulefile at the root of their module, PMT will use it exclusively to build the release and issue a deprecation warning. Let's call this the legacy build process.


If the user provides a metadata.json file at the root of their module, PMT will use it exclusively to build the release. Let's call this the v3 build process.


If the user providers both a Modulefile and metadata.json, PMT will use the v3 build process, ignoring the Modulefile but issuing a warning against including both files in the module root. The legacy build process will issue a deprecation warning but will otherwise behave as it does today.

Jira (PUP-1975) Environment & transaction_uuid is not passed to facts indirector during compilation

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Environment & transaction_uuid is not passed to facts indirector during compilation 










After talking to Andy Parker we've decided to extend this to transaction_uuid also, since the information may be useful later on when we start doing more intelligent data marriage between facts/catalogs/reports in PuppetDB.












   

 Add Comment











 













 Puppet /  PUP-1975



  Environment & transaction_uuid is not passed to facts indirector during compilation 







 The class Puppet::Indirector::Catalog::Compiler contains a method 'extract_facts_from_request' which extracts facts from the request to be stored in a cache indirector.   We utilise this call as part of the PuppetDB terminus to save facts.   The problem however, is that the environment is not passed through to the indirector, which means we cannot prese...















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

Jira (PUP-1973) future parser doesn't bind variables from inherited scope

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-1973



  future parser doesn't bind variables from inherited scope 










Change By:

 Henrik Lindberg




Sprint:

 Week 2014-3-12 to 2014-3-19












   

 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/d/optout.

Jira (PUP-1973) future parser doesn't bind variables from inherited scope

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-1973



  future parser doesn't bind variables from inherited scope 










Change By:

 Henrik Lindberg




Component/s:

 DSL




Story Points:

 1




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/d/optout.

Jira (PUP-1975) Environment & transaction_uuid is not passed to facts indirector during compilation

Title: Message Title










 

 Kenneth Barber updated an issue











 






 Puppet /  PUP-1975



  Environment & transaction_uuid is not passed to facts indirector during compilation 










Change By:

 Kenneth Barber




Summary:

 Environment  & transaction_uuid  is not passed to facts indirector during compilation












   

 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/d/optout.

Jira (PUP-1973) future parser doesn't bind variables from inherited scope

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-1973



  future parser doesn't bind variables from inherited scope 










Change By:

 Henrik Lindberg




Summary:

 futurepaser future parser  doesn't bind variables  in templates correctly  from inherited scope












   

 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/d/optout.

Jira (PUP-1973) futurepaser doesn't bind variables in templates correctly

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: futurepaser doesn't bind variables in templates correctly 












PUP-1220
 accidentally turns off access to inherited scope (as a consequence of turning off dynamic scope).












   

 Add Comment











 













 Puppet /  PUP-1973



  futurepaser doesn't bind variables in templates correctly 







 If you run the puppetlabs-ntp module with parser=future on 3.5.0-rc1 it will break complaining that it can't call {{flatten}} on {{nil:NilClass}} in the ntp.conf template.   This happens because for some reason {{@restrict}} and every other variable in the template isn't bound, ergo nil.   If I explicitly add a {{$restricted = $::ntp::restricted}} to co...















 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 thi

Jira (HI-175) PR (176): (CPR-12) Ensure hiera works with alternatives on debian - haus

Title: Message Title










 

 Adrien Thebo assigned an issue to Unassigned











 






 Hiera /  HI-175



  PR (176): (CPR-12) Ensure hiera works with alternatives on debian - haus 










Change By:

 Adrien Thebo




Assignee:

 Adrien Thebo












   

 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/d/optout.

Jira (HI-174) PR (175): (CPR-12) Ensure hiera works with alternatives on debian - haus

Title: Message Title










 

 Adrien Thebo assigned an issue to Unassigned











 






 Hiera /  HI-174



  PR (175): (CPR-12) Ensure hiera works with alternatives on debian - haus 










Change By:

 Adrien Thebo




Assignee:

 Adrien Thebo












   

 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/d/optout.

Jira (HI-225) allow interleaved querying of backends

Title: Message Title










 

 Adrien Thebo updated an issue











 






 Hiera /  HI-225



  allow interleaved querying of backends 










Change By:

 Adrien Thebo




Assignee:

 Adrien Thebo












   

 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/d/optout.

Jira (HI-225) allow interleaved querying of backends

Title: Message Title










 

 Adrien Thebo updated an issue











 






 Hiera /  HI-225



  allow interleaved querying of backends 










Change By:

 Adrien Thebo




Component/s:

 Community












   

 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/d/optout.

Jira (PUP-1975) Environment is not passed to facts indirector during compilation

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Environment is not passed to facts indirector during compilation 










PR is here: https://github.com/puppetlabs/puppet/pull/2444












   

 Add Comment











 













 Puppet /  PUP-1975



  Environment is not passed to facts indirector during compilation 







 The class Puppet::Indirector::Catalog::Compiler contains a method 'extract_facts_from_request' which extracts facts from the request to be stored in a cache indirector.   We utilise this call as part of the PuppetDB terminus to save facts.   The problem however, is that the environment is not passed through to the indirector, which means we cannot prese...















 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/d/optout.

Jira (PUP-1975) Environment is not passed to facts indirector during compilation