date:20140131

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2309): Separate out hold state into a separate property - lollipopman 










lollipopman commented:
I have fixed and added tests for this new feature, apologies for not including them in the initial pull request.
I would love some feedback on the commit.












   

 Add Comment











 













 Puppet /  PUP-1541



  PR (2309): Separate out hold state into a separate property - lollipopman 







 h2. Separate out hold state into a separate property   * Author: <>  * Company:   * Github ID: [lollipopman|https://github.com/lollipopman]  * [Pull Request 2309 Discussion|https://github.com/puppetlabs/puppet/pull/2309]  * [Pull Request 2309 File Diff|https://github.com/puppetlabs/puppet/pull/2309/files]  h2. Pull Request Description   Currently hol...















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




 














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

Jira (PUP-1566) PR (2321): (pup-1524) Correct resource_present? to account for purged - kylog

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2321): (pup-1524) Correct resource_present? to account for purged - kylog 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 Puppet /  PUP-1566



  PR (2321): (pup-1524) Correct resource_present? to account for purged - kylog 







 h2. (pup-1524) Correct resource_present? to account for purged   * Author: Kylo Ginsberg <>  * Company:   * Github ID: [kylog|https://github.com/kylog]  * [Pull Request 2321 Discussion|https://github.com/puppetlabs/puppet/pull/2321]  * [Pull Request 2321 File Diff|https://github.com/puppetlabs/puppet/pull/2321/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

Jira (PUP-1565) PR (2320): Feature/master/pup 1551 environmentpath - jpartlow

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2320): Feature/master/pup 1551 environmentpath - jpartlow 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 Puppet /  PUP-1565



  PR (2320): Feature/master/pup 1551 environmentpath - jpartlow 







 h2. Feature/master/pup 1551 environmentpath   * Author: Josh Partlow <>  * Company:   * Github ID: [jpartlow|https://github.com/jpartlow]  * [Pull Request 2320 Discussion|https://github.com/puppetlabs/puppet/pull/2320]  * [Pull Request 2320 File Diff|https://github.com/puppetlabs/puppet/pull/2320/files]  h2. Pull Request Description   First pass at br...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to 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-377) Can't start puppetdb after upgrade to 1.6.0-1.fc19.noarch

2014-01-31 Thread Ryan Senior (JIRA)

Title: Message Title










 

 Ryan Senior assigned an issue to Ryan Senior











 






 PuppetDB /  PDB-377



  Can't start puppetdb after upgrade to 1.6.0-1.fc19.noarch 










Change By:

 Ryan Senior




Assignee:

 Ryan Senior












   

 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-377) Can't start puppetdb after upgrade to 1.6.0-1.fc19.noarch

2014-01-31 Thread Ryan Senior (JIRA)

Title: Message Title










 

 Ryan Senior commented on an issue











 






  Re: Can't start puppetdb after upgrade to 1.6.0-1.fc19.noarch 










Can you post your database.ini file? I'm in #puppet on freenode (rsenior) as well if you want to troubleshoot it real-time.












   

 Add Comment











 













 PuppetDB /  PDB-377



  Can't start puppetdb after upgrade to 1.6.0-1.fc19.noarch 







 yum-cron got me puppetdb-1.6.0-1.fc19.noarch and puppetdb-terminus-1.6.0-1.fc19.noarch earlier today. Now I cannot get the service to start:   {quote}  java[11322]: java.lang.NullPointerException: null  java[11322]: at clojure.lang.RT.intCast (RT.java:1087)  java[11322]: com.puppetlabs.jdbc$make_connection_pool.invoke (jdbc.clj:293)  java[11322]: com.pu...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to 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-377) Can't start puppetdb after upgrade to 1.6.0-1.fc19.noarch

2014-01-31 Thread John Florian (JIRA)

Title: Message Title










 

 John Florian created an issue











 






 PuppetDB /  PDB-377



  Can't start puppetdb after upgrade to 1.6.0-1.fc19.noarch 










Issue Type:

  Bug




Affects Versions:


 1.6.0




Assignee:


 Unassigned




Created:


 31/Jan/14 6:13 PM




Environment:


Fedora 19 x86_64




Priority:

  Critical




Reporter:

 John Florian










yum-cron got me puppetdb-1.6.0-1.fc19.noarch and puppetdb-terminus-1.6.0-1.fc19.noarch earlier today. Now I cannot get the service to start:

