date:20140122

Title: Message Title










 

 gepetto-bot commented on an issue











 






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










Savar commented:
I get your point with the necessity of versioning and that stuff but I don't agree with this as an argument to not fix bad bugs which are a pain in the ass.
And this change is not really "not backwards compatible" .. the only thing which is changing: now every valid float is allowed instead of only the ones which are exceptionally looking the same after doing String.to_f.to_s ..
So do you say I have to wait for a rewrite until I get rid of ruby exceptions in my puppet run because is_integer cannot check an array/hash?












   

 Add Comment











 













 Puppet /  PUP-1195



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







 h2. fix is_numeric/is_integer when checking non-string parameters   * Author: Simon Effenberg <>  * Company:   * Github ID: [Savar|https://github.com/Savar]  * [Pull Request 213 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213]  * [Pull Request 213 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213/files]  h2. Pull Reque...















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

Jira (PUP-1495) Puppet on Debian systems failing to apply file changes

2014-01-22 Thread Anthony Somerset (JIRA)

Title: Message Title










 

 Anthony Somerset created an issue











 






 Puppet /  PUP-1495



  Puppet on Debian systems failing to apply file changes 










Issue Type:

  Bug




Affects Versions:


 3.4.2




Assignee:

 Eric Sorenson




Created:


 22/Jan/14 11:15 PM




Environment:


Debian 64 Bit - Wheezy master (with foreman) through passenger, mix of wheezy or squeeze clients




Priority:

  Normal




Reporter:

 Anthony Somerset










i'm not exactly sure which version this started in but it was after 3.3.x and still exists in 3.4.2
whenever a file change is detected the puppet run it will show the diff but be unable to apply it. it seems to timeout. without debug/verbose this error drops into the terminal window:
err: /Stage[main]/Ssh/File[/etc/ssh/sshd_config]: Could not evaluate: Puppet::Util::Log requires a message
however if i run debug and verbose flags i get:
rror: Could not back up /etc/ssh/sshd_config: Timeout::Error Error: Could not back up /etc/ssh/sshd_config: Timeout::Error Error: /Stage[main]/Ssh/File[/etc/ssh/sshd_config]/content: change from  {md5}8caefdd9e251b7cc1baa37874149a870 to {md5}
2ee23a0ec404874c9e8e8462194fbf29 failed: Could not back up /etc/ssh/sshd_config: Timeout::Error
i note that pluginsync continues to work, creating new files pulling from p

Jira (FACT-194) Merge external facts support to facter-2

Title: Message Title










 

 Kylo Ginsberg assigned an issue to Kylo Ginsberg











 






 Facter /  FACT-194



  Merge external facts support to facter-2 










Change By:

 Kylo Ginsberg




Assignee:

 Eric Sorenson Kylo Ginsberg












   

 Add Comment











 










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




 














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

Jira (FACT-243) PR (613): (RE-814) Add initial support for building in a RHEL 7 mock - mckern

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (613): (RE-814) Add initial support for building in a RHEL 7 mock - mckern 










kylog commented:
Just occurred to me that you probably want to cherry-pick this down to the facter-2 branch, since that's what 2.0.1 will come from.












   

 Add Comment











 













 Facter /  FACT-243



  PR (613): (RE-814) Add initial support for building in a RHEL 7 mock - mckern 







 h2. (RE-814) Add initial support for building in a RHEL 7 mock   * Author: Ryan McKern   * Company: Puppet Labs  * Github ID: [mckern|https://github.com/mckern]  * [Pull Request 613 Discussion|https://github.com/puppetlabs/facter/pull/613]  * [Pull Request 613 File Diff|https://github.com/puppetlabs/facter/pull/613/files]  h2. Pull Re...















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




 














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

Jira (PUP-1485) test agent/fallback_to_cached_catalog.rb assumes no master is running by default

2014-01-22 Thread Branan Purvine-Riley (JIRA)

Title: Message Title










 

 Branan Purvine-Riley assigned an issue to Branan Purvine-Riley











 






 Puppet /  PUP-1485



  test agent/fallback_to_cached_catalog.rb assumes no master is running by default 










Change By:

 Branan Purvine-Riley




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-1494) Windows colors.rb may be subject to Ruby corruption bug with wide strings

2014-01-22 Thread Joshua Cooper (JIRA)

Title: Message Title










 

 Joshua Cooper assigned an issue to Joshua Cooper











 






 Puppet /  PUP-1494



  Windows colors.rb may be subject to Ruby corruption bug with wide strings 










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-1406) PR (2236): Add ability to override default system confdir and vardir - jeffmccune

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2236): Add ability to override default system confdir and vardir - jeffmccune 










