date:20140226

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: (PR 2012) Add install_options to gem provider 










mmoghadas commented:
I have not. I will probably do so next week.
On Wed, Feb 26, 2014 at 10:05 AM, Josh Cooper wrote:
> Hi @mmoghadas  have you had a chance to > look into this? > > – > Reply to this email directly or view it on GitHub > . >












   

 Add Comment











 













 Puppet /  PUP-620



  (PR 2012) Add install_options to gem provider 







 h2. added install_options to gem provider. now you can do... install_options...   * Author: Mike   * Company:   * Github ID: [mmoghadas|https://github.com/mmoghadas]  * [Pull Request 2012 Discussion|https://github.com/puppetlabs/puppet/pull/2012]  * [Pull Request 2012 File Diff|https://github.com/puppetlabs/puppet/pull/2012/files...















 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.

Jira (PDB-476) Convert the terminus performance logging one-off support solution to something permanent

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Convert the terminus performance logging one-off support solution to something permanent 










Example of the profiling debug output is here: https://gist.github.com/kbarber/9243889












   

 Add Comment











 













 PuppetDB /  PDB-476



  Convert the terminus performance logging one-off support solution to something permanent 







 To help diagnose some potential performance issues with the PuppetDB terminus (PE-2889), I instrumented a bunch of different operations done by the PuppetDB terminus here: https://github.com/senior/puppetdb/commit/133a76de04b709515af6dcb4759ad880ecec3d77. We should make that permanent via similar changes in master.   It seems like there is a lot of over...















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

Jira (PDB-476) Convert the terminus performance logging one-off support solution to something permanent

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Convert the terminus performance logging one-off support solution to something permanent 










PR is here: https://github.com/puppetlabs/puppetdb/pull/872












   

 Add Comment











 













 PuppetDB /  PDB-476



  Convert the terminus performance logging one-off support solution to something permanent 







 To help diagnose some potential performance issues with the PuppetDB terminus (PE-2889), I instrumented a bunch of different operations done by the PuppetDB terminus here: https://github.com/senior/puppetdb/commit/133a76de04b709515af6dcb4759ad880ecec3d77. We should make that permanent via similar changes in master.   It seems like there is a lot of over...















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




 














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

Jira (PUP-1781) PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo 










adrienthebo commented:
Blagh, fixed. I hope.












   

 Add Comment











 













 Puppet /  PUP-1781



  PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo 







 h2. Issue/master/pup 876 redhat 6 upstart   * Author: Adrien Thebo git...@somethingsinistral.net>  * Company: Puppet Labs  * Github ID: [adrienthebo|https://github.com/adrienthebo]  * [Pull Request 2392 Discussion|https://github.com/puppetlabs/puppet/pull/2392]  * [Pull Request 2392 File Diff|https://github.com/puppetlabs/puppet/pull/2392/files]  h2















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




 














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

Jira (PUP-1584) Puppet module tool should work with new directory environments

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Puppet module tool should work with new directory environments 










I believe that --force just forces the installation into the current environment regardless of previous installation or conflicts. Since saz/ntp had not yet been installed in --envirionment direnv, it was installed there. If you repeated the command to install without --force, it should raise an error, with --force it should reinstall. But you might want to double check with someone on the forge team.












   

 Add Comment











 













 Puppet /  PUP-1584



  Puppet module tool should work with new directory environments 







 Given two environments, a legacy environment 'legacyenv' defined in puppet.conf and a 'direnv' directory in the established $environmentdir, `puppet module install --environment ` will respect the legacy environment but not the directory environment. This probably needs to be fixed for all the module functions, but I haven't tested everything yet.















 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 re

Jira (FACT-239) Expose different resolution types in DSL

Title: Message Title










 

 Joshua Cooper assigned an issue to Unassigned











 






 Facter /  FACT-239



  Expose different resolution types in DSL 










Change By:

 Joshua Cooper




Assignee:

 Joshua Cooper












   

 Add Comment











 










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




 














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

Jira (PUP-1781) PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 Puppet /  PUP-1781



  PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo 







 h2. Issue/master/pup 876 redhat 6 upstart   * Author: Adrien Thebo git...@somethingsinistral.net>  * Company: Puppet Labs  * Github ID: [adrienthebo|https://github.com/adrienthebo]  * [Pull Request 2392 Discussion|https://github.com/puppetlabs/puppet/pull/2392]  * [Pull Request 2392 File Diff|https://github.com/puppetlabs/puppet/pull/2392/files]  h2















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




 














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

Jira (PUP-1781) PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo 










kylog commented:
@adrienthebo ping that travis failed.












   

 Add Comment











 













 Puppet /  PUP-1781



  PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo 







 h2. Issue/master/pup 876 redhat 6 upstart   * Author: Adrien Thebo git...@somethingsinistral.net>  * Company: Puppet Labs  * Github ID: [adrienthebo|https://github.com/adrienthebo]  * [Pull Request 2392 Discussion|https://github.com/puppetlabs/puppet/pull/2392]  * [Pull Request 2392 File Diff|https://github.com/puppetlabs/puppet/pull/2392/files]  h2















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




 














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

Jira (PUP-1336) The puppet master should automatically re-parse hiera_config if the file is changed

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1336



  The puppet master should automatically re-parse hiera_config if the file is changed 










So. The current config re-parsing scheme specifically only deals with the puppet.conf file and is implemented in settings.rb. The parse_config_files method called therein is limited to dealing with Puppet settings that come out of puppet.conf.
Hiera settings are loaded inside of the Hiera terminus for the data_binding indirection. In order to implement this feature, that code would have to be extended to watch the Hiera config file and re-generate the Hiera object when the config file changes.










Change By:

 Charlie Sharpsteen




Issue Type:

 Bug New Feature




Summary:

 FWIW, puppetmaster doesn't notice changes to /etc/ The puppet /hiera.yaml  master should automatically re-parse hiera_config if the file is changed












   

 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

Jira (PUP-1336) The puppet master should automatically re-parse hiera_config if the file is changed

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1336



  The puppet master should automatically re-parse hiera_config if the file is changed 










Change By:

 Charlie Sharpsteen




Assignee:

 Charlie Sharpsteen












   

 Add Comment











 










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




 














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

Jira (FACT-239) Expose different resolution types in DSL

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Expose different resolution types in DSL 










Facter doesn't gracefully handle mixing chunk datatypes.



$ cat lib/facter/mismatch.rb
Facter.add("mismatch", :type => :aggregate) do
  chunk(:one) do
['one']
  end
  chunk(:two) do
{'two'}
  end
end
$ be facter mismatch
Error loading fact /Users/josh/work/facter/lib/facter/mismatch.rb /Users/josh/work/facter/lib/facter/mismatch.rb:6: syntax error, unexpected '}', expecting tASSOC
Error loading fact /Users/josh/work/facter/lib/facter/mismatch.rb /Users/josh/work/facter/lib/facter/mismatch.rb:6: syntax error, unexpected '}', expecting tASSOC















   

 Add Comment











 













 Facter /  FACT-239



  Expose different resolution types in DSL 







 Adding multiple resolution types to Facter means that the DSL will have to take this into account. The DSL needs to take the following into account:   Resolutions need to be able to declare their type upon creation. This should just be a simple matter of taking :type => :something when the resolution is initially created.   Resolutions may also need to...















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

Jira (FACT-239) Expose different resolution types in DSL

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Expose different resolution types in DSL 










Think we should mention that aggregate fact chunks need to return aggregate-able data. For example, if each chunk returns a string, I get an error:



$ cat lib/facter/reopened_aggregate.rb
Facter.add("reopened_aggregate", :type => :aggregate) do
  chunk(:one) do
'one'
  end
  chunk(:two) do
'two'
  end
end
$ be facter reopened_aggregate
Could not retrieve fact='reopened_aggregate', resolution='': No aggregate block specified and could not deep merge all chunks, either specify an aggregate block or ensure that all chunks return deep mergable structures. (Original error: Cannot merge "one":String and "two":String)



If I change the return values to ['one'] and ['two'], then they are merged as expected.












   

 Add Comment











 













 Facter /  FACT-239



  Expose different resolution types in DSL 







 Adding multiple resolution types to Facter means that the DSL will have to take this into account. The DSL needs to take the following into account:   Resolutions need to be able to declare their type upon creation. This should just be a simple matter of taking :type => :something when the resolution is initially created.   Resolutions may also need to...















 This message was sent by Atlassian JIRA (v6.1.4#6159-s

Jira (FACT-239) Expose different resolution types in DSL

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Expose different resolution types in DSL 










Should facter raise an error when using setcode with an aggregate fact?



$ cat lib/facter/reopened_aggregate.rb
Facter.add("reopened_aggregate", :type => :aggregate) do
  setcode do
'one'
  end
end

Facter.add("reopened_aggregate", :type => :aggregate) do
  setcode do
'two'
  end
end
$ be facter reopened_aggregate
Unable to add resolve nil for fact reopened_aggregate: undefined method `setcode' for #
Unable to add resolve nil for fact reopened_aggregate: undefined method `setcode' for #















   

 Add Comment











 













 Facter /  FACT-239



  Expose different resolution types in DSL 







 Adding multiple resolution types to Facter means that the DSL will have to take this into account. The DSL needs to take the following into account:   Resolutions need to be able to declare their type upon creation. This should just be a simple matter of taking :type => :something when the resolution is initially created.   Resolutions may also need to...















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

Jira (FACT-239) Expose different resolution types in DSL

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Expose different resolution types in DSL 










Should this raise an error?



$ cat lib/facter/reopened.rb
Facter.add("reopened", :type => :simple) do
  setcode do
'one'
  end
end

Facter.add("reopened", :type => :simple) do
  setcode do
'two'
  end
end
$ be facter reopened
one



Should this be an error? Or will facter always pick the first resolution in parse order?












   

 Add Comment











 













 Facter /  FACT-239



  Expose different resolution types in DSL 







 Adding multiple resolution types to Facter means that the DSL will have to take this into account. The DSL needs to take the following into account:   Resolutions need to be able to declare their type upon creation. This should just be a simple matter of taking :type => :something when the resolution is initially created.   Resolutions may also need to...















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

Jira (PDB-280) Measure PuppetDB AWS costs by integrating it fully into Cloudability

2014-02-26 Thread Deepak Giridharagopal (JIRA)

Title: Message Title










 

 Deepak Giridharagopal updated an issue











 






 PuppetDB /  PDB-280



  Measure PuppetDB AWS costs by integrating it fully into Cloudability 










Change By:

 Deepak Giridharagopal




Epic Status:

 To Do Done












   

 Add Comment











 










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




 














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

Jira (FACT-351) undefined method 'ipaddress' for Facter:Module

Title: Message Title










 

 Joshua Cooper created an issue











 






 Facter /  FACT-351



  undefined method 'ipaddress' for Facter:Module 










Issue Type:

  Bug




Assignee:

 Adrien Thebo




Created:


 26/Feb/14 5:33 PM




Priority:

  Normal




Reporter:

 Joshua Cooper










On facter-2, Darwin:



bundle exec facter
Could not retrieve fact='netmask', resolution='': undefined method `ipaddress' for Facter:Module
...



I think this is due to some facts still using setcode without a block, but I may be confusing this with a different issue.












   

 Add Comment











 










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

Jira (PDB-6) New capability for PE 3.2

2014-02-26 Thread Deepak Giridharagopal (JIRA)

Title: Message Title










 

 Deepak Giridharagopal updated an issue











 






 PuppetDB /  PDB-6



  New capability for PE 3.2 










Change By:

 Deepak Giridharagopal




Epic Status:

 To Do Done












   

 Add Comment











 










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




 














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

Jira (PUP-1584) Puppet module tool should work with new directory environments

2014-02-26 Thread Tony Vu (JIRA)

Title: Message Title










 

 Tony Vu commented on an issue











 






  Re: Puppet module tool should work with new directory environments 










Testing has looked good so far, there is one test scenario that I tried that did not meet my expectations. Is my expectation correct in this situation?
Steps:
1. Create an "environments/direnv/modules' in your puppet installation folder 2. Execute 'puppet module install saz/ntp' ==> this should put the module in /etc/puppet/modules 3. Execute 'puppet module install saz/ntp --environment direnv --force'
Expectation: The module should be reinstalled in /etc/puppet/modules
Result: The module is installed in the /etc/puppet/environments/direnv/modules.












   

 Add Comment











 













 Puppet /  PUP-1584



  Puppet module tool should work with new directory environments 







 Given two environments, a legacy environment 'legacyenv' defined in puppet.conf and a 'direnv' directory in the established $environmentdir, `puppet module install --environment ` will respect the legacy environment but not the directory environment. This probably needs to be fixed for all the module functions, but I haven't tested everything yet.















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

Jira (PUP-473) Add support for \u for unicode chars in strings

Title: Message Title










 

 Joshua Partlow updated an issue











 






 Puppet /  PUP-473



  Add support for \u for unicode chars in strings 










Change By:

 Joshua Partlow




Fix Version/s:

 4.0.0




Fix Version/s:

 3.5.0












   

 Add Comment











 










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




 














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

Jira (PDB-231) Add Postgres disk space full warnings

2014-02-26 Thread Nick Walker (JIRA)

Title: Message Title










 

 Nick Walker commented on an issue











 






  Re: Add Postgres disk space full warnings 










I'm linking this ticket to PE-1662 because I'm not sure what the solution in puppetdb vs the console is going to be but potentially either side could use insight into how the other side solved the problem. 












   

 Add Comment











 













 PuppetDB /  PDB-231



  Add Postgres disk space full warnings 







 We've had several support issues where the user's Postgres database ran out of space. It would be nice to have some process in place that we could notify/log potential disk space issues as recovering from this issue once the disk has filled is painful.















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




 














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

Jira (HI-203) Hiera 1.3.2 Release -- Feb. 27, 2014

2014-02-26 Thread Melissa Stone (JIRA)

Title: Message Title










 

 Melissa Stone updated an issue











 






 Hiera /  HI-203



  Hiera 1.3.2 Release -- Feb. 27, 2014 










Change By:

 Melissa Stone




Fix Version/s:

 1.3.2












   

 Add Comment











 










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




 














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

Jira (PUP-1782) Deprecation warning when attempt to match a number with a regexp in 3.x

Title: Message Title










 

 Joshua Partlow created an issue











 






 Puppet /  PUP-1782



  Deprecation warning when attempt to match a number with a regexp in 3.x 










Issue Type:

  Improvement




Assignee:

 Andrew Parker




Components:


 DSL




Created:


 26/Feb/14 4:53 PM




Fix Versions:


 3.6.0




Priority:

  Normal




Reporter:

 Joshua Partlow












PUP-483
 describes how this is being handled in the future parser. We should issue a deprecation warning a =~ or !~ is performed with an LHS that is numeric in 3.x.












   

 Add Comment

Jira (PUP-483) Handle Match in useful and consistent way

Title: Message Title










 

 Joshua Partlow updated an issue











 






 Puppet /  PUP-483



  Handle Match in useful and consistent way 










Change By:

 Joshua Partlow




Fix Version/s:

 4.0.0




Fix Version/s:

 3.5.0












   

 Add Comment











 










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




 














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

Jira (HI-211) Smoke test packages

Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: Smoke test packages 










Everything looks good on CentOS 6.5 as well:


[root@muninn ~]# yum install -y puppetlabs-release-el-6.noarch.rpm

...

Complete!

[root@muninn ~]# yum install -y hiera-1.3.2-1.el6.noarch.rpm

...

Running Transaction
  Installing : compat-readline5-5.2-17.1.el6.x86_64   1/8
  Installing : ruby-libs-1.8.7.352-13.el6.x86_64  2/8
  Installing : ruby-1.8.7.352-13.el6.x86_64   3/8
  Installing : ruby-irb-1.8.7.352-13.el6.x86_64   4/8
  Installing : ruby-rdoc-1.8.7.352-13.el6.x86_64  5/8
  Installing : rubygems-1.3.7-5.el6.noarch6/8
  Installing : rubygem-json-1.5.5-1.el6.x86_647/8
  Installing : hiera-1.3.2-1.el6.noarch   8/8
  Verifying  : ruby-irb-1.8.7.352-13.el6.x86_64   1/8
  Verifying  : ruby-1.8.7.352-13.el6.x86_64   2/8
  Verifying  : compat-readline5-5.2-17.1.el6.x86_64   3/8
  Verifying  : ruby-rdoc-1.8.7.352-13.el6.x86_64  4/8
  Verifying  : rubygems-1.3.7-5.el6.noarch5/8
  Verifying  : ruby-libs-1.8.7.352-13.el6.x86_64  6/8
  Verifying  : rubygem-json-1.5.5-1.el6.x86_647/8
  Verifying  : hiera-1.3.2-1.el6.noarch   8/8

Installed:
  hiera.noarch 0:1.3.2-1.el6

Dependency Installed:
  compat-readline5.x86_64 0:5.2-17.1.el6   ruby.x86_64 0:1.8.7.352-13.el6  ruby-irb.x86_64 0:1.8.7.352-13.el6   ruby-libs.x86_64 0:1.8.7.352-13.el6
  ruby-rdoc.x86_64 0:1.8.7.352-13.el6  rubygem-json.x86_64 0:1.5.5-1.el6   rubygems.noarch 0:1.3.7-5.el6

Complete!


[root@muninn ~]# hiera --version
1.3.2


[root@muninn ~]# vim /var/lib/hiera/global.json   # <--- define key foo
[root@muninn ~]# vim /var/lib/hiera/defaults.yaml # <--- define key baz
[root@muninn ~]# vim /etc/hiera.yaml  # <--- activate JSON backend

[root@muninn ~]# hiera foo
bar
[root@muninn ~]# hiera baz
bim

Jira (PUP-482) Handle Comparisons / Equality a consistent way

Title: Message Title










 

 Joshua Partlow updated an issue











 






 Puppet /  PUP-482



  Handle Comparisons / Equality a consistent way 










Change By:

 Joshua Partlow




Fix Version/s:

 4.0.0




Fix Version/s:

 3.5.0












   

 Add Comment











 










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




 














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

Jira (HI-211) Smoke test packages

Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: Smoke test packages 










JSON and YAML lookups pass after installation on Ubuntu 12.04:


root@huginn:~# dpkg -i hiera_1.3.2-1puppetlabs1_all.deb

Selecting previously unselected package hiera.
(Reading database ... 53994 files and directories currently installed.)
Unpacking hiera (from hiera_1.3.2-1puppetlabs1_all.deb) ...
dpkg: dependency problems prevent configuration of hiera:
 hiera depends on ruby | ruby-interpreter; however:
  Package ruby is not installed.
  Package ruby-interpreter is not installed.
 hiera depends on libjson-ruby | ruby-json; however:
  Package libjson-ruby is not installed.
  Package ruby-json is not installed.
dpkg: error processing hiera (--install):
 dependency problems - leaving unconfigured
Processing triggers for man-db ...
Errors were encountered while processing:
 hiera

root@huginn:~# which hiera
/usr/bin/hiera

root@huginn:~# apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
  libjson-ruby libruby1.8 ruby ruby-json ruby1.8
Suggested packages:
  ri ruby-dev ruby1.8-examples ri1.8
The following NEW packages will be installed:
  libjson-ruby libruby1.8 ruby ruby-json ruby1.8
0 upgraded, 5 newly installed, 0 to remove and 119 not upgraded.
1 not fully installed or removed.
Need to get 1,911 kB of archives.
After this operation, 7,069 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main libruby1.8 amd64 1.8.7.352-2ubuntu1.4 [1,797 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main ruby1.8 amd64 1.8.7.352-2ubuntu1.4 [33.8 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu/ precise/main ruby all 4.8 [5,054 B]
Get:4 http://us.archive.ubuntu.com/ubuntu/ precise/universe ruby-json amd64 1.6.3-1 [73.3 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu/ precise/universe libjson-ruby all 1.6.3-1 [1,588 B]
Fetched 1,911 kB in 4s (435 kB/s)
Selecting previously unselected package libruby1.8.
(Reading database ... 54019 files and directories currently installed.)
Unpacking libruby1.8 (from .../libruby1.8_1.8.7.352-2ubuntu1.4_amd64.deb) ...
Selecting previously unselected package ruby1.8.
Unpacking ruby1.8 (from .../ruby1.8_1.8.7.352-2ubuntu1.4_amd64.deb) ...
Selecting previously unselected package ruby.
Unpacking ruby (from .../apt/archives/ruby_4.8_all.deb) ...
Selecting previously unselected package ruby-json.
Unpacking ruby-json (from .../ruby-json_1.6.3-1_amd64.deb) ...
Selecting previously unselected package libjson-ruby.
Unpacking libjson-ruby (from .../libjson-ruby_1.6.3-1_all.deb) ...
Processing triggers for man-db ...
Setting up libruby1.8 (1.8.7.352-2ubuntu1.4) ...
Setting up ruby1.8 (1.8.7.352-2ubuntu1.4) ...
update-alternatives: using /usr/bin/ruby1.8 to provide /usr/bin/ruby (ruby) in auto mode.
Setting up ruby (4.8) ...
Setting up ruby-json (1.6.3-1) ...
Setting up libjson-ruby (1.6.3-1) ...
Setting up hiera (1.3.2-1puppetlabs1) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place


root@huginn:~# hiera --version
1.3.2


root@huginn:~# vim /var/lib/hiera/global.json  # <--- define key foo
root@huginn:~# vim /var/lib/hiera/defaults.yaml  # <--- define key baz
root@huginn:~# vim /etc/hiera.yaml# <--- activate JSON backend

root@huginn:~# hiera foo
bar
root@huginn:~# hiera baz
bim

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

Title: Message Title










 

 Joshua Partlow commented on an issue











 






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










Henrik and I feel that these should be issuing errors. That will mean deprecation warnings in 3.6 for cases where it currently falls through silently, and the new Catalog Builder will need to raise errors when these cases are encountered.












   

 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 and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs

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

Title: Message Title










 

 Joshua Partlow updated an issue











 






 Puppet /  PUP-996



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










Change By:

 Joshua Partlow




Fix Version/s:

 4.0.0




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/groups/opt_out.

Jira (PUP-1042) Puppet apply runmode should write classes.txt file

2014-02-26 Thread Michelle Johansen (JIRA)

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1042



  Puppet apply runmode should write classes.txt file 










Change By:

 Michelle Johansen




Sprint:

 Week 2014-1-22 to 2014-1-29, Week 2014-1-29 to 2014-2-05, Week 2014-2-5 to 2014-2-12, Week 2014-2-19 to 2014-2-26 , Week 2014-2-26 to 2014-3-5












   

 Add Comment











 










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




 














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

Jira (PUP-1564) package rpm provider should support :uninstall_options feature

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1564



  package rpm provider should support :uninstall_options feature 










Change By:

 Charlie Sharpsteen




Sprint:

 Week 2014-2-26 to 2014-3-5












   

 Add Comment











 










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




 














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

Jira (HI-203) Hiera 1.3.2 Release -- Feb. 27, 2014

2014-02-26 Thread Melissa Stone (JIRA)

Title: Message Title










 

 Melissa Stone updated an issue











 






 Hiera /  HI-203



  Hiera 1.3.2 Release -- Feb. 27, 2014 










Change By:

 Melissa Stone




Summary:

 Hiera 1.3.2 Release  -- Feb. 27, 2014












   

 Add Comment











 










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




 














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

Jira (PUP-1564) package rpm provider should support :uninstall_options feature

Title: Message Title










 

 Charlie Sharpsteen assigned an issue to Charlie Sharpsteen











 






 Puppet /  PUP-1564



  package rpm provider should support :uninstall_options feature 










Change By:

 Charlie Sharpsteen




Assignee:

 Charlie Sharpsteen












   

 Add Comment











 










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




 














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

Jira (PUP-1779) "puppet node clean" is hard-coded to use rails/activerecord backend

2014-02-26 Thread redmine.exporter (JIRA)

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1779



  "puppet node clean" is hard-coded to use rails/activerecord backend 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 26/Feb/14 1:52 PM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










See #14721.
PuppetDB already has code to remove a node's data ("puppet node deactivate"), but we can't get it to seamlessly work with "puppet node clean" as long as it's hard-coded to assume legacy storeconfigs. This face should use some manner of indirection to allow other storeconfigs backends to participate in node cleanup.












   

 Add Comment

Jira (PUP-979) future parser fails to recognize hash as parameter in un-parenthesized calls

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-979



  future parser fails to recognize hash as parameter in un-parenthesized calls 










Change By:

 Andrew Parker




Story Points:

 2 5












   

 Add Comment











 










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




 














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

Jira (PDB-93) duplicate resource collections during catalog compilation

2014-02-26 Thread Branan Purvine-Riley (JIRA)

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: duplicate resource collections during catalog compilation 










I've been able to reproduce and somewhat control this with the following manifest:


define sum_series($counter = 0) {
 
  $newcounter = $counter + $title
  if $title == 1 {
notify { "${newcounter}": }
  }
  else {
$dec = $title - 1
$hash = {
  "${dec}"=> {
"counter" => $newcounter,
  },
}
 
create_resources('sum_series', $hash)
  }
}
 
sum_series { '50': }

@@host { "${::hostname}.branan.ec2":
  ip => $::ipaddress
}

Host<<||>>



When this manifest is applied with `puppet agent -t`, 51 (yes, fifty-one. Not a typo) queries to puppetdb are made to collect the Host resources.
If I comment out the "sum_series  { '50': }
" line, a mere 5 queries are made... which is still 5 times as many as I would expect.
In my environment of about 850 nodes, each of these queries takes about 0.1 seconds to complete, which means a good 5s are spent only hitting puppetdb, without counting the decoding and processing of the resources that the master does once it gets them (the extent of which I don't actually know)












   

 Add Comment











 













 PuppetDB /  PDB-93



  duplicate resource collections during catalog compilation 







 While attempting to troubleshoot performance issues with puppetdb, I noticed that during a single catalog compilation, the same resources are trying to be collected multiple times. In my case, what is normally 4 collections turns into 28. This is potentially the source of my performance issue when multiple nodes check in and hammer puppetdb with all these

Jira (PUP-979) future parser fails to recognize hash as parameter in un-parenthesized calls

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-979



  future parser fails to recognize hash as parameter in un-parenthesized calls 










Change By:

 Andrew Parker




Story Points:

 5 2












   

 Add Comment











 










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




 














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

Jira (PUP-979) future parser fails to recognize hash as parameter in un-parenthesized calls

Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: future parser fails to recognize hash as parameter in un-parenthesized calls 










Don't forget that this also includes removing the extra warnings around "foo  { a => 5 }
" (titleless resource declaration)












   

 Add Comment











 













 Puppet /  PUP-979



  future parser fails to recognize hash as parameter in un-parenthesized calls 







 If an attempt is made to evaluate this  {code}  notice {a => 10}  {code}   The result is the error message: "ll resource specifications require names"   This is because it was once allowed to have resource initialization without a name, and the parser issues a deprecation error for this.   This is somewhat tricky to work around as the grammar does not ...















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

Jira (PUP-979) future parser fails to recognize hash as parameter in un-parenthesized calls

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-979



  future parser fails to recognize hash as parameter in un-parenthesized calls 










Change By:

 Andrew Parker




Story Points:

 2 5












   

 Add Comment











 










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




 














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

Jira (PUP-979) future parser fails to recognize hash as parameter in un-parenthesized calls

Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: future parser fails to recognize hash as parameter in un-parenthesized calls 










We are going to change the grammar so that all function calls need to use parentheses. Many of the built in statement functions (include, require, realize, defined, contain) will be changed to be keywords. This will clear up the grammar for dealing with resources and remove some ambiguous cases.
The problematic case is the logging functions. Do they become keywords or do they stay as functions and therefore require parens around the args? In many cases this shouldn't be a major change, but notice is used a lot as a statement to puts some information.












   

 Add Comment











 













 Puppet /  PUP-979



  future parser fails to recognize hash as parameter in un-parenthesized calls 







 If an attempt is made to evaluate this  {code}  notice {a => 10}  {code}   The result is the error message: "ll resource specifications require names"   This is because it was once allowed to have resource initialization without a name, and the parser issues a deprecation error for this.   This is somewhat tricky to work around as the grammar does not ...















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

Jira (FACT-239) Expose different resolution types in DSL

Title: Message Title










 

 Joshua Cooper assigned an issue to Joshua Cooper











 






 Facter /  FACT-239



  Expose different resolution types in DSL 










Change By:

 Joshua Cooper




Assignee:

 Joshua Cooper












   

 Add Comment











 










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




 














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

Jira (PUP-542) Provide access to all facts in a single structure

Title: Message Title










 

 Andrew Parker assigned an issue to Adrien Thebo











 







Adrien Thebo might be the best one to take a look at this for an FR. I looked over it when merging, but Adrien's been working on facter 2 and so is more immediately familiar with facts right now.









 Puppet /  PUP-542



  Provide access to all facts in a single structure 










Change By:

 Andrew Parker




Assignee:

 Andrew Parker 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/groups/opt_out.

Jira (PUP-542) Provide access to all facts in a single structure

Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: Provide access to all facts in a single structure 










For FR: make sure that interaction with $trusted and --trusted_node_data is sane. Try adding new facts and see them get in. Look over the list and make sure that non-facts (aside from "local facts" of clientcert, clientversion, and clientnoop) don't appear in the structure.












   

 Add Comment











 













 Puppet /  PUP-542



  Provide access to all facts in a single structure 







 The facts that are reported by the agent should be accessible via a top-scope {{$facts}} hash. The keys are the fact names and the values are the fact values.   If this variable is shadowed in a scope the evaluator should emit a warning.















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




 














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

Jira (PUP-542) Provide access to all facts in a single structure

Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: Provide access to all facts in a single structure 










Merged into master in 6ec652












   

 Add Comment











 













 Puppet /  PUP-542



  Provide access to all facts in a single structure 







 The facts that are reported by the agent should be accessible via a top-scope {{$facts}} hash. The keys are the fact names and the values are the fact values.   If this variable is shadowed in a scope the evaluator should emit a warning.















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




 














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

Jira (PUP-542) Provide access to all facts in a single structure

Title: Message Title










 

 Andrew Parker assigned an issue to Andrew Parker











 






 Puppet /  PUP-542



  Provide access to all facts in a single structure 










Change By:

 Andrew Parker




Assignee:

 Andrew 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/groups/opt_out.

Jira (PDB-401) PR (826): Port to trapperkeeper 0.3.0 - cprice404

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (826): Port to trapperkeeper 0.3.0 - cprice404 










cprice404 commented:
@puppetlabs-jenkins retest this please












   

 Add Comment











 













 PuppetDB /  PDB-401



  PR (826): Port to trapperkeeper 0.3.0 - cprice404 







 h2. Port to trapperkeeper 0.3.0   * Author: Chris Price <>  * Company:   * Github ID: [cprice404|https://github.com/cprice404]  * [Pull Request 826 Discussion|https://github.com/puppetlabs/puppetdb/pull/826]  * [Pull Request 826 File Diff|https://github.com/puppetlabs/puppetdb/pull/826/files]  h2. Pull Request Description   This commit updates PuppetD...















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




 














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

Jira (PDB-13) Add acceptance tests for platforms with a default ruby of 1.9

2014-02-26 Thread John Duarte (JIRA)

Title: Message Title










 

 John Duarte updated an issue











 






 PuppetDB /  PDB-13



  Add acceptance tests for platforms with a default ruby of 1.9 










Change By:

 John Duarte




Assignee:

 Branan Purvine-Riley












   

 Add Comment











 










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




 














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

Jira (PUP-1665) Puppet cert list behavior is suboptimal

2014-02-26 Thread Peter Huene (JIRA)

Title: Message Title










 

 Peter Huene updated an issue











 






 Puppet /  PUP-1665



  Puppet cert list behavior is suboptimal 










Change By:

 Peter Huene




Sprint:

 Week 2014-2-26 to 2014-3-5












   

 Add Comment











 










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




 














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

Jira (PDB-13) Add acceptance tests for platforms with a default ruby of 1.9

2014-02-26 Thread John Duarte (JIRA)

Title: Message Title










 

 John Duarte updated an issue











 






 PuppetDB /  PDB-13



  Add acceptance tests for platforms with a default ruby of 1.9 










Change By:

 John Duarte




Labels:

 qa-reviewed












   

 Add Comment











 










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




 














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

Jira (PUP-1778) puppet parser validate --ignoreimport ignores a bit too much

2014-02-26 Thread redmine.exporter (JIRA)

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1778



  puppet parser validate --ignoreimport ignores a bit too much 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 26/Feb/14 1:24 PM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










Attempting to validate changed manifests in a git pre-commit hook, I found that a regular `puppet parser validate` was complaining about not being able to find imported files. So, I whacked `--ignoreimport` in there and all seemed fine... until I realised it wasn't finding legitimate syntax errors.
Turns out that `--ignoreimport` ignores a bit too much, and doesn't actually perform a parse. Quick fix was to remove the first line of `perform_initial_import` (in `node/environment.rb`) so that it didn't return immediately.
What other effects that might have, I couldn't rightly say, but at least I know when I've broken my manifests now.












   

 Add Comment

Jira (PUP-1665) Puppet cert list behavior is suboptimal

2014-02-26 Thread Peter Huene (JIRA)

Title: Message Title










 

 Peter Huene updated an issue











 






 Puppet /  PUP-1665



  Puppet cert list behavior is suboptimal 










Change By:

 Peter Huene




Story Points:

 1












   

 Add Comment











 










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




 














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

Jira (PUP-1665) Puppet cert list behavior is suboptimal

2014-02-26 Thread Peter Huene (JIRA)

Title: Message Title










 

 Peter Huene assigned an issue to Peter Huene











 






 Puppet /  PUP-1665



  Puppet cert list behavior is suboptimal 










Change By:

 Peter Huene




Assignee:

 Peter Huene












   

 Add Comment











 










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




 














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

Jira (PUP-1777) PR (2391): pup-1766 make systemd the defaultprovider for service on rhel7 - kylog

Title: Message Title










 

 gepetto-bot created an issue











 






 Puppet /  PUP-1777



  PR (2391): pup-1766 make systemd the defaultprovider for service on rhel7 - kylog 










Issue Type:

  Task




Assignee:

 Eric Sorenson




Components:


 Community




Created:


 26/Feb/14 1:12 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










pup-1766 make systemd the defaultprovider for service on rhel7


Author: Kylo Ginsberg <>


Company:


Github ID: kylog


Pull Request 2391 Discussion


Pull Request 2391 File Diff


Pull Request Description

Note that this need uncovere

Jira (PUP-1662) PR (2346): Test on 2.1.0 now that it's stable - rb2k

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2346): Test on 2.1.0 now that it's stable - rb2k 










peterhuene commented:
Thanks for the contribution!












   

 Add Comment











 













 Puppet /  PUP-1662



  PR (2346): Test on 2.1.0 now that it's stable - rb2k 







 h2. Test on 2.1.0 now that it's stable   * Author: Marc Seeger   * Company:   * Github ID: [rb2k|https://github.com/rb2k]  * [Pull Request 2346 Discussion|https://github.com/puppetlabs/puppet/pull/2346]  * [Pull Request 2346 File Diff|https://github.com/puppetlabs/puppet/pull/2346/files]  h2. Pull Request Description  (web...















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




 














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

Jira (PUP-1772) Proposal to make Puppet::Util::Profiler#profile api public

Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: Proposal to make Puppet::Util::Profiler#profile api public 










Merged into master in 5eaa40. This will make it into the 3.5.0 release












   

 Add Comment











 













 Puppet /  PUP-1772



  Proposal to make Puppet::Util::Profiler#profile api public 







 The current profile method: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/profiler.rb#L30-L32, would be perfect for PuppetDB terminus to use to solve any profiling issues internally. We've had some bugs raised on this in the past but it would be great to be able to produce profiling information in the same fashion that Puppet does.   T...















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




 














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

Jira (PUP-1772) Proposal to make Puppet::Util::Profiler#profile api public

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-1772



  Proposal to make Puppet::Util::Profiler#profile api public 










Change By:

 Andrew Parker




Fix Version/s:

 3.6.0




Fix Version/s:

 3.5.0












   

 Add Comment











 










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




 














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

Jira (PUP-1662) PR (2346): Test on 2.1.0 now that it's stable - rb2k

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2346): Test on 2.1.0 now that it's stable - rb2k 










Pull request Test on 2.1.0 now that it's stable has been closed.












   

 Add Comment











 













 Puppet /  PUP-1662



  PR (2346): Test on 2.1.0 now that it's stable - rb2k 







 h2. Test on 2.1.0 now that it's stable   * Author: Marc Seeger   * Company:   * Github ID: [rb2k|https://github.com/rb2k]  * [Pull Request 2346 Discussion|https://github.com/puppetlabs/puppet/pull/2346]  * [Pull Request 2346 File Diff|https://github.com/puppetlabs/puppet/pull/2346/files]  h2. Pull Request Description  (web...















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




 














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

Jira (PUP-845) Create a windows provider

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Create a windows provider 










Filed as PUP-1776












   

 Add Comment











 













 Puppet /  PUP-845



  Create a windows provider 







 Create a basic (empty) windows provider that is only suitable on windows.















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




 














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

Jira (PUP-1776) acl module can't load helper code when types loaded on master

Title: Message Title










 

 Joshua Cooper created an issue











 






 Puppet /  PUP-1776



  acl module can't load helper code when types loaded on master 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 26/Feb/14 12:20 PM




Fix Versions:


 M




Labels:


 windows




Priority:

  Normal




Reporter:

 Joshua Cooper










The type and provider try to require 'puppet/type/acl/ace', etc, but this doesn't work when the module is installed on the puppetmaster, because individual module lib directories are not added to the master's LOAD_PATH.
The pattern that we've followed in the past is to use a relative directory, e.g.



require 'pathname'
require Pathname.new(__FILE__).dirname + "../../" + "puppet/type/acl/ace"

Jira (PUP-845) Create a windows provider

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Create a windows provider 










Verified running via puppet apply on windows. Also when running a Linux agent, I get the expected gracefully error message:



Error: Could not find a suitable provider for acl



I am having issues running a puppetmaster/agent due to $LOAD_PATH issues on the master when the acl module requires common helper code. I will file a separate issue for that.












   

 Add Comment











 













 Puppet /  PUP-845



  Create a windows provider 







 Create a basic (empty) windows provider that is only suitable on windows.















 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 (PUP-1764) PR (2387): Respect Yum's lock - seveas

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2387): Respect Yum's lock - seveas 










seveas commented:
Ticket filed: https://tickets.puppetlabs.com/browse/PUP-1775












   

 Add Comment











 













 Puppet /  PUP-1764



  PR (2387): Respect Yum's lock - seveas 







 h2. Respect Yum's lock   * Author: Dennis Kaarsemaker   * Company: Booking.com  * Github ID: [seveas|https://github.com/seveas]  * [Pull Request 2387 Discussion|https://github.com/puppetlabs/puppet/pull/2387]  * [Pull Request 2387 File Diff|https://github.com/puppetlabs/puppet/pull/2387/files]  h2. Pull Request Description   We...















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




 














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

Jira (PUP-1775) yumhelper.py: Not respecting the yum lock leads to RPM database corruption

2014-02-26 Thread Dennis Kaarsemaker (JIRA)

Title: Message Title










 

 Dennis Kaarsemaker created an issue











 






 Puppet /  PUP-1775



  yumhelper.py: Not respecting the yum lock leads to RPM database corruption 










Issue Type:

  Bug




Assignee:

 Kylo Ginsberg




Components:


 Types and Providers




Created:


 26/Feb/14 12:07 PM




Priority:

  Normal




Reporter:

 Dennis Kaarsemaker










We're recently seeing frequent rpm database corruption on our systems and have narrowed it down to yumhelper.py not respecting Yum's lock. Not doing so means that a concurrently running yum, or any other application using the yum library, will make yumhelper.py corrupt the rpm database.
In our case an ossec module which uses the yum library and does proper locking started taking longer and now there are frequent clashes between it and a puppet run. This doesn't always cause corruption, but we've been seeing it quite a bit. Making yumhelper.py respect Yum's lock fixed the corruption problem for us.
A patch for this can be found on https://github.com/puppetlabs/puppet/pull/2387












   

 Add Comment

Jira (PUP-1764) PR (2387): Respect Yum's lock - seveas

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2387): Respect Yum's lock - seveas 










seveas commented:
finally blocks get executed even in the face of sys.exit in the try block. Observe: ``` dennis@spirit:~$ cat foo.py  import sys try: sys.exit(0) finally: print "After exit" dennis@spirit:~$ python foo.py After exit ```












   

 Add Comment











 













 Puppet /  PUP-1764



  PR (2387): Respect Yum's lock - seveas 







 h2. Respect Yum's lock   * Author: Dennis Kaarsemaker   * Company: Booking.com  * Github ID: [seveas|https://github.com/seveas]  * [Pull Request 2387 Discussion|https://github.com/puppetlabs/puppet/pull/2387]  * [Pull Request 2387 File Diff|https://github.com/puppetlabs/puppet/pull/2387/files]  h2. Pull Request Description   We...















 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 gro

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

Title: Message Title










 

 gepetto-bot commented on an issue











 






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










m4ce commented:
Hi @adrienthebo,
It appears to be a bug in the chkconfig shipped with SLES insserv package.
There's already a ticket that relates to this bug at https://projects.puppetlabs.com/issues/20121 .
Note that the changes I have added are partially based on this old commit: https://github.com/puppetlabs/puppet/commit/e740bc41137fa59e30b125ddacadd6aed359 .
Although my changes fix the enable issue for boot services, it does introduce another. When running chkconfig against a non-existent boot., that returns zero. Only way to work around this would be to check if the chkconfig stderr =~ /unknown service$/.
Best would be really for SLES chkconfig to behave normally 
Cheers, Matteo












   

 Add Comment











 













 Puppet /  PUP-1751



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







 h2. Suse chkconfig --check boot. always returns 1 whether the service is enabled/disabled.   * Author: Matteo <>  * Company:   * Github ID: [m4ce|https://github.com/m4ce]  * [Pull Request 2383 Discussion|https://github.com/puppetlabs/puppet/pull/2383]  * [Pull Request 2383 File Diff|https://github.com/puppetlabs/puppet/pull/2383/files]  h2. Pull ...

Jira (PDB-477) Support for NCSA (or Apache access_log) logging in jetty

Title: Message Title










 

 Kenneth Barber moved an issue











 






 PuppetDB /  PDB-477



  Support for NCSA (or Apache access_log) logging in jetty 










Change By:

 Kenneth Barber




Key:

 PUP PDB - 1774 477




Project:

 Puppet PuppetDB












   

 Add Comment











 










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




 














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

Jira (PUP-1774) Support for NCSA (or Apache access_log) logging in jetty

Title: Message Title










 

 Kenneth Barber created an issue











 






 Puppet /  PUP-1774



  Support for NCSA (or Apache access_log) logging in jetty 










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 26/Feb/14 11:58 AM




Priority:

  Normal




Reporter:

 Kenneth Barber










It would be nice to add NCSA style logging to PuppetDB for request logs. This would help users debug queries and help with analyzing query load via logstash/splunk/webalizer and other tools like that.
NCSA == apache style logging for you younger dudes.
Ref: https://wiki.eclipse.org/Jetty/Howto/Configure_Request_Logs












   

 Add Comment











 










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

Jira (PUP-1764) PR (2387): Respect Yum's lock - seveas

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2387): Respect Yum's lock - seveas 










kylog commented:
@seveas During triage, we had some concern that this change could leave the db open, due to the `sys.exit` in the `except` (so not getting to the `finally` block).
Also, bookkeeping: can you add an issue in tickets.puppetlabs.com's puppet project describing the issue (and reference it in the commit messages).
@lutter do you have any comment on this? 












   

 Add Comment











 













 Puppet /  PUP-1764



  PR (2387): Respect Yum's lock - seveas 







 h2. Respect Yum's lock   * Author: Dennis Kaarsemaker   * Company: Booking.com  * Github ID: [seveas|https://github.com/seveas]  * [Pull Request 2387 Discussion|https://github.com/puppetlabs/puppet/pull/2387]  * [Pull Request 2387 File Diff|https://github.com/puppetlabs/puppet/pull/2387/files]  h2. Pull Request Description   We...















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

Jira (PUP-1772) Proposal to make Puppet::Util::Profiler#profile api public

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Proposal to make Puppet::Util::Profiler#profile api public 










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












   

 Add Comment











 













 Puppet /  PUP-1772



  Proposal to make Puppet::Util::Profiler#profile api public 







 The current profile method: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/profiler.rb#L30-L32, would be perfect for PuppetDB terminus to use to solve any profiling issues internally. We've had some bugs raised on this in the past but it would be great to be able to produce profiling information in the same fashion that Puppet does.   T...















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




 














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

Jira (PUP-1568) Error reporting within augeas provider fails

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Error reporting within augeas provider fails 










Merged to master in 28c12d1 to be released in 3.5.0












   

 Add Comment











 













 Puppet /  PUP-1568



  Error reporting within augeas provider fails 







 If the augeas provider fails to store a change to a file it's error reporting is broken due to the refactoring that happened in https://github.com/puppetlabs/puppet/commit/000b8fef6a33e5c9f56c0801523de15a0e5bc30b   {noformat}  # cat foo.pp  augeas{'enable_shorewall':    context => '/files/etc/sysconfig/shorewall',    changes => 'set startup 1',    lens ...















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




 














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

Jira (PUP-1568) Error reporting within augeas provider fails

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1568



  Error reporting within augeas provider fails 










Change By:

 Joshua Cooper




Sprint:

 Week 2014-2-26 to 2014-3-5












   

 Add Comment











 










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




 














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

Jira (HI-213) Docs pushed

2014-02-26 Thread Nicholas Fagerlund (JIRA)

Title: Message Title










 

 Nicholas Fagerlund commented on an issue











 






  Re: Docs pushed 










This is ready to go. Hit me when it's release time. 












   

 Add Comment











 













 Hiera /  HI-213



  Docs pushed 














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




 














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

Jira (HI-220) Interpolation functions can cause infinite recursion when used in the settings file

2014-02-26 Thread Nicholas Fagerlund (JIRA)

Title: Message Title










 

 Nicholas Fagerlund commented on an issue











 






  Re: Interpolation functions can cause infinite recursion when used in the settings file 










I've changed the wording of the docs warning to link here and be more emphatic about avoiding hiera() in the config file. (This change will go out with the hiera 1.3.2 final release.)












   

 Add Comment











 













 Hiera /  HI-220



  Interpolation functions can cause infinite recursion when used in the settings file 







 Given the following {{hiera.yaml}} file where an interpolation function is used to define the hierarchy:   {code}  ---  :backends:    - yaml  :logger: console  :hierarchy:    - "roles/%{hiera('role')}"    - common   :yaml:     :datadir: /etc/puppet/environments/%{environment}/extdata  {code}   This will result in infinite recursion on any lookup:   {c...















 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 h

Jira (PUP-1568) Error reporting within augeas provider fails

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1568



  Error reporting within augeas provider fails 










Change By:

 Joshua Cooper




Story Points:

 1












   

 Add Comment











 










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




 














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

Jira (PUP-1568) Error reporting within augeas provider fails

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1568



  Error reporting within augeas provider fails 










Change By:

 Joshua Cooper




Fix Version/s:

 3.5.0












   

 Add Comment











 










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




 














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

Jira (PUP-1569) PR (2324): Fix/master/pup 1568 fix error reporting - duritong

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2324): Fix/master/pup 1568 fix error reporting - duritong 










Pull request Fix/master/pup 1568 fix error reporting has been closed.












   

 Add Comment











 













 Puppet /  PUP-1569



  PR (2324): Fix/master/pup 1568 fix error reporting - duritong 







 h2. Fix/master/pup 1568 fix error reporting   * Author: duritong <>  * Company:   * Github ID: [duritong|https://github.com/duritong]  * [Pull Request 2324 Discussion|https://github.com/puppetlabs/puppet/pull/2324]  * [Pull Request 2324 File Diff|https://github.com/puppetlabs/puppet/pull/2324/files]  h2. Pull Request Description   https://tickets.pupp...















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




 














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

Jira (PUP-1772) Proposal to make Puppet::Util::Profiler#profile api public

Title: Message Title










 

 Kenneth Barber updated an issue











 






 Puppet /  PUP-1772



  Proposal to make Puppet::Util::Profiler#profile api public 










Change By:

 Kenneth Barber




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/groups/opt_out.

Jira (PUP-1773) Disallow Regexp in current catalog format

Title: Message Title










 

 Andrew Parker created an issue











 






 Puppet /  PUP-1773



  Disallow Regexp in current catalog format 










Issue Type:

  Bug




Affects Versions:


 3.5.0




Assignee:

 Andrew Parker




Components:


 DSL




Created:


 26/Feb/14 11:34 AM




Fix Versions:


 3.6.0




Priority:

  Normal




Reporter:

 Andrew Parker










The new Regexp type can end up in the catalog when it is set as a parameter on a resource. The current/3.x catalog format cannot handle this, and so we need to make sure that the compiler system produces an error and stops the catalog compilation when this occurs.
A new catalog format, that can represent Regexp, will happen during the 4.x series.

Jira (PUP-525) Support Regular Expression as data type (an issue of encoding)

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-525



  Support Regular _expression_ as data type (an issue of encoding) 










Change By:

 Andrew Parker




Fix Version/s:

 3.6.0




Fix Version/s:

 3.5.0












   

 Add Comment











 










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




 














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

Jira (PUP-1772) Proposal to make Puppet::Util::Profiler#profile api public

Title: Message Title










 

 Kenneth Barber updated an issue











 






 Puppet /  PUP-1772



  Proposal to make Puppet::Util::Profiler#profile api public 










Change By:

 Kenneth Barber









 The current profile method: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/profiler.rb#L30-L32 Would , would  be perfect for PuppetDB terminus to use to solve any profiling issues internally. We've had some bugs raised on this in the past but it would be great to be able to produce profiling information in the same fashion that Puppet does.This will mean that users seeing any performance issues on their master will see the terminus profiling right alongside it. It also means we don't need to reinvent the wheel in terminus to do this action.Right now I only see the method #profile as needing to be exposed, the others can probably happily stay private.I'm going to provide a patch as well today, and I'll attach the URL for a PR to this ticket very shortly.












   

 Add Comment











 










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




 














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

Jira (PUP-1772) Proposal to make Puppet::Util::Profiler#profile api public

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Proposal to make Puppet::Util::Profiler#profile api public 










This ticket (or at least the decision around this ticket) kind of blocks PDB-476 being implemented in the way we would prefer, although if you decided to not make this public we would just change tactics.












   

 Add Comment











 













 Puppet /  PUP-1772



  Proposal to make Puppet::Util::Profiler#profile api public 







 The current profile method: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/profiler.rb#L30-L32, would be perfect for PuppetDB terminus to use to solve any profiling issues internally. We've had some bugs raised on this in the past but it would be great to be able to produce profiling information in the same fashion that Puppet does.   T...















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

Jira (PUP-525) Support Regular Expression as data type (an issue of encoding)

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-525



  Support Regular _expression_ as data type (an issue of encoding) 










Change By:

 Andrew Parker




Fix Version/s:

 4.0.0




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/groups/opt_out.

Jira (PUP-1772) Proposal to make Puppet::Util::Profiler#profile api public

Title: Message Title










 

 Kenneth Barber updated an issue











 






 Puppet /  PUP-1772



  Proposal to make Puppet::Util::Profiler#profile api public 










Change By:

 Kenneth Barber




Summary:

 Proposal to  un-private  make  Puppet::Util::Profiler#profile  api public












   

 Add Comment











 










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




 














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

Jira (PUP-1772) Proposal to un-private Puppet::Util::Profiler#profile

Title: Message Title










 

 Kenneth Barber created an issue











 






 Puppet /  PUP-1772



  Proposal to un-private Puppet::Util::Profiler#profile 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 26/Feb/14 11:29 AM




Priority:

  Normal




Reporter:

 Kenneth Barber










The current profile method: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/profiler.rb#L30-L32
Would be perfect for PuppetDB terminus to use to solve any profiling issues internally. We've had some bugs raised on this in the past but it would be great to be able to produce profiling information in the same fashion that Puppet does.
This will mean that users seeing any performance issues on their master will see the terminus profiling right alongside it. It also means we don't need to reinvent the wheel in terminus to do this action.
Right now I only see the method #profile as needing to be exposed, the others can probably happily stay private.
I'm going to provide a patch as well today, and I'll attach the URL for a PR to this ticket very shortly.












   

 Add Comment

Jira (PUP-1564) package rpm provider should support :uninstall_options feature

Title: Message Title










 

 Charlie Sharpsteen assigned an issue to Charlie Sharpsteen











 






 Puppet /  PUP-1564



  package rpm provider should support :uninstall_options feature 










Change By:

 Charlie Sharpsteen




Assignee:

 Eric Sorenson Charlie Sharpsteen












   

 Add Comment











 










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




 














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

Jira (PDB-476) Convert the terminus performance logging one-off support solution to something permanent

Title: Message Title










 

 Kenneth Barber assigned an issue to Kenneth Barber











 






 PuppetDB /  PDB-476



  Convert the terminus performance logging one-off support solution to something permanent 










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/groups/opt_out.

Jira (PUP-1771) Simplify the syntax for specifying file paths in modules using a '~'

2014-02-26 Thread redmine.exporter (JIRA)

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1771



  Simplify the syntax for specifying file paths in modules using a '~' 










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 26/Feb/14 11:25 AM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










There is too much redundant info in puppet file source specifications in modules.
 file  { "ugly": source => "puppet:///modules/foo/bar", }

Additionally, we're inconsistent with our template() and file() functions.
template() takes either a path relative to the modulepath, dereferencing to "templates" sub-directories of the module or an absolute path. file() takes an absolute path only.
I suggest (after a flash of inspiration from Patrick on the mailing list) we use the '~' syntax in a standard unix-y way to refer to module locations as follows.
Each class mentioned below corresponds to a module.
File source:
Reference: $modulepath/modules/foo/files/bar   class foo { file  { "booyah": source => "~/bar", }
}
class notfoo { file  { "booyah2": source => "~foo/bar", }
} 
Template function: Reference: $modulepath/modules/foo/templates/bar.erb  class foo { file  { "booyah": content => template("~/bar.erb"), }
}

Jira (PUP-1079) Exported resources is exporting to the database with --noop flag

2014-02-26 Thread Christophe Vanlancker (JIRA)

Title: Message Title










 

 Christophe Vanlancker updated an issue











 






 Puppet /  PUP-1079



  Exported resources is exporting to the database with --noop flag 










Change By:

 Christophe Vanlancker




Component/s:

 Catalog Application












   

 Add Comment











 










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




 














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

Jira (PUP-1079) Exported resources is exporting to the database with --noop flag

2014-02-26 Thread Christophe Vanlancker (JIRA)

Title: Message Title










 

 Christophe Vanlancker updated an issue











 






 Puppet /  PUP-1079



  Exported resources is exporting to the database with --noop flag 










Change By:

 Christophe Vanlancker




Affects Version/s:

 3.3.1












   

 Add Comment











 










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




 














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

Jira (PUP-1079) Exported resources is exporting to the database with --noop flag

2014-02-26 Thread Christophe Vanlancker (JIRA)

Title: Message Title










 

 Christophe Vanlancker commented on an issue











 






  Re: Exported resources is exporting to the database with --noop flag 










Quick recap:
There is a valid use-case for both behaviours:


--noop exports resources but doesn't affect locally (migration to PuppetDB and have everything pre-populated)


--noop (in combination with another option likely) doesn't export resources (for testing changes which could potentially remove necessary exported resources like apache vhosts, nagios_hosts, firewall rules and the likes)














   

 Add Comment











 













 Puppet /  PUP-1079



  Exported resources is exporting to the database with --noop flag 







 When I run puppet with the noop flag resources are being exported to the  db.   I would expect it to simulate the transaction with the db...   This is causing things like nagios host resources being creating before the plugins get there, so I get invalid alerts.   -Andrew















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

Jira (PDB-402) Disable AOT compiling of PuppetDB code

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Disable AOT compiling of PuppetDB code 










PR is here: https://github.com/puppetlabs/puppetdb/pull/871












   

 Add Comment











 













 PuppetDB /  PDB-402



  Disable AOT compiling of PuppetDB code 







 We currently need to use AOT to support "java -jar .. services..." form of execution. We can instead switch to "java -cp ... clojure.main -m services ..." which does not require AOT compiling and removes the need to do any AOT compiling of PuppetDB code. This would have saved us a lot of headaches. The steps needed to do this are below:   - Change scri...















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




 














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

Jira (PUP-489) Handle += / -= with consistent semantics

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-489



  Handle += / -= with consistent semantics 










Change By:

 Andrew Parker









 The current 4x implementation does this:* if referenced and given are numeric, do arithmetic + or -* if referenced and given are  collection  collections , do concat/merge* else fail (no string concatenation)Decide:* is this implementation ok* should string concatenation be allowed (+ is not string concat elsewhere)* Remove in favor of explicit $a = $a + [ ] (etc. possible because hashes and arrays support + operator).












   

 Add Comment











 










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




 














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

Jira (PUP-489) Handle += / -= with consistent semantics

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-489



  Handle += / -= with consistent semantics 










Change By:

 Andrew Parker









 The current 4x implementation does this:* if referenced and given are numeric, do arithmetic + or -* if referenced and given are  collectsion  collection , do concat/merge* else fail (no string concatenation)Decide:* is this implementation ok* should string concatenation be allowed (+ is not string concat elsewhere)* Remove in favor of explicit $a = $a + [ ] (etc. possible because hashes and arrays support + operator).












   

 Add Comment











 










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




 














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

Jira (HI-213) Docs pushed

2014-02-26 Thread Justin Holguin (JIRA)

Title: Message Title










 

 Justin Holguin updated an issue











 






 Hiera /  HI-213



  Docs pushed 










Change By:

 Justin Holguin




Assignee:

 Justin Holguin Nicholas Fagerlund












   

 Add Comment











 










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




 














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

Jira (FACT-310) Docs pushed

2014-02-26 Thread Justin Holguin (JIRA)

Title: Message Title










 

 Justin Holguin updated an issue











 






 Facter /  FACT-310



  Docs pushed 










Change By:

 Justin Holguin




Assignee:

 Justin Holguin Nicholas Fagerlund












   

 Add Comment











 










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




 














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

Jira (PUP-1584) Puppet module tool should work with new directory environments

2014-02-26 Thread Tony Vu (JIRA)

Title: Message Title










 

 Tony Vu assigned an issue to Tony Vu











 






 Puppet /  PUP-1584



  Puppet module tool should work with new directory environments 










Change By:

 Tony Vu




Assignee:

 Tony Vu












   

 Add Comment











 










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




 














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

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

Title: Message Title

gepetto-bot commented on an issue

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

adrienthebo commented:
@m4ce thanks for this contribution!
Looking at this change doesn't make it immediately clear what's going on or why the underlying behavior is present. Is this a bug in chkconfig or is this intended? It would be very helpful to have a ticket associated with this change so that we can have some documentation available for future reference, if we ever have questions about this change in the future.
In addition it doesn't look like there is test coverage associated with this change. Test coverage helps prevent regressions and makes it easier to reason about what the change is expected to do; would you be willing to try to add some test coverage to this?

Add Comment

Puppet / PUP-1751

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

h2. Suse chkconfig --check boot. always returns 1 whether the service is enabled/disabled. * Author: Matteo <> * Company: * Github ID: [m4ce|https://github.com/m4ce] * [Pull Request 2383 Discussion|https://github.com/puppetlabs/puppet/pull/2383] * [Pull Request 2383 File Diff|https://github.com/puppetlabs/puppet/pull/2383/files] h2. Pull ...

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

Jira (HI-204) Is checklist current

2014-02-26 Thread Melissa Stone (JIRA)

Title: Message Title










 

 Melissa Stone assigned an issue to Melissa Stone











 






 Hiera /  HI-204



  Is checklist current 










Change By:

 Melissa Stone




Assignee:

 Andrew Parker Melissa Stone












   

 Add Comment











 










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




 














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

Jira (PUP-479) Handle types other than string as hash key

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-479



  Handle types other than string as hash key 










Change By:

 Andrew Parker









 Currently  on  only  String, and Name can be used as hash keys (most specifically it is not possible to have a QualifiedName - e.g. a Type as a key).This is currently prohibited in the grammar. It can be relaxed to allow any _expression_ as key. Validation can be added to prevent certain types of expressions if we do not want this open ended while still allowing Type.From an evaluator perspective it is only required that the _expression_ results in an object that can function as a hash key.Suggest making this open ended, all puppet types can technically function as hash keys).OPTIONS:* as today (bad)* also accept type* accept anythingIf we want to restrict to type only, a decision has to be made if only accepting a literal type, or if it can be the result of an _expression_.The easiest (and most powerful) is to make it open ended and accept anything.












   

 Add Comment











 










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




 














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

Jira (PUP-479) Handle types other than string as hash key

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-479



  Handle types other than string as hash key 










Change By:

 Andrew Parker




Summary:

 Handle  other  types  other  than string as hash key












   

 Add Comment











 










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




 














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

Jira (PUP-956) PR (2136): (#11383) support purging of all cronjobs - ffrank