java[11322]: java.lang.NullPointerException: null java[11322]: at clojure.lang.RT.intCast (RT.java:1087) java[11322]: com.puppetlabs.jdbc$make_connection_pool.invoke (jdbc.clj:293) java[11322]: com.puppetlabs.jdbc$pooled_datasource.invoke (jdbc.clj:323) java[11322]: com.puppetlabs.puppetdb.cli.services$_main.doInvoke (services.clj:242) java[11322]: clojure.lang.RestFn.invoke (RestFn.java:421) java[11322]: clojure.lang.Var.invoke (Var.java:419) java[11322]: clojure.lang.AFn.applyToHelper (AFn.java:163) java[11322]: clojure.lang.Var.applyTo (Var.java:532) java[11322]: clojure.core$apply.invoke (core.clj:617) java[11322]: com.puppetlabs.puppetdb.core$run_command.invoke (core.clj:87) java[11322]: com.puppetlabs.puppetdb.core$_main.doInvoke (core.clj:95) java[11322]: clojure.lang.RestFn.applyTo (RestFn.java:137) java[11322]: com.puppetlabs.puppetdb.core.main (:-1) systemd[1]: puppetdb.service: main process exited, co

Jira (PUP-1551) Change from "environmentdir" to "environmentpath"

2014-01-31 Thread Andrew Parker (JIRA)

Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: Change from "environmentdir" to "environmentpath" 










Joshua Partlow, I think using --environment with puppet module install should cause it to install in the environment's module directory, since the module tool will install into the first directory in the environment's modulepath.












   

 Add Comment











 













 Puppet /  PUP-1551



  Change from "environmentdir" to "environmentpath" 







 There is likely a need for having multiple directories to hold environments. This can be done by changing from a single {{environmentdir}} to having a list of paths as an {{environmentpath}}.















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




 














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

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Change from "environmentdir" to "environmentpath" 










And another question, how should this be interacting with puppet module? If I `puppet module --environment foo install puppetlabs-barmod` (and foo is an environment directory in the path) should I expect the module to be installed in foo/modules? (haven't tested this yet)












   

 Add Comment











 













 Puppet /  PUP-1551



  Change from "environmentdir" to "environmentpath" 







 There is likely a need for having multiple directories to hold environments. This can be done by changing from a single {{environmentdir}} to having a list of paths as an {{environmentpath}}.















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to 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-640) Report format 4 docs should be updated for optional fields

2014-01-31 Thread Andrew Parker (JIRA)

Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: Report format 4 docs should be updated for optional fields 










Merged into master in https://github.com/puppetlabs/puppet/commit/bfc60db480921f1d735e33dc05198749709b698f












   

 Add Comment











 













 Puppet /  PUP-640



  Report format 4 docs should be updated for optional fields 







 In PE 3.1.0/Puppet 3.3.1 the report format changed to include a new kind of event, which is not associated with a property, for some failures that previously did not have an event. This has caused a change in the report format because these events do not always have previous_value, property, desired_value, name, and historical_value. Some of these get tra...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to 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-1533) PR (2307): (pup-640) Update report schema for error events - kylog

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2307): (pup-640) Update report schema for error events - kylog 










Pull request (pup-640) Update report schema for error events has been closed.












   

 Add Comment











 













 Puppet /  PUP-1533



  PR (2307): (pup-640) Update report schema for error events - kylog 







 h2. (pup-640) Update report schema for error events   * Author: Kylo Ginsberg <>  * Company:   * Github ID: [kylog|https://github.com/kylog]  * [Pull Request 2307 Discussion|https://github.com/puppetlabs/puppet/pull/2307]  * [Pull Request 2307 File Diff|https://github.com/puppetlabs/puppet/pull/2307/files]  h2. Pull Request Description   Previously, s...















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




 














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

Jira (PUP-1566) PR (2321): (pup-1524) Correct resource_present? to account for purged - kylog

Title: Message Title










 

 gepetto-bot created an issue











 






 Puppet /  PUP-1566



  PR (2321): (pup-1524) Correct resource_present? to account for purged - kylog 










Issue Type:

  Task




Assignee:

 Eric Sorenson




Components:


 Community




Created:


 31/Jan/14 5:27 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










(pup-1524) Correct resource_present? to account for purged


Author: Kylo Ginsberg <>


Company:


Github ID: kylog


Pull Request 2321 Discussion


Pull Request 2321 File Diff


Pull Request Description

The fix for http://projects.puppetla

Jira (PUP-1560) PR (2318): (pup-1524) Correct resource_present? to account for purged - kylog

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2318): (pup-1524) Correct resource_present? to account for purged - kylog 