zaphod42 commented:
After a bit of discussion during the PR triage, a long discussion and IRC, and @adrienthebo talking to some others (@haus, I believe), the decision is that we aren't going to take this change as is.
The crux of the problem comes down to the desire to use released gems, supposedly unmodified, but configured to work differently at install time, to remove any need to specify the confdir and vardir, yet use the non-default confdir and vardir. This is a very specific set of requirements, which is not something that we want to maintain.
If we drop the requirement to use the released gems, then there is an approach that I would be happy to maintain: introduce a build step into how puppet gets packaged and allow that to control the default confdir and vardir of that build of puppet.












   

 Add Comment











 













 Puppet /  PUP-1406



  PR (2236): Add ability to override default system confdir and vardir - jeffmccune 







 h2. Add ability to override default system confdir and vardir   * Author: Jeff McCune   * Company: Puppet Labs  * Github ID: [jeffmccune|https://github.com/jeffmccune]  * [Pull Request 2236 Discussion|https://github.com/puppetlabs/puppet/pull/2236]  * [Pull Request 2236 File Diff|https://github.com/puppetlabs/puppet/pull/2236/files]  ...















 This message was sent by Atlassia

Jira (FACT-240) PR (611): Feature/facter 2/fact 238 extract resolution mixins - adrienthebo

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (611): Feature/facter 2/fact 238 extract resolution mixins - adrienthebo 










Pull request Feature/facter 2/fact 238 extract resolution mixins has been closed.












   

 Add Comment











 













 Facter /  FACT-240



  PR (611): Feature/facter 2/fact 238 extract resolution mixins - adrienthebo 







 h2. Feature/facter 2/fact 238 extract resolution mixins   * Author: Adrien Thebo git...@somethingsinistral.net>  * Company: Puppet Labs  * Github ID: [adrienthebo|https://github.com/adrienthebo]  * [Pull Request 611 Discussion|https://github.com/puppetlabs/facter/pull/611]  * [Pull Request 611 File Diff|https://github.com/puppetlabs/facter/pull/611/f...















 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-150) PR (173): (RE-816) Add initial support for building in a RHEL 7 mock - mckern

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (173): (RE-816) Add initial support for building in a RHEL 7 mock - mckern 










Pull request (RE-816) Add initial support for building in a RHEL 7 mock has been closed.












   

 Add Comment











 













 Hiera /  HI-150



  PR (173): (RE-816) Add initial support for building in a RHEL 7 mock - mckern 







 h2. (RE-816) Add initial support for building in a RHEL 7 mock   * Author: Ryan McKern   * Company: Puppet Labs  * Github ID: [mckern|https://github.com/mckern]  * [Pull Request 173 Discussion|https://github.com/puppetlabs/hiera/pull/173]  * [Pull Request 173 File Diff|https://github.com/puppetlabs/hiera/pull/173/files]  h2. Pull Requ...















 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-150) PR (173): (RE-816) Add initial support for building in a RHEL 7 mock - mckern

Title: Message Title










 

 gepetto-bot created an issue











 






 Hiera /  HI-150



  PR (173): (RE-816) Add initial support for building in a RHEL 7 mock - mckern 










Issue Type:

  Task




Assignee:

 Adrien Thebo




Components:


 Community




Created:


 22/Jan/14 5:12 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










(RE-816) Add initial support for building in a RHEL 7 mock


Author: Ryan McKern 


Company: Puppet Labs


Github ID: mckern


Pull Request 173 Discussion


Pull Request 173 File Diff


Pull Request Description

Building in an x86_64 mock, since

Jira (PUP-1411) Windows agents experience intermittent SSL_connect failures in acceptance testing

2014-01-22 Thread Joshua Cooper (JIRA)

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Windows agents experience intermittent SSL_connect failures in acceptance testing 












 * Agents: Run agent --test second time to obtain signed cert
...
kkmn0q5m0bgh6rx (agent-2012-x86_64) $ env PATH="/opt/puppet-git-repos/hiera/bin:${PATH}" RUBYLIB="`cygpath -w /opt/puppet-git-repos/hiera/lib`;`cygpath -w /opt/puppet-git-repos/hiera-puppet/lib`;${RUBYLIB}" cmd.exe /c puppet agent kkmn0q5m0bgh6rx --test --server a4e5hyo2m0ooom1
Exiting; failed to retrieve certificate and waitforcert is disabled
Error: Could not request certificate: SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A

kkmn0q5m0bgh6rx (agent-2012-x86_64) executed in 12.00 seconds
Exited: 1



Note the time is a bit higher than normal












   

 Add Comment











 













 Puppet /  PUP-1411



  Windows agents experience intermittent SSL_connect failures in acceptance testing 







 Breaking this out as a separate ticket related to QA-768.  During Windows acceptance testing on master, certificate requests non-deterministically fail due with SSL_connect failures:  {code}  #  ...















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

Jira (PDB-345) PR (812): Fixes an issue when using spyscope as a lein user profile - senior

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (812): Fixes an issue when using spyscope as a lein user profile - senior 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 PuppetDB /  PDB-345



  PR (812): Fixes an issue when using spyscope as a lein user profile - senior 







 h2. Fixes an issue when using spyscope as a lein user profile   * Author: Ryan Senior   * Company:   * Github ID: [senior|https://github.com/senior]  * [Pull Request 812 Discussion|https://github.com/puppetlabs/puppetdb/pull/812]  * [Pull Request 812 File Diff|https://github.com/puppetlabs/puppetdb/pull/812/files]  h2. Pull Request ...















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




 














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

Jira (FACT-243) PR (613): (RE-814) Add initial support for building in a RHEL 7 mock - mckern

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (613): (RE-814) Add initial support for building in a RHEL 7 mock - mckern 










Pull request (RE-814) Add initial support for building in a RHEL 7 mock has been closed.












   

 Add Comment











 













 Facter /  FACT-243



  PR (613): (RE-814) Add initial support for building in a RHEL 7 mock - mckern 







 h2. (RE-814) Add initial support for building in a RHEL 7 mock   * Author: Ryan McKern   * Company: Puppet Labs  * Github ID: [mckern|https://github.com/mckern]  * [Pull Request 613 Discussion|https://github.com/puppetlabs/facter/pull/613]  * [Pull Request 613 File Diff|https://github.com/puppetlabs/facter/pull/613/files]  h2. Pull Re...















 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-1406) PR (2236): Add ability to override default system confdir and vardir - jeffmccune

2014-01-22 Thread Andrew Parker (JIRA)

Title: Message Title










 

 Andrew Parker assigned an issue to Andrew Parker











 






 Puppet /  PUP-1406



  PR (2236): Add ability to override default system confdir and vardir - jeffmccune 










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 (FACT-243) PR (613): (RE-814) Add initial support for building in a RHEL 7 mock - mckern

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (613): (RE-814) Add initial support for building in a RHEL 7 mock - mckern 










mckern commented:
Added a note about x86_64 only.












   

 Add Comment











 













 Facter /  FACT-243



  PR (613): (RE-814) Add initial support for building in a RHEL 7 mock - mckern 







 h2. (RE-814) Add initial support for building in a RHEL 7 mock   * Author: Ryan McKern   * Company: Puppet Labs  * Github ID: [mckern|https://github.com/mckern]  * [Pull Request 613 Discussion|https://github.com/puppetlabs/facter/pull/613]  * [Pull Request 613 File Diff|https://github.com/puppetlabs/facter/pull/613/files]  h2. Pull Re...















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




 














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

Jira (FACT-243) PR (613): (RE-814) Add initial support for building in a RHEL 7 mock - mckern

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (613): (RE-814) Add initial support for building in a RHEL 7 mock - mckern 










haus commented:
@mckern probably worth noting why we're only adding x86_64












   

 Add Comment











 













 Facter /  FACT-243



  PR (613): (RE-814) Add initial support for building in a RHEL 7 mock - mckern 







 h2. (RE-814) Add initial support for building in a RHEL 7 mock   * Author: Ryan McKern   * Company: Puppet Labs  * Github ID: [mckern|https://github.com/mckern]  * [Pull Request 613 Discussion|https://github.com/puppetlabs/facter/pull/613]  * [Pull Request 613 File Diff|https://github.com/puppetlabs/facter/pull/613/files]  h2. Pull Re...















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




 














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

Jira (FACT-243) PR (613): (RE-814) Add initial support for building in a RHEL 7 mock - mckern

Title: Message Title










 

 gepetto-bot created an issue











 






 Facter /  FACT-243



  PR (613): (RE-814) Add initial support for building in a RHEL 7 mock - mckern 










Issue Type:

  Task




Assignee:

 Adrien Thebo




Components:


 Community




Created:


 22/Jan/14 4:48 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










(RE-814) Add initial support for building in a RHEL 7 mock


Author: Ryan McKern 


Company: Puppet Labs


Github ID: mckern


Pull Request 613 Discussion


Pull Request 613 File Diff


Pull Request Description

Jira (PUP-1411) Windows agents experience intermittent SSL_connect failures in acceptance testing

2014-01-22 Thread Joshua Cooper (JIRA)

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Windows agents experience intermittent SSL_connect failures in acceptance testing 










I believe that these failures have been triggered by the recent vsphere slowness, and unfortunately haven't been able to reproduce. However, I did add timing information to step where it always fails. The agent has taken between 5 and 25 seconds across different runs.


hmz8uryanqmjmca (master) $ env PATH="/usr/bin:/opt/puppet-git-repos/hiera/bin:${PATH}" RUBYLIB="/opt/puppet-git-repos/hiera/lib:/opt/puppet-git-repos/hiera-puppet/lib:${RUBYLIB}" puppet agent hmz8uryanqmjmca --test --server hmz8uryanqmjmca
Info: Retrieving plugin
Error: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve information from environment production source(s) puppet://hmz8uryanqmjmca/plugins
Info: Caching catalog for hmz8uryanqmjmca.delivery.puppetlabs.net
Info: Applying configuration version '1390435971'
Notice: Finished catalog run in 0.04 seconds
agent ran in 3.24 seconds





oy8kqjuc27nw07v $ env PATH="/opt/puppet-git-repos/hiera/bin:${PATH}" RUBYLIB="`cygpath -w /opt/puppet-git-repos/hiera/lib`;`cygpath -w /opt/puppet-git-repos/hiera-puppet/lib`;${RUBYLIB}" cmd.exe /c puppet agent oy8kqjuc27nw07v --test --server s75uqsxff1d711d
Info: Caching certificate for oy8kqjuc27nw07v.delivery.puppetlabs.net
Info: Caching certificate_revocation_list for ca
Info: Caching certificate for oy8kqjuc27nw07v.delivery.puppetlabs.net
Info: Retrieving plugin
Error: /File[C:/ProgramData/PuppetLabs/puppet/var/lib]: Could not evaluate: Could not retrieve information from environment production source(s) puppet://s75uqsxff1d711d/plugins
Info: Caching catalog for oy8kqjuc27nw07v.delivery.puppetlabs.net
Info: Applying configuration version '1390335419'
Notice: Finished catalog run in 1.51 seconds
agent ran in 22.64 seconds



I'm going to submit a PR to beaker to print diagnostic timing info for commands that it executes. I am also going to update the test to do agents.each do |agent| on(agent, puppet_agent...) instead of on(agents...)












   

 Add Comment

Jira (MCO-161) Investigate possible loss of parity between standard Puppet Labs packaging and "mco plugin package"

2014-01-22 Thread Matthaus Owens (JIRA)

Title: Message Title










 

 Matthaus Owens commented on an issue











 






  Re: Investigate possible loss of parity between standard Puppet Labs packaging and "mco plugin package" 










When putting together the pull request for the mcollective-package plugin, I made sure that the contents and dependencies of the packages were consistent with the output of the plugin packager. Moving forward this does mean that before releasing/shipping a plugin, the changes since the last release need to be reviewed to ensure that dependencies (either on mcollective itself or other libraries) haven't changed. However, that should be part of the release process already, so shouldn't pose any additional burden. This also means that the same care would need to be taken in moving other plugins to use our packaging tools.
So with the above in place the packages (both in content and metadata) will be consistent between the plugin packager and the Puppet Labs packaging tools. I absolutely want users to have consistent packages available to them, but we can ensure that package consistency without using the same tools.












   

 Add Comment











 













 MCollective /  MCO-161



  Investigate possible loss of parity between standard Puppet Labs packaging and "mco plugin package" 







 User feedback has brought up the fact that if plugin packaging moves to the standard Puppet Labs packaging methods "mco plugin package" becomes devalued.   We need to have the discussion here if we should review moving forward with standardising packaging or move back to using "mco plugin package".















 This message wa

Jira (PDB-312) PR (802): Convert unit testing to use dynamic postgres instance - kbarber

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: PR (802): Convert unit testing to use dynamic postgres instance - kbarber 










At the end of the day I wouldn't object to trialing it for a while then reverting if the idea is crap . I wouldn't put up with a crap solution anyway, at the end of the day if this is bad I suffer as well . The only other risk is to your slave I guess, but we can monitor that closely and see how it goes, I think this is the most critical piece. Generally we only run 1 test at a time per branch, so at best 3.












   

 Add Comment











 













 PuppetDB /  PDB-312



  PR (802): Convert unit testing to use dynamic postgres instance - kbarber 







 h2. Convert unit testing to use dynamic postgres instance   * Author: Ken Barber   * Company: Puppetlabs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 802 Discussion|https://github.com/puppetlabs/puppetdb/pull/802]  * [Pull Request 802 File Diff|https://github.com/puppetlabs/puppetdb/pull/802/files]  h2. Pull Request...















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




 














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

Jira (PUP-845) Create a windows provider

2014-01-22 Thread Rob Reynolds (JIRA)

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-845



  Create a windows provider 










Change By:

 Rob Reynolds




Sprint:

 Week 2014-1-22 to 2014-1-29












   

 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-844) Create basic acl type

2014-01-22 Thread Rob Reynolds (JIRA)

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-844



  Create basic acl type 










Change By:

 Rob Reynolds




Sprint:

 Week 2014-1-22 to 2014-1-29












   

 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-312) PR (802): Convert unit testing to use dynamic postgres instance - kbarber

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: PR (802): Convert unit testing to use dynamic postgres instance - kbarber 










Branan Purvine-Riley it crashes regularly putting the FS into read-only mode. Its been doing that for months.












   

 Add Comment











 













 PuppetDB /  PDB-312



  PR (802): Convert unit testing to use dynamic postgres instance - kbarber 







 h2. Convert unit testing to use dynamic postgres instance   * Author: Ken Barber   * Company: Puppetlabs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 802 Discussion|https://github.com/puppetlabs/puppetdb/pull/802]  * [Pull Request 802 File Diff|https://github.com/puppetlabs/puppetdb/pull/802/files]  h2. Pull Request...















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




 














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

Jira (PUP-312) Get MSI packages so that we can test windows against packages.

2014-01-22 Thread Michelle Johansen (JIRA)

Title: Message Title










 

 Michelle Johansen commented on an issue











 






  Re: Get MSI packages so that we can test windows against packages. 










Matthaus Owens and Joshua Cooper Do we still need more information on this one? Any forward progress yet? 












   

 Add Comment











 













 Puppet /  PUP-312



  Get MSI packages so that we can test windows against packages. 







 Need to check with delivery and see if the pipeline can produce msi packages.   * need to move to using re's packaging system (generate MSI on commit)  * be able to build stable vs master puppet with appropriately versioned MSIs so that they don't collide on builds.puppetlabs.lan (sha based on the installer not puppet)  * ideally, wix packaging files sho...















 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-344) Latests docs point to unreleased version

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Latests docs point to unreleased version 










Nicholas Fagerlund so dude, this is an interesting one. Up until now we haven't hit this because we've not been releasing RC's but this time trying to be clever we have released the 1.6 branch of docs ahead of time while we do RC's.
The does create the problem whereby the 'latest' is interpreted as '1.6', which is obviously throwing people. We state on the 1.6 page that is not the latest and to click -> here, but of course that brings you right back again.
Any thoughts on this? Perhaps putting something in front of the 1.6 to lower its rating to your 'latest' calculation? Like rc-1.6? What would bother me about such a solution would be the fact that upon final release this would change the link .












   

 Add Comment











 













 PuppetDB /  PDB-344



  Latests docs point to unreleased version 







 Currently the {{/latest}} point to PuppetDB 1.6 docs but PuppetDB hasn't been released yet. I understand that {{/latest}} is being interpreted as bleeding edge but when you do a search on Google for {{puppetdb docs}} the first hit is {{/latest}}.   This is causing people confusion:  {quote}  20:15:03 Phibs | or I guess 1.6 isn't 'released' yet  ...















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

Jira (PDB-312) PR (802): Convert unit testing to use dynamic postgres instance - kbarber

2014-01-22 Thread Branan Purvine-Riley (JIRA)

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: PR (802): Convert unit testing to use dynamic postgres instance - kbarber 










we actually can't decommission vor, we use it for unit testing the dashboard on the PE side of things. Though if this pattern works out we could switch that over as well.
What sorts of faults are you seeing in vor, though? Ideally we want to spend time stabilizing our infra, not working around it.












   

 Add Comment











 













 PuppetDB /  PDB-312



  PR (802): Convert unit testing to use dynamic postgres instance - kbarber 







 h2. Convert unit testing to use dynamic postgres instance   * Author: Ken Barber   * Company: Puppetlabs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 802 Discussion|https://github.com/puppetlabs/puppetdb/pull/802]  * [Pull Request 802 File Diff|https://github.com/puppetlabs/puppetdb/pull/802/files]  h2. Pull Request...















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




 














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

Jira (PDB-312) PR (802): Convert unit testing to use dynamic postgres instance - kbarber

Title: Message Title

Kenneth Barber commented on an issue

Re: PR (802): Convert unit testing to use dynamic postgres instance - kbarber

So whats going on is that we're seeing a lot of faults on vor.puppetlabs.lan. This solution is a kind of work-around to allow us to fire up our own postgresql instance on the unit testing slave itself. Thus removing dependence on that stack 'vor' host.
So really this is a bit of a proposal ... there are other ideas as well, like ec2 hosting (prefer to host the db close to the testing host though) using RDS we however have the limitation of being stuck on 'their db'. We see some benefit in having our own managed postgresql instance, as then we can start to fire up separate version of postgresql (we just need the binaries to do this).
Having the test maintain the db keeps that in the control of the tester, its quite nice really. And what's more, when the test isn't running the database is down so its not consuming space for nothing.
If its a good idea, then it involves the installation of postgresql binaries (no running service) on the test slave(s) where this test would run (bor I think?). You could then decommission vor.puppetlabs.lan.
Let me know if that doesn't make sense .

Add Comment

PuppetDB / PDB-312

PR (802): Convert unit testing to use dynamic postgres instance - kbarber

h2. Convert unit testing to use dynamic postgres instance * Author: Ken Barber * Company: Puppetlabs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 802 Discussion|https://github.com/puppetlabs/puppetdb/pull/802] * [Pull Request 802 File Diff|https://github.com/puppetlabs/puppetdb/pull/802/files] h2. Pull Request...

Jira (PDB-341) Select-resources subquery strange behavior

Title: Message Title










 

 Kenneth Barber assigned an issue to Kenneth Barber











 






 PuppetDB /  PDB-341



  Select-resources subquery strange behavior  










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-434) Puppet does not accurately capture exit codes from exec resources on Windows

2014-01-22 Thread Rob Reynolds (JIRA)

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-434



  Puppet does not accurately capture exit codes from exec resources on Windows 










Change By:

 Rob Reynolds




Security:

 Internal












   

 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-1406) PR (2236): Add ability to override default system confdir and vardir - jeffmccune

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2236): Add ability to override default system confdir and vardir - jeffmccune 










jeffmccune commented:
If it might help, here's the Gem that I've written that takes advantage of this API in order to install the official, released puppet gem and have it automatically relocated.
This gem demonstrates the approach required without this patch applied, directly patching `run_mode.rb`, and the improved approach of using the public API to relocate an officially released Gem.


[puppet_transplant documentation](http://rubydoc.info/github/jeffmccune/puppet_transplant/master/frames)


[specific use of the public API contained in this pull request](https://github.com/jeffmccune/puppet_transplant/blob/8d6b1c8a452942a6f88dee5e2c3ef9b1fd71fa77/lib/puppet_transplant/installer.rb#L77)














   

 Add Comment











 













 Puppet /  PUP-1406



  PR (2236): Add ability to override default system confdir and vardir - jeffmccune 







 h2. Add ability to override default system confdir and vardir   * Author: Jeff McCune   * Company: Puppet Labs  * Github ID: [jeffmccune|https://github.com/jeffmccune]  * [Pull Request 2236 Discussion|https://github.com/puppetlabs/puppet/pull/2236]  * [Pull Request 2236 File Diff|https://github.com/puppetlabs/puppet/pull/2236/files]  ...

Jira (FACT-90) (#22944) External facts are evaluated many times

2014-01-22 Thread Stefan Schulte (JIRA)

Title: Message Title










 

 Stefan Schulte updated an issue











 






 Facter /  FACT-90



  (#22944) External facts are evaluated many times 










Change By:

 Stefan Schulte









 **  Reproduction  ** : # Drop script {{/etc/facter/facts.d/test.sh}}:{noformat}#!/bin/bashecho "SCRIPT CALLED" >&2echo "test=value"{noformat}# Make script executeable{noformat}chmod +x /etc/facter/facts.d/test.sh{noformat}Call {{facter}}, the following output is shown:{noformat}root@puppet:~# facterSCRIPT CALLEDSCRIPT CALLEDSCRIPT CALLEDSCRIPT CALLEDSCRIPT CALLEDSCRIPT CALLED...Regular facter output...{noformat}I don't see a reason why the script is called 6 times.System information* Ubuntu 12.04.3* Facter 1.7.3












   

 Add Comment











 










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




 














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

Jira (FACT-90) (#22944) External facts are evaluated many times

2014-01-22 Thread Stefan Schulte (JIRA)

Title: Message Title










 

 Stefan Schulte updated an issue











 






 Facter /  FACT-90



  (#22944) External facts are evaluated many times 










Change By:

 Stefan Schulte









 ** Reproduction ** * #  Drop script  {{  /etc/facter/facts.d/test.sh }} :  {noformat} #!/bin/bashecho "SCRIPT CALLED" >&2echo "test=value"  {noformat}  * #  Make script executeable  {noformat} chmod +x /etc/facter/facts.d/test.sh  {noformat}  *  Call  '  {{ facter ' }} , the following output is shown:  {noformat} root@puppet:~# facterSCRIPT CALLEDSCRIPT CALLEDSCRIPT CALLEDSCRIPT CALLEDSCRIPT CALLEDSCRIPT CALLED...Regular facter output...  {noformat} I don't see a reason why the script is called 6 times.System information* Ubuntu 12.04.3* Facter 1.7.3












   

 Add Comment











 










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




 














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

Jira (PUP-1406) PR (2236): Add ability to override default system confdir and vardir - jeffmccune

2014-01-22 Thread Andrew Parker (JIRA)

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-1406



  PR (2236): Add ability to override default system confdir and vardir - jeffmccune 










Change By:

 Andrew Parker




Sprint:

 Week 2014-1-15 to 2014-1-22












   

 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-312) PR (802): Convert unit testing to use dynamic postgres instance - kbarber

2014-01-22 Thread Branan Purvine-Riley (JIRA)

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: PR (802): Convert unit testing to use dynamic postgres instance - kbarber 










Kenneth Barber So Michelle assigned this to QA, but I'm not sure you need me here? What's the status of things? Do you just need a code review? Infra changes to make sure postgres is on your test servers?












   

 Add Comment











 













 PuppetDB /  PDB-312



  PR (802): Convert unit testing to use dynamic postgres instance - kbarber 







 h2. Convert unit testing to use dynamic postgres instance   * Author: Ken Barber   * Company: Puppetlabs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 802 Discussion|https://github.com/puppetlabs/puppetdb/pull/802]  * [Pull Request 802 File Diff|https://github.com/puppetlabs/puppetdb/pull/802/files]  h2. Pull Request...















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




 














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

Jira (PUP-1147) Strange behaviour with file backup and purge

2014-01-22 Thread Charlie Sharpsteen (JIRA)

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1147



  Strange behaviour with file backup and purge 










Change By:

 Charlie Sharpsteen









 Create this manifest: {code} $backup = '.old'$fragdir = '/tmp/bug'File {  backup => $backup}file { $fragdir:  ensure => directory,}file { "${fragdir}/fragments":  ensure   => directory,  force=> true,  purge=> true,  recurse  => true,}file { "${fragdir}/fragments/file.a":  ensure   => present,  content  => 'Filename = file.a',}file { "${fragdir}/fragments/file.b":  ensure   => present,  content  => 'Filename = file.b',} {code}   Run it {code} $ puppet apply {code}   Check result {code} $ find /tmp/bug/tmp/bug//tmp/bug/fragments/tmp/bug/fragments/file.a/tmp/bug/fragments/file.b {code}   Remove the last file statement i.e remove file.b from the manifest.Rerun the manifest {code} $ puppet apply {code}   Check result {code} $ find /tmp/bug/tmp/bug//tmp/bug/fragments/tmp/bug/fragments/file.a/tmp/bug/fragments/file.b.old {code}   Rerun yet another time {code} $ puppet apply {code}   Check result {code} $ find /tmp/bug/tmp/bug//tmp/bug/fragments/tmp/bug/fragments/file.a/tmp/bug/fragments/file.b.old.old {code}   File file.b will get yet another .old tagged on for each new run. 












   

 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 htt

Jira (PUP-1492) Spec failures on Arch Linux if yaourt is installed

2014-01-22 Thread Peter Huene (JIRA)

Title: Message Title










 

 Peter Huene created an issue











 






 Puppet /  PUP-1492



  Spec failures on Arch Linux if yaourt is installed 










Issue Type:

  Task




Affects Versions:


 3.5.0




Assignee:

 Peter Huene




Created:


 22/Jan/14 11:33 AM




Environment:


ArchLinux




Priority:

  Normal




Reporter:

 Peter Huene










If yaourt is installed on Arch Linux, the pacman package provider will execute it instead of pacman. This results in failures for two specs that assume pacman will be run:
1) Puppet::Type::Package::ProviderPacman when installing should call pacman to install the right package quietly Failure/Error: @provider.install Mocha::ExpectationError: unexpected invocation: Puppet::Util.which('/usr/bin/yaourt') unsatisfied expectations:


expected at least once, not yet invoked: Puppet::Util::Execution.execute(['/usr/bin/pacman', '--noconfirm', '--noprogressbar', '-Sy', 'package'], {:failonfail => true, :combine => true, :custom_environment => {}}) satisfied expectations:


allowed any number of times, not yet invoked: Signal.trap(any_parameters)

Jira (PUP-1492) Spec failures on Arch Linux if yaourt is installed

2014-01-22 Thread Peter Huene (JIRA)

Title: Message Title










 

 Peter Huene updated an issue











 






 Puppet /  PUP-1492



  Spec failures on Arch Linux if yaourt is installed 










Change By:

 Peter Huene









 If yaourt is installed on Arch Linux, the pacman package provider will execute it instead of pacman.  This results in failures for two specs that assume pacman will be run: {code} 1) Puppet::Type::Package::ProviderPacman when installing should call pacman to install the right package quietly Failure/Error: @provider.install Mocha::ExpectationError:   unexpected invocation: Puppet::Util.which('/usr/bin/yaourt')   unsatisfied expectations:   - expected at least once, not yet invoked: Puppet::Util::Execution.execute(['/usr/bin/pacman', '--noconfirm', '--noprogressbar', '-Sy', 'package'], {:failonfail => true, :combine => true, :custom_environment => {}})   satisfied expectations:   - allowed any number of times, not yet invoked: Signal.trap(any_parameters)   - allowed any number of times, not yet invoked: Puppet::Util.which('/usr/bin/pacman')   - allowed any number of times, not yet invoked: Puppet::Type::Package::ProviderPacman.which('/usr/bin/pacman')   - allowed any number of times, not yet invoked: #.query(any_parameters) # ./lib/puppet/provider/command.rb:22:in `execute' # ./lib/puppet/provider.rb:237:in `block in has_command' # ./lib/puppet/provider.rb:444:in `block in create_class_and_instance_method' # ./lib/puppet/provider/package/pacman.rb:37:in `install_from_repo' # ./lib/puppet/provider/package/pacman.rb:27:in `install' # ./spec/unit/provider/package/pacman_spec.rb:33:in `block (3 levels) in 2) Puppet::Type::Package::ProviderPacman when installing should raise an ExecutionFailure if the installation failed Failure/Error: lambda { @provider.install }.should raise_exception(Puppet::ExecutionFailure)   expected Puppet::ExecutionFailure, got #   unsatisfied expectations:   - expected exactly once, not yet invoked: #.query(any_parameters)   satisfied expectations:   - allowed any number of times, not yet invoked: Signal.trap(any_parameters)   - allowed any number of times, not yet invoked: Puppet::Util.which('/usr/bin/pacman')   - allowed any number of times, not yet invoked: Puppet::Type::Package::ProviderPacman.which('/usr/bin/pacman')   - allowed any number of times, not yet invoked: #.query(any_parameters)   - allowed any number of times, not yet invoked: Puppet::Util::Execution.execute(any_parameters)   > # ./spec/unit/provider/package/pacman_spec.rb:40:in `block (3 levels) in ' {code}












   

 Add Comment

Jira (HI-140) Smoke test packages

2014-01-22 Thread Melissa Stone (JIRA)

Title: Message Title










 

 Melissa Stone commented on an issue











 






  Re: Smoke test packages 










Henrik Lindberg per the issue with a lack of man pages for hiera: HI-114. It looks like this hasn't been resolved yet. So I suppose just validate basic functionality, and make a note on the ticket (HI-114) about which platforms do and do not have man pages.












   

 Add Comment











 













 Hiera /  HI-140



  Smoke test packages 







 Procedure may vary by project and point in the release cycle. Ask around.   * Centos 5/6  * Debian Squeeze/Wheezy  * Ubuntu Lucid/Precise  * Gem  * dmg   Check that  * hiera is available.  * man hiera (except for gems)















 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-1241) netbsd support

2014-01-22 Thread Charlie Sharpsteen (JIRA)

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1241



  netbsd support 










Change By:

 Charlie Sharpsteen









 So far NetBSD basically works but the first hurdle is finding a working user provider.useradd works except for 'chage'.  usermod the same stuff as chage, but might be less convenient.I patched useradd.rb to make useradd_netbsd.rb like this* but I was wondering if there wasn't an easier way to override has_features or have usermod as an alternative to chage.*  {code} --- useradd.rb  2012-03-24 08:04:50.0 -0400+++ useradd_netbsd.rb   2012-04-02 19:37:19.0 -0400@@ -1,17 +1,17 @@ require 'puppet/provider/nameservice/objectadd' -Puppet::Type.type(:user).provide :useradd, :parent => Puppet::Provider::NameService::ObjectAdd do+Puppet::Type.type(:user).provide :useradd_netbsd, :parent => Puppet::Provider::NameService::ObjectAdd do   desc "User management via `useradd` and its ilk.  Note that you will need to install Ruby's shadow password library (often known as `ruby-libshadow`) if you wish to manage user passwords." -  commands :add => "useradd", :delete => "userdel", :modify => "usermod", :password => "chage"+  commands :add => "useradd", :delete => "userdel", :modify => "usermod", :password => "usermod"options :home, :flag => "-d", :method => :dir   options :comment, :method => :gecos   options :groups, :flag => "-G"-  options :password_min_age, :flag => "-m"-  options :password_max_age, :flag => "-M"+  options :password_min_age, :flag => "-e"+  options :password_max_age, :flag => "-f"verify :gid, "GID must be an integer" do |value| value.is_a? Integer@@ -23,7 +23,7 @@has_features :manages_homedir, :allows_duplicates, :manages_expiry, :system_users -  has_features :manages_passwords, :manages_password_age if Puppet.features.libshadow?+#  has_features :manages_passwords, :manages_password_age if Puppet.features.libshadow?def check_allow_dup @resource.allowdupe? ? ["-o"] : []  {code}












   

 Add Comment











 










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

Jira (PDB-344) Latests docs point to unreleased version

2014-01-22 Thread Daniele Sluijters (JIRA)

Title: Message Title










 

 Daniele Sluijters created an issue











 






 PuppetDB /  PDB-344



  Latests docs point to unreleased version 










Issue Type:

  Bug




Assignee:


 Unassigned




Components:


 DOCS




Created:


 22/Jan/14 11:21 AM




Labels:


 puppetdb




Priority:

  Normal




Reporter:

 Daniele Sluijters










Currently the /latest point to PuppetDB 1.6 docs but PuppetDB hasn't been released yet. I understand that /latest is being interpreted as bleeding edge but when you do a search on Google for puppetdb docs the first hit is /latest.
This is causing people confusion:

20:15:03 Phibs | or I guess 1.6 isn't 'released' yet 20:15:23 Phibs | even though latest official release points @ 1.6 on the docs













   

 Add Comment

Jira (PDB-322) Smoke test packages

2014-01-22 Thread Melissa Stone (JIRA)

Title: Message Title










 

 Melissa Stone commented on an issue











 






  Re: Smoke test packages 










Just a nitpick, next time could you include the steps you used to smoke test the packages? Just so we can look back and know what exactly we tested. Thanks!












   

 Add Comment











 













 PuppetDB /  PDB-322



  Smoke test packages 














 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-140) Smoke test packages

2014-01-22 Thread Melissa Stone (JIRA)

Title: Message Title










 

 Melissa Stone updated an issue











 






 Hiera /  HI-140



  Smoke test packages 










Change By:

 Melissa Stone









 Procedure may vary by project and point in the release cycle. Ask around.* Centos 5/6* Debian Squeeze/Wheezy* Ubuntu Lucid/Precise* Gem * dmg   Check that* hiera is available.* man hiera (except for gems)












   

 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-778) PR (2086): Initial refactoring of yumrepo. - apenney

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2086): Initial refactoring of yumrepo. - apenney 










unux commented:
@apenney from the yum config parser: http://yum.baseurl.org/gitweb?p=yum.git;a=blob;f=yum/config.py#l387
 class BoolOption(Option): """An option representing a boolean value. The value can be one of 0, 1, yes, no, true, or false. """
Seems like yum's boolean options also take yes and no in addition to (0|1|false|true). This might be worth expanding into the rest of yumrepos options.












   

 Add Comment











 













 Puppet /  PUP-778



  PR (2086): Initial refactoring of yumrepo. - apenney 







 h2. Initial refactoring of yumrepo.   * Author: Ashley Penney   * Company: Puppetlabs  * Github ID: [apenney|https://github.com/apenney]  * [Pull Request 2086 Discussion|https://github.com/puppetlabs/puppet/pull/2086]  * [Pull Request 2086 File Diff|https://github.com/puppetlabs/puppet/pull/2086/files]  h2. Pull Request Descr...















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




 














-- 
You received this mes

Jira (PUP-778) PR (2086): Initial refactoring of yumrepo. - apenney

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2086): Initial refactoring of yumrepo. - apenney 










apenney commented:
A, nice, I didn't look in config.py, I had only got as far as repo.py. That'll teach me. I'll fix this globally.












   

 Add Comment











 













 Puppet /  PUP-778



  PR (2086): Initial refactoring of yumrepo. - apenney 







 h2. Initial refactoring of yumrepo.   * Author: Ashley Penney   * Company: Puppetlabs  * Github ID: [apenney|https://github.com/apenney]  * [Pull Request 2086 Discussion|https://github.com/puppetlabs/puppet/pull/2086]  * [Pull Request 2086 File Diff|https://github.com/puppetlabs/puppet/pull/2086/files]  h2. Pull Request Descr...















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




 














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

Jira (PDB-314) Release 1.6.0rc3 - January 22nd 2014

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-314



  Release 1.6.0rc3 - January 22nd 2014 










Change By:

 Kenneth Barber




Summary:

 Release 1.6.0rc3 -  TBA  January 22nd 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-1462) PR (2268): Ccin2p3 yumrepo repo gpgcheck - riton

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2268): Ccin2p3 yumrepo repo gpgcheck - riton 










apenney commented:
I would like to fold this into #2086 if you're OK with this. I can either do a stellar cut and paste job, or if you want you could rebase this against that PR and send me a PR and I'll merge it in so you retain credit. I've split yumrepo into a type/provider so I want to make sure this gets included with that work.












   

 Add Comment











 













 Puppet /  PUP-1462



  PR (2268): Ccin2p3 yumrepo repo gpgcheck - riton 







 h2. Ccin2p3 yumrepo repo gpgcheck   * Author: Remi Ferrand <>  * Company: IN2P3 Computing Centre  * Github ID: [riton|https://github.com/riton]  * [Pull Request 2268 Discussion|https://github.com/puppetlabs/puppet/pull/2268]  * [Pull Request 2268 File Diff|https://github.com/puppetlabs/puppet/pull/2268/files]  h2. Pull Request Description   Add suppor...















 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 pupp

Jira (PUP-1490) Support --test option for puppet apply

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1490



  Support --test option for puppet apply 










Change By:

 Kylo Ginsberg




Story Points:

 1












   

 Add Comment











 










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




 














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

Jira (PUP-1491) (packaging)Remove Fedora 18 from default mocks

2014-01-22 Thread Joshua Partlow (JIRA)

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: (packaging)Remove Fedora 18 from default mocks 










Merged to master in 31ffec7












   

 Add Comment











 













 Puppet /  PUP-1491



  (packaging)Remove Fedora 18 from default mocks 







 Fedora 18 reached end-of-life on January 14, 2014. Remove Fedora 18 from the list of default package build mocks. The F18 yum repos will be removed from yum.puppetlabs.com on March 18.















 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-1490) Support --test option for puppet apply

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1490



  Support --test option for puppet apply 










Change By:

 Kylo Ginsberg




Sprint:

 Week 2014-1-15 to 2014-1-21












   

 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-1487) PR (2284): (maint) Remove Fedora 18 as a default build target - shrug

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2284): (maint) Remove Fedora 18 as a default build target - shrug 










Pull request (pup-1491) (packaging) Remove Fedora 18 as a default build target has been closed.












   

 Add Comment











 













 Puppet /  PUP-1487



  PR (2284): (maint) Remove Fedora 18 as a default build target - shrug 







 h2. (maint) Remove Fedora 18 as a default build target   * Author: <>  * Company:   * Github ID: [shrug|https://github.com/shrug]  * [Pull Request 2284 Discussion|https://github.com/puppetlabs/puppet/pull/2284]  * [Pull Request 2284 File Diff|https://github.com/puppetlabs/puppet/pull/2284/files]  h2. Pull Request Description   Fedora 18 reached end-o...















 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-343) (packaging) Remove Fedora 18 from default build targets

Title: Message Title










 

 Rob Braden created an issue











 






 PuppetDB /  PDB-343



  (packaging) Remove Fedora 18 from default build targets 










Issue Type:

  Task




Assignee:

 Rob Braden




Created:


 22/Jan/14 9:47 AM




Priority:

  Normal




Reporter:

 Rob Braden










Fedora 18 reached end-of-life on January 14, 2014. Remove Fedora 18 from the list of default package build mocks. The F18 yum repos will be removed from yum.puppetlabs.com on March 18.












   

 Add Comment











 










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

Jira (PUP-1490) Support --test option for puppet apply

Title: Message Title










 

 Kylo Ginsberg assigned an issue to Kylo Ginsberg











 






 Puppet /  PUP-1490



  Support --test option for puppet apply 










Change By:

 Kylo Ginsberg




Assignee:

 Kylo Ginsberg












   

 Add Comment











 










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




 














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

Jira (FACT-242) (packaging) Remove Fedora 18 from default build targets

Title: Message Title










 

 Rob Braden updated an issue











 






 Facter /  FACT-242



  (packaging) Remove Fedora 18 from default build targets 










Change By:

 Rob Braden









 Fedora 18 reached end-of-life on January 14, 2014. Remove Fedora 18 from the list of default package build mocks. The F18 yum repos will be removed from yum.puppetlabs.com on March 18.












   

 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-1491) (packaging)Remove Fedora 18 from default mocks

Title: Message Title










 

 Rob Braden updated an issue











 






 Puppet /  PUP-1491



  (packaging)Remove Fedora 18 from default mocks 










Change By:

 Rob Braden




Summary:

 (packaging) Remove Fedora 18 from default mocks












   

 Add Comment











 










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




 














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

Jira (MCO-166) (packaging) Remove Fedora 18 from default build targets

Title: Message Title










 

 Rob Braden created an issue











 






 MCollective /  MCO-166



  (packaging) Remove Fedora 18 from default build targets 










Issue Type:

  Task




Assignee:

 Rob Braden




Created:


 22/Jan/14 9:44 AM




Priority:

  Normal




Reporter:

 Rob Braden










Fedora 18 reached end-of-life on January 14, 2014. Remove Fedora 18 from the list of default package build mocks. The F18 yum repos will be removed from yum.puppetlabs.com on March 18.












   

 Add Comment











 










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

Jira (HI-149) (packaging) Remove Fedora 18 from default build targets

Title: Message Title










 

 Rob Braden created an issue











 






 Hiera /  HI-149



  (packaging) Remove Fedora 18 from default build targets 










Issue Type:

  Task




Assignee:

 Rob Braden




Created:


 22/Jan/14 9:46 AM




Priority:

  Normal




Reporter:

 Rob Braden










Fedora 18 reached end-of-life on January 14, 2014. Remove Fedora 18 from the list of default package build mocks. The F18 yum repos will be removed from yum.puppetlabs.com on March 18.












   

 Add Comment











 










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

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

Title: Message Title










 

 gepetto-bot commented on an issue











 






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










hlindberg commented:
We have now talked about this PR in community triage, and concluded we do need to take a bigger grip on the backwards compatibility of stdlib. As things stand right now it is not possible to support multiple versions. Once that has been resolved (discussions and design) we can come back to the set of is_xxx functions. The idea is that we can support a maintained (backwards compatible) stdlib, as well as corrected version. Going forward we may also need to support a 3x compatibility version (for code not migrated to Puppet 4). Anyway - I am jumping ahead in that discussion (which will take place on puppet-dev).












   

 Add Comment











 













 Puppet /  PUP-1195



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







 h2. fix is_numeric/is_integer when checking non-string parameters   * Author: Simon Effenberg <>  * Company:   * Github ID: [Savar|https://github.com/Savar]  * [Pull Request 213 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213]  * [Pull Request 213 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213/files]  h2. Pull Reque...















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

Jira (FACT-242) (packaging) Remove Fedora 18 from default build targets

Title: Message Title










 

 Rob Braden created an issue











 






 Facter /  FACT-242



  (packaging) Remove Fedora 18 from default build targets 










Issue Type:

  Task




Assignee:

 Rob Braden




Created:


 22/Jan/14 9:41 AM




Priority:

  Normal




Reporter:

 Rob Braden












   

 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-1491) Remove Fedora 18 from default mocks

Title: Message Title










 

 Rob Braden assigned an issue to Rob Braden











 






 Puppet /  PUP-1491



  Remove Fedora 18 from default mocks 










Change By:

 Rob Braden




Assignee:

 Eric Sorenson Rob Braden












   

 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-1491) Remove Fedora 18 from default mocks

Title: Message Title










 

 Rob Braden created an issue











 






 Puppet /  PUP-1491



  Remove Fedora 18 from default mocks 










Issue Type:

  Task




Assignee:

 Eric Sorenson




Created:


 22/Jan/14 9:18 AM




Priority:

  Normal




Reporter:

 Rob Braden










Fedora 18 reached end-of-life on January 14, 2014. Remove Fedora 18 from the list of default package build mocks. The F18 yum repos will be removed from yum.puppetlabs.com on March 18.












   

 Add Comment











 










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




 














-- 
You receiv

Jira (PUP-638) PR (198): Modify pick() to always return a value. - DavidS

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (198): Modify pick() to always return a value. - DavidS 










zaphod42 commented:
@example42 @DavidS any progress on this?












   

 Add Comment











 













 Puppet /  PUP-638



  PR (198): Modify pick() to always return a value. - DavidS 







 h2. Modify pick() to always return a value.   * Author: David Schmitt   * Company: dasz.at OG  * Github ID: [DavidS|https://github.com/DavidS]  * [Pull Request 198 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/198]  * [Pull Request 198 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/198/files]  h2. Pull Requ...















 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-1342) PR (2212): Updates to ext/suse init and spec files - benkevan

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2212): Updates to ext/suse init and spec files - benkevan 










zaphod42 commented:
@haus do you have all of the information you need now?












   

 Add Comment











 













 Puppet /  PUP-1342



  PR (2212): Updates to ext/suse init and spec files - benkevan 







 h2. Updates to ext/suse init and spec files   * Author: Ben Kevan <>  * Company:   * Github ID: [benkevan|https://github.com/benkevan]  * [Pull Request 2212 Discussion|https://github.com/puppetlabs/puppet/pull/2212]  * [Pull Request 2212 File Diff|https://github.com/puppetlabs/puppet/pull/2212/files]  h2. Pull Request Description   The removal of chan...















 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-1438) puppet resource does not handle yum repo files with white space

2014-01-22 Thread lee loucks (JIRA)

Title: Message Title










 

 lee loucks commented on an issue











 






  Re: puppet resource does not handle yum repo files with white space 










Pull Request 2288
https://github.com/puppetlabs/puppet/pull/2288












   

 Add Comment











 













 Puppet /  PUP-1438



  puppet resource does not handle yum repo files with white space 







 When running:  {quote}  puppet resource yumrepo epel  {quote}  puppet reports  {color:red}  Error: Could not run: Invalid value " 1". Valid values are absent. Valid values match /^(0|1)$/.  {color}   This is because a Yum repository file contains white space between the equals and the 0 or the 1 for enabled or disabled. Like this  {quote}  [rhel-6-server...















 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-312) PR (802): Convert unit testing to use dynamic postgres instance - kbarber

2014-01-22 Thread John Duarte (JIRA)

Title: Message Title










 

 John Duarte updated an issue











 






 PuppetDB /  PDB-312



  PR (802): Convert unit testing to use dynamic postgres instance - kbarber 










Change By:

 John Duarte




Assignee:

 QA 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 (PDB-308) Drop 2.7.x support for puppetdb-terminus

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-308



  Drop 2.7.x support for puppetdb-terminus 










Change By:

 Kenneth Barber









 We would like to drop 2.7.x support from puppetdb-terminus for 2.0.0 if possible. This would allow us to drop the Ruby 1.8.5 tests as well.   We should consider what minimum puppet version we support as part of this also going forward, as this might not include older 3.x revisions, but where we draw the line is yet to be determined. This involves:* test matrix modfication* throwing an error on unsupported puppets* new methods in puppet that are 3.x (this might be a new ticket?) that we should start using












   

 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-228) PR (776): (#23422) Use JSON in terminus instead of PSON - dalen

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (776): (#23422) Use JSON in terminus instead of PSON - dalen 










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












   

 Add Comment











 













 PuppetDB /  PDB-228



  PR (776): (#23422) Use JSON in terminus instead of PSON - dalen 







 h2. (#23422) Use JSON in terminus instead of PSON   * Author: Erik Dalén   * Company: Spotify  * Github ID: [dalen|https://github.com/dalen]  * [Pull Request 776 Discussion|https://github.com/puppetlabs/puppetdb/pull/776]  * [Pull Request 776 File Diff|https://github.com/puppetlabs/puppetdb/pull/776/files]  h2. Pull Request De...















 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 (PDB-234) Create v4 API

Title: Message Title










 

 Deepak Giridharagopal updated an issue











 






 PuppetDB /  PDB-234



  Create v4 API 










Change By:

 Deepak Giridharagopal




Sprint:

 20140122 to  20140129  to 20140205












   

 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-312) PR (802): Convert unit testing to use dynamic postgres instance - kbarber

2014-01-22 Thread Michelle Johansen (JIRA)

Title: Message Title










 

 Michelle Johansen updated an issue











 






 PuppetDB /  PDB-312



  PR (802): Convert unit testing to use dynamic postgres instance - kbarber 










Change By:

 Michelle Johansen




Assignee:

 QA












   

 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-342) Add acceptance testing for Oracle JDK 7

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-342



  Add acceptance testing for Oracle JDK 7 










Change By:

 Kenneth Barber




Sprint:

 20140129 to 20140205












   

 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-312) PR (802): Convert unit testing to use dynamic postgres instance - kbarber

2014-01-22 Thread Michelle Johansen (JIRA)

Title: Message Title










 

 Michelle Johansen updated an issue











 






 PuppetDB /  PDB-312



  PR (802): Convert unit testing to use dynamic postgres instance - kbarber 










Change By:

 Michelle Johansen




Component/s:

 QA












   

 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-88) Remove JDK 1.6 Support

Title: Message Title










 

 Deepak Giridharagopal updated an issue











 






 PuppetDB /  PDB-88



  Remove JDK 1.6 Support 










Change By:

 Deepak Giridharagopal




Sprint:

 20131218 to 20140101, 20140108 to 20140115,  20140122 to  20140129  to 20140205












   

 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-342) Add acceptance testing for Oracle JDK 7

Title: Message Title










 

 Kenneth Barber created an issue











 






 PuppetDB /  PDB-342



  Add acceptance testing for Oracle JDK 7 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 22/Jan/14 8:32 AM




Fix Versions:


 1.6.x




Priority:

  Normal




Reporter:

 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 a

Jira (PDB-128) Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-128



  Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid 










Change By:

 Kenneth Barber




Story Points:

 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 (PDB-336) Investigage - PuppetDB won't start: OutOfMemoryError: Java heap space

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-336



  Investigage - PuppetDB won't start: OutOfMemoryError: Java heap space 










Change By:

 Kenneth Barber




Summary:

 Investigage - PuppetDB won't start: OutOfMemoryError: Java heap space












   

 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-336) PuppetDB won't start: OutOfMemoryError: Java heap space

Title: Message Title










 

 Deepak Giridharagopal updated an issue











 






 PuppetDB /  PDB-336



  PuppetDB won't start: OutOfMemoryError: Java heap space 










Change By:

 Deepak Giridharagopal




Story Points:

 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 (PDB-336) PuppetDB won't start: OutOfMemoryError: Java heap space

Title: Message Title










 

 Deepak Giridharagopal updated an issue











 






 PuppetDB /  PDB-336



  PuppetDB won't start: OutOfMemoryError: Java heap space 










Change By:

 Deepak Giridharagopal




Sprint:

 20140115 to 20140122 , 20140122 to 20140129












   

 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-341) Select-resources subquery strange behavior

Title: Message Title










 

 Deepak Giridharagopal updated an issue











 






 PuppetDB /  PDB-341



  Select-resources subquery strange behavior  










Change By:

 Deepak Giridharagopal




Story Points:

 3












   

 Add Comment











 










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




 














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

Jira (PDB-275) Release 1.6.0 final

Title: Message Title










 

 Deepak Giridharagopal updated an issue











 






 PuppetDB /  PDB-275



  Release 1.6.0 final 










Change By:

 Deepak Giridharagopal




Sprint:

 20140122 to  20140129  to 20140205












   

 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-274) Write up blog for 1.6 release

Title: Message Title










 

 Deepak Giridharagopal updated an issue











 






 PuppetDB /  PDB-274



  Write up blog for 1.6 release 










Change By:

 Deepak Giridharagopal




Sprint:

 20140108 to 20140115,  20140122 to  20140129  to 20140205












   

 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-340) PR (811): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior

Title: Message Title










 

 Deepak Giridharagopal updated an issue











 






 PuppetDB /  PDB-340



  PR (811): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior 










Change By:

 Deepak Giridharagopal




Sprint:

 20140115 to 20140122,  20140122 to  20140129  to 20140205












   

 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-341) Select-resources subquery strange behavior

Title: Message Title










 

 Deepak Giridharagopal updated an issue











 






 PuppetDB /  PDB-341



  Select-resources subquery strange behavior  










Change By:

 Deepak Giridharagopal




Sprint:

 20140122 to 20140129












   

 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-238) Remove v1 API

Title: Message Title










 

 Deepak Giridharagopal updated an issue











 






 PuppetDB /  PDB-238



  Remove v1 API 










Change By:

 Deepak Giridharagopal




Sprint:

 20140108 to 20140115, 20140115 to 20140122 , 20140122 to 20140129












   

 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-314) Release 1.6.0rc3 - TBA

Title: Message Title










 

 Deepak Giridharagopal updated an issue











 






 PuppetDB /  PDB-314



  Release 1.6.0rc3 - TBA 










Change By:

 Deepak Giridharagopal




Sprint:

 20131218 to 20140101, 20140101 to 20140108, 20140108 to 20140115, 20140115 to 20140122 , 20140122 to 20140129












   

 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-228) PR (776): (#23422) Use JSON in terminus instead of PSON - dalen

Title: Message Title










 

 Deepak Giridharagopal updated an issue











 






 PuppetDB /  PDB-228



  PR (776): (#23422) Use JSON in terminus instead of PSON - dalen 










Change By:

 Deepak Giridharagopal




Sprint:

 20140101 to 20140108, 20140108 to 20140115, 20140115 to 20140122 , 20140122 to 20140129












   

 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-312) PR (802): Convert unit testing to use dynamic postgres instance - kbarber

Title: Message Title










 

 Deepak Giridharagopal updated an issue











 






 PuppetDB /  PDB-312



  PR (802): Convert unit testing to use dynamic postgres instance - kbarber 










Change By:

 Deepak Giridharagopal




Sprint:

 20140108 to 20140115, 20140115 to 20140122 , 20140122 to 20140129












   

 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-340) PR (811): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior

Title: Message Title










 

 Deepak Giridharagopal updated an issue











 






 PuppetDB /  PDB-340



  PR (811): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior 










Change By:

 Deepak Giridharagopal




Sprint:

 20140115 to 20140122 , 20140122 to 20140129












   

 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-228) PR (776): (#23422) Use JSON in terminus instead of PSON - dalen

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (776): (#23422) Use JSON in terminus instead of PSON - dalen 










kbarber commented:
@puppetlabs-jenkins retest this please












   

 Add Comment











 













 PuppetDB /  PDB-228



  PR (776): (#23422) Use JSON in terminus instead of PSON - dalen 







 h2. (#23422) Use JSON in terminus instead of PSON   * Author: Erik Dalén   * Company: Spotify  * Github ID: [dalen|https://github.com/dalen]  * [Pull Request 776 Discussion|https://github.com/puppetlabs/puppetdb/pull/776]  * [Pull Request 776 File Diff|https://github.com/puppetlabs/puppetdb/pull/776/files]  h2. Pull Request De...















 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-140) Smoke test packages

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Smoke test packages 












man hiera


 produces: "no manual for hiera" on both Deb6 and Centos 6. - is that expected? The instructions in 

HI-80
 includes "man hiera" as a test...












   

 Add Comment











 













 Hiera /  HI-140



  Smoke test packages 







 Procedure may vary by project and point in the release cycle. Ask around.   * Centos 5/6  * Debian Squeeze/Wheezy  * Ubuntu Lucid/Precise  * Gem   Check that  * hiera is available.  * man hiera (except for gems)















 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 gro

Jira (PUP-1478) PR (2279): Fix serialization of TagSet - dalen

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2279): Fix serialization of TagSet - dalen 










Pull request Fix serialization of TagSet has been closed.












   

 Add Comment











 













 Puppet /  PUP-1478



  PR (2279): Fix serialization of TagSet - dalen 







 h2. Fix serialization of TagSet   * Author: Erik Dalén   * Company: Spotify  * Github ID: [dalen|https://github.com/dalen]  * [Pull Request 2279 Discussion|https://github.com/puppetlabs/puppet/pull/2279]  * [Pull Request 2279 File Diff|https://github.com/puppetlabs/puppet/pull/2279/files]  h2. Pull Request Description   Th...















 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-1478) PR (2279): Fix serialization of TagSet - dalen

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2279): Fix serialization of TagSet - dalen 










dalen commented:
reopened against stable: https://github.com/puppetlabs/puppet/pull/2287












   

 Add Comment











 













 Puppet /  PUP-1478



  PR (2279): Fix serialization of TagSet - dalen 







 h2. Fix serialization of TagSet   * Author: Erik Dalén   * Company: Spotify  * Github ID: [dalen|https://github.com/dalen]  * [Pull Request 2279 Discussion|https://github.com/puppetlabs/puppet/pull/2279]  * [Pull Request 2279 File Diff|https://github.com/puppetlabs/puppet/pull/2279/files]  h2. Pull Request Description   Th...















 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-140) Smoke test packages

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Hiera /  HI-140



  Smoke test packages 










Change By:

 Henrik Lindberg









 Procedure may vary by project and point in the release cycle. Ask around. * Centos 5/6* Debian Squeeze/Wheezy* Ubuntu Lucid/Precise* GemCheck that* hiera is available.* man hiera (except for gems)












   

 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-140) Smoke test packages

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Smoke test packages 










CentOs 6 PASSED












   

 Add Comment











 













 Hiera /  HI-140



  Smoke test packages 







 Procedure may vary by project and point in the release cycle. Ask around.















 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-1430) PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen 










dalen commented:
I still haven't merged together those PRs, hopefully I can do it before next weeks triage












   

 Add Comment











 













 Puppet /  PUP-1430



  PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen 







 h2. Make SSL file permissions a bit more relaxed for public files   * Author: Erik Dalén   * Company: Spotify  * Github ID: [dalen|https://github.com/dalen]  * [Pull Request 2257 Discussion|https://github.com/puppetlabs/puppet/pull/2257]  * [Pull Request 2257 File Diff|https://github.com/puppetlabs/puppet/pull/2257/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-bu

Jira (PUP-1486) The resources type should be more generic

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: The resources type should be more generic 










Something along these lines seems like a good idea; I agree that the resources type is too generic, and perhaps shouldn't be a separate type, as suggested here.
This probably merits a spike to investigate some options.












   

 Add Comment











 













 Puppet /  PUP-1486



  The resources type should be more generic 







 The {{resources}} type is currently very static (it only allows to purge resources) and heavily linked to the {{user}} type (which has all sorts of hardcoded stuff about it.   It would be great to make this system more generic and pluggable. Maybe these things could be coded in each type, and the `resources` type would then make use of these type propert...















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




 














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

Jira (PUP-1490) Support --test option for puppet apply

2014-01-22 Thread JIRA

Title: Message Title










 

 Erik Dalén commented on an issue











 






  Re: Support --test option for puppet apply 










https://github.com/puppetlabs/puppet/pull/2286












   

 Add Comment











 













 Puppet /  PUP-1490



  Support --test option for puppet apply 







 For more parity between agent and apply it we should support the --test option in apply as well.















 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-1490) Support --test option for puppet apply

2014-01-22 Thread JIRA

Title: Message Title










 

 Erik Dalén created an issue











 






 Puppet /  PUP-1490



  Support --test option for puppet apply 










Issue Type:

  New Feature




Assignee:

 Eric Sorenson




Created:


 22/Jan/14 7:23 AM




Priority:

  Normal




Reporter:

 Erik Dalén










For more parity between agent and apply it we should support the --test option in apply as well.












   

 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"

Jira (PUP-1489) Missing group should give error in noop

2014-01-22 Thread Terri Haber (JIRA)

Title: Message Title










 

 Terri Haber created an issue











 






 Puppet /  PUP-1489



  Missing group should give error in noop 










Issue Type:

  Bug




Assignee:

 Eric Sorenson




Created:


 22/Jan/14 7:10 AM




Priority:

  Normal




Reporter:

 Terri Haber










Given this manifest:
class users { user  { 'testing': ensure => present, gid => 'staff', }
If group staff is unmanaged and missing from the target node, enforcing the class in noop mode should give some sort of warning that the group is missing. However, no warning is given, and then when enforcing the class without noop, the enforcement fails, puppet exits.
Given that noop mode is expected to fail in cases such as these, gid should be checked for user type declarations to be sure the group either exits on the target node or is being managed in the catalog.












   

 Add Comment

Jira (PUP-1032) The function API has "interesting" type conversions

2014-01-22 Thread JIRA

Title: Message Title










 

 Erik Dalén commented on an issue











 






  Re: The function API has "interesting" type conversions 










also, [undef] is turned into [:undef] same with undef in hashes












   

 Add Comment











 













 Puppet /  PUP-1032



  The function API has "interesting" type conversions 







 The type of parameters passed to functions is just weird:  foo(1) - String "1"  foo(1+1) - String "2"  foo($processorcount) - Numeric  foo(1*1) - Numeric 1  foo(1.0) - String "1.0"  foo(1.0+1) - Numeric 2.0  foo(1.0*1) - Numeric 1.0  foo("1"+"1") - String "2"  foo(undef) - String "" 















 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-336) PuppetDB won't start: OutOfMemoryError: Java heap space

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-336



  PuppetDB won't start: OutOfMemoryError: Java heap space 










Change By:

 Kenneth Barber




Story Points:

 5 3












   

 Add Comment











 










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




 














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

Jira (HI-30) New YAML shorthand for class params blocks existing form of class param lookup when enabled