Pull request (pup-1524) Correct resource_present? to account for purged has been closed.












   

 Add Comment











 













 Puppet /  PUP-1560



  PR (2318): (pup-1524) Correct resource_present? to account for purged - kylog 







 h2. (pup-1524) Correct resource_present? to account for purged   * Author: Kylo Ginsberg <>  * Company:   * Github ID: [kylog|https://github.com/kylog]  * [Pull Request 2318 Discussion|https://github.com/puppetlabs/puppet/pull/2318]  * [Pull Request 2318 File Diff|https://github.com/puppetlabs/puppet/pull/2318/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-1551) Change from "environmentdir" to "environmentpath"

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Change from "environmentdir" to "environmentpath" 










Blocked by the same future parser issue holding back PUP-1118 – which I haven't figured out yet.












   

 Add Comment











 













 Puppet /  PUP-1551



  Change from "environmentdir" to "environmentpath" 







 There is likely a need for having multiple directories to hold environments. This can be done by changing from a single {{environmentdir}} to having a list of paths as an {{environmentpath}}.















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to 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-1118) Support an $environmentsdir setting

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Support an $environmentsdir setting 










This is blowing up the future parser test runs.  https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Future-Parser-master-vcloud-and-github/55/












   

 Add Comment











 













 Puppet /  PUP-1118



  Support an $environmentsdir setting 







 Puppet needs to read environment specific manifests and modules from directories that reside in a location specified by an {{environmentsdir}} setting. The name of the environment is the name of the directory that will be used for that environment.   Each environment directory contains 2 directories (both optional)     * manifests    * modules   The {{...















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




 














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

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Change from "environmentdir" to "environmentpath" 










A first pass is up for review in the attached PR. Also need to update the pre-docs for this change.












   

 Add Comment











 













 Puppet /  PUP-1551



  Change from "environmentdir" to "environmentpath" 







 There is likely a need for having multiple directories to hold environments. This can be done by changing from a single {{environmentdir}} to having a list of paths as an {{environmentpath}}.















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to 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-1565) PR (2320): Feature/master/pup 1551 environmentpath - jpartlow

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2320): Feature/master/pup 1551 environmentpath - jpartlow 










jpartlow commented:
The acceptance test in particular could use some review. Is it testing what we want to test? I'm a little hazy on the use case.












   

 Add Comment











 













 Puppet /  PUP-1565



  PR (2320): Feature/master/pup 1551 environmentpath - jpartlow 







 h2. Feature/master/pup 1551 environmentpath   * Author: Josh Partlow <>  * Company:   * Github ID: [jpartlow|https://github.com/jpartlow]  * [Pull Request 2320 Discussion|https://github.com/puppetlabs/puppet/pull/2320]  * [Pull Request 2320 File Diff|https://github.com/puppetlabs/puppet/pull/2320/files]  h2. Pull Request Description   First pass at br...















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




 














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

Jira (PUP-1565) PR (2320): Feature/master/pup 1551 environmentpath - jpartlow

Title: Message Title










 

 gepetto-bot created an issue











 






 Puppet /  PUP-1565



  PR (2320): Feature/master/pup 1551 environmentpath - jpartlow 










Issue Type:

  Task




Assignee:

 Eric Sorenson




Components:


 Community




Created:


 31/Jan/14 5:13 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Feature/master/pup 1551 environmentpath


Author: Josh Partlow <>


Company:


Github ID: jpartlow


Pull Request 2320 Discussion


Pull Request 2320 File Diff


Pull Request Description

First pass at broadening the new environmentdir setting to be an envi

Jira (PUP-1362) Rubyize yumhelper.py to remove dependency on python

2014-01-31 Thread Jo Rhett (JIRA)

Title: Message Title










 

 Jo Rhett commented on an issue











 






  Re: Rubyize yumhelper.py to remove dependency on python 










We have two choices here:
1. Puppet only works if you don't install any non-stock software 2. Puppet works fine as long as the command it depends on (yum) works fine. 
#2 is a trivial code change. So we can embrace stock-ism religion and break large numbers of sites, or we can make a trivial change used by the stock software itself to ensure it work.












   

 Add Comment











 













 Puppet /  PUP-1362



  Rubyize yumhelper.py to remove dependency on python 







 There are several bugs (bug 11380 being one that triggered this patch) that highlight the fact that the version of python used as the default on a system running puppet can break yumhelper.py.   This refactor removes yumhelper.py and moves the functionality into the Yum provider in puppet.















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




 














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

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

Title: Message Title










 

 Joshua Hoblitt updated an issue











 






 Puppet /  PUP-1564



  package rpm provider should support :uninstall_options feature 










Change By:

 Joshua Hoblitt




Summary:

 package rpm provider should support : uninstallable uninstall_options  feature












   

 Add Comment











 










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




 














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

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

Title: Message Title










 

 Joshua Hoblitt created an issue











 






 Puppet /  PUP-1564



  package rpm provider should support :uninstallable feature 










Issue Type:

  Improvement




Assignee:

 Eric Sorenson




Created:


 31/Jan/14 4:26 PM




Priority:

  Normal




Reporter:

 Joshua Hoblitt












   

 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-1563) Puppet::ModuleTool::Applications::Installer::resolve_install_conflicts can get in a recursive loop

2014-01-31 Thread Joe Julian (JIRA)

Title: Message Title

Joe Julian updated an issue

Puppet / PUP-1563

Puppet::ModuleTool::Applications::Installer::resolve_install_conflicts can get in a recursive loop

Change By:

Joe Julian

resolve_install_conflicts will enter into an endless recursion if any package dependency does not exist. I had a package I force installed (local package file) that had a dependency on a package that I hadn't actually packaged yet, ie. joejulian am re - logfile depended on joejulian-logrotate but there was no metadata.json for /etc/puppet/modules/logrotate. joejulian-logrotate is not on evaluating the forge cause . I tried installing a module (any module) through "puppet module install ..." and the command hung for more than 10 minutes before mistakenly thought I killed 'd identified it when I originally opened this bug . strace showed it walking the module tree over and over again indefinitely.

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-1563) Puppet::ModuleTool::Applications::Installer::resolve_install_conflicts can get in a recursive loop

2014-01-31 Thread Joe Julian (JIRA)

Title: Message Title










 

 Joe Julian created an issue











 






 Puppet /  PUP-1563



  Puppet::ModuleTool::Applications::Installer::resolve_install_conflicts can get in a recursive loop 










Issue Type:

  Bug




Affects Versions:


 3.3.2




Assignee:

 Andrew Parker




Components:


 Modules




Created:


 31/Jan/14 3:59 PM




Priority:

  Normal




Reporter:

 Joe Julian










resolve_install_conflicts will enter into an endless recursion if any package dependency does not exist.
I had a package I force installed (local package file) that had a dependency on a package that I hadn't actually packaged yet, ie. joejulian-logfile depended on joejulian-logrotate but there was no metadata.json for /etc/puppet/modules/logrotate. joejulian-logrotate is not on the forge.
I tried installing a module (any module) through "puppet module install ..." and the command hung for more than 10 minutes before I killed it. strace showed it walking the module tree over and over again indefinitely.

Jira (PDB-365) Merge new tag into pe- fork

2014-01-31 Thread Ryan McKern (JIRA)

Title: Message Title










 

 Ryan McKern commented on an issue











 






  Re: Merge new tag into pe- fork 










Waiting on PR 6












   

 Add Comment











 













 PuppetDB /  PDB-365



  Merge new tag into pe- fork 







 Upon release the latest changes need to be merged into the pe- fork.















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to 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-1362) Rubyize yumhelper.py to remove dependency on python

Title: Message Title










 

 Joshua Hoblitt commented on an issue











 






  Re: Rubyize yumhelper.py to remove dependency on python 










I've never had a problem with either EPEL5 or EPEL6. Keep in mind that EPEL6 does not include an updated python interpreter at all. I can't speak for RepoForge, as I don't use it. Replacing the system c compiler or perl5/ruby/python interpreters with a different version means you also have to assume the risk of breaking software that depends on those things.
Reviewing this thread, I don't see a mention of what python builds/package(s) break the helper or an error output or an analysis of how it broke.












   

 Add Comment











 













 Puppet /  PUP-1362



  Rubyize yumhelper.py to remove dependency on python 







 There are several bugs (bug 11380 being one that triggered this patch) that highlight the fact that the version of python used as the default on a system running puppet can break yumhelper.py.   This refactor removes yumhelper.py and moves the functionality into the Yum provider in puppet.















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




 














-- 
You received this message because you are subscribed to the Google Group

Jira (FACT-94) Unvendor CFPropertyList

2014-01-31 Thread Kurt Wall (JIRA)

Title: Message Title










 

 Kurt Wall updated an issue











 






 Facter /  FACT-94



  Unvendor CFPropertyList 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall












   

 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-1362) Rubyize yumhelper.py to remove dependency on python

2014-01-31 Thread Jo Rhett (JIRA)

Title: Message Title










 

 Jo Rhett commented on an issue











 






  Re: Rubyize yumhelper.py to remove dependency on python 










It happens from EPEL and RepoForge packages as well as people building locally. 
I do not argue that all possible ways to break this are our responsibility. I am arguing that it's trivial to ensure against breakage. If yum works from the command line, so should puppet. Nothing which doesn't break yum should break puppet.












   

 Add Comment











 













 Puppet /  PUP-1362



  Rubyize yumhelper.py to remove dependency on python 







 There are several bugs (bug 11380 being one that triggered this patch) that highlight the fact that the version of python used as the default on a system running puppet can break yumhelper.py.   This refactor removes yumhelper.py and moves the functionality into the Yum provider in puppet.















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




 














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

Jira (FACT-94) Unvendor CFPropertyList

2014-01-31 Thread Kurt Wall (JIRA)

Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Facter /  FACT-94



  Unvendor CFPropertyList 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall












   

 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-1562) certnames with @ symbols don't pass through auth.conf

2014-01-31 Thread Nicholas Fagerlund (JIRA)

Title: Message Title










 

 Nicholas Fagerlund commented on an issue











 






  Re: certnames with @ symbols don't pass through auth.conf 










This had a pull request which was closed because Spencer was slammed and didn't have time to guide it through the last stages of review/revision. I also worked on identifying the problem and the possible fix. 












   

 Add Comment











 













 Puppet /  PUP-1562



  certnames with @ symbols don't pass through auth.conf 







 In lib/puppet/network/authstore.rb line 242ish a case statement deals with certnames with @ symbols in way that makes it so that they'll never match auth.conf rules for hosts. The easy workaround is, of course, not to use certnames with at symbols.   We really ought to stop conflating host, name and certname in this area of code also, because it makes i...















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




 














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

Jira (PUP-1562) certnames with @ symbols don't pass through auth.conf

2014-01-31 Thread redmine.exporter (JIRA)

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1562



  certnames with @ symbols don't pass through auth.conf 










Issue Type:

  Bug




Assignee:

 Eric Sorenson




Created:


 31/Jan/14 2:47 PM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










In lib/puppet/network/authstore.rb line 242ish a case statement deals with certnames with @ symbols in way that makes it so that they'll never match auth.conf rules for hosts. The easy workaround is, of course, not to use certnames with at symbols.
We really ought to stop conflating host, name and certname in this area of code also, because it makes it REALLY hard to read.












   

 Add Comment

Jira (PUP-845) Create a windows provider

2014-01-31 Thread Rob Reynolds (JIRA)

Title: Message Title










 

 Rob Reynolds assigned an issue to Rob Reynolds











 






 Puppet /  PUP-845



  Create a windows provider 










Change By:

 Rob Reynolds




Assignee:

 Rob Reynolds












   

 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-31 Thread Rob Reynolds (JIRA)

Title: Message Title










 

 Rob Reynolds assigned an issue to Unassigned











 






 Puppet /  PUP-844



  Create basic acl type 










Change By:

 Rob Reynolds




Assignee:

 Rob Reynolds












   

 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-1362) Rubyize yumhelper.py to remove dependency on python

Title: Message Title










 

 Joshua Hoblitt commented on an issue











 






  Re: Rubyize yumhelper.py to remove dependency on python 










I've never seen this issue occur in centos 5.0 -> 5.10 or 6.0 -> 6.4. Is this breakage happening from core packages updates or a 3rd party installation?












   

 Add Comment











 













 Puppet /  PUP-1362



  Rubyize yumhelper.py to remove dependency on python 







 There are several bugs (bug 11380 being one that triggered this patch) that highlight the fact that the version of python used as the default on a system running puppet can break yumhelper.py.   This refactor removes yumhelper.py and moves the functionality into the Yum provider in puppet.















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to 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-897) package type should accept virtual package for rpm

2014-01-31 Thread Ryan McKern (JIRA)

Title: Message Title










 

 Ryan McKern commented on an issue











 






  Re: package type should accept virtual package for rpm 










There's a comment in the original conversation on projects.puppetlabs.com from Eric Sorenson:

UPDATED BY ERIC SORENSON 2 MONTHS AGO (11/27/2013) Target version set to 3.5.0 Pulling this in for 3.5.0 — since there’s code we can probably just do this as part of community pull request triage.

I can confirm that this patch hasn't been merged yet, but that was the last conversation about it.












   

 Add Comment











 













 Puppet /  PUP-897



  package type should accept virtual package for rpm 







 Rpm ( like many similar package systems ) define a system of virtual package, with the tag Provides.  For example, on Mandriva, we have :   $ rpm -q --provides perl-Term-Size-Any-0.1.0-2mdv2010.1  perl(Term::Size::Any) = 0.1.0  perl-Term-Size-Any = 0.1.0-2mdv2010.1   So I can use "urpmi perl(Term::Size::Any)" to install the rpm.  On puppet,...















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

Jira (PUP-897) package type should accept virtual package for rpm

2014-01-31 Thread Michelle Johansen (JIRA)

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-897



  package type should accept virtual package for rpm 










Change By:

 Michelle Johansen




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 (PUP-897) package type should accept virtual package for rpm

2014-01-31 Thread Michelle Johansen (JIRA)

Title: Message Title










 

 Michelle Johansen commented on an issue











 






  Re: package type should accept virtual package for rpm 










Kylo Ginsberg or Ryan McKern Can we get some review here please?












   

 Add Comment











 













 Puppet /  PUP-897



  package type should accept virtual package for rpm 







 Rpm ( like many similar package systems ) define a system of virtual package, with the tag Provides.  For example, on Mandriva, we have :   $ rpm -q --provides perl-Term-Size-Any-0.1.0-2mdv2010.1  perl(Term::Size::Any) = 0.1.0  perl-Term-Size-Any = 0.1.0-2mdv2010.1   So I can use "urpmi perl(Term::Size::Any)" to install the rpm.  On puppet,...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to 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-1560) PR (2318): (pup-1524) Correct resource_present? to account for purged - kylog

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2318): (pup-1524) Correct resource_present? to account for purged - kylog 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 Puppet /  PUP-1560



  PR (2318): (pup-1524) Correct resource_present? to account for purged - kylog 







 h2. (pup-1524) Correct resource_present? to account for purged   * Author: Kylo Ginsberg <>  * Company:   * Github ID: [kylog|https://github.com/kylog]  * [Pull Request 2318 Discussion|https://github.com/puppetlabs/puppet/pull/2318]  * [Pull Request 2318 File Diff|https://github.com/puppetlabs/puppet/pull/2318/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

Jira (PUP-1504) PR (2294): Clarified `pattern` parameter for Service type (DOCUMENT-1) - holguinj

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2294): Clarified `pattern` parameter for Service type (DOCUMENT-1) - holguinj 










holguinj commented:
I think it ended up in DOCUMENT because it was spotted at [Docs: Type Reference](http://docs.puppetlabs.com/references/latest/type.html). If that messes with the platform workflow then we're happy to figure out a better way to handle issues like this.












   

 Add Comment











 













 Puppet /  PUP-1504



  PR (2294): Clarified `pattern` parameter for Service type (DOCUMENT-1) - holguinj 







 h2. Clarified `pattern` parameter for Service type (DOCUMENT-1)   * Author: Justin Holguin   * Company: Puppet Labs, Inc.  * Github ID: [holguinj|https://github.com/holguinj]  * [Pull Request 2294 Discussion|https://github.com/puppetlabs/puppet/pull/2294]  * [Pull Request 2294 File Diff|https://github.com/puppetlabs/puppet/p...















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




 














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

Jira (PUP-576) Add a fedora19 host to the platforms we are testing in ci.

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Add a fedora19 host to the platforms we are testing in ci. 










Merged 3168a71 to master to fix issues with sqlite3 driver on Debian.












   

 Add Comment











 













 Puppet /  PUP-576



  Add a fedora19 host to the platforms we are testing in ci. 







 We are not currently testing on fedora19 because of two test failures we haven't had time to resolve. I believe fedora19 is the only platform currently available in our dynamic vcloud templates running Ruby 2.0, so it would be good to get this in.   The two failures are:   1) helpful_error_message_when_hostname_not_match_server_certificate.rb  2) store...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to 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-1504) PR (2294): Clarified `pattern` parameter for Service type (DOCUMENT-1) - holguinj