date:20140103

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1369



  Kylo Test Sub-task 










Issue Type:

  Sub-task




Assignee:

 Kylo Ginsberg




Created:


 03/Jan/14 11:57 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Kylo Test Sub-task Description












   

 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 e

Jira (PUP-1367) Kylo Test Sub-task

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1367



  Kylo Test Sub-task 










Issue Type:

  Sub-task




Assignee:

 Kylo Ginsberg




Created:


 03/Jan/14 11:56 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Kylo Test Sub-task Description












   

 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 e

Jira (PUP-1371) Kylo Test Sub-task

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1371



  Kylo Test Sub-task 










Issue Type:

  Sub-task




Assignee:

 Kylo Ginsberg




Created:


 03/Jan/14 11:57 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Kylo Test Sub-task Description












   

 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 e

Jira (PUP-1366) Kylo Test Issue

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1366



  Kylo Test Issue 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 03/Jan/14 11:56 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Kylo Test Issue Description












   

 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 rec

Jira (PUP-1368) Kylo Test Issue

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1368



  Kylo Test Issue 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 03/Jan/14 11:57 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Kylo Test Issue Description












   

 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 rec

Jira (PUP-1370) Kylo Test Issue

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1370



  Kylo Test Issue 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 03/Jan/14 11:57 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Kylo Test Issue Description












   

 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 rec

Jira (PUP-1363) Kylo Test Sub-task

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1363



  Kylo Test Sub-task 










Issue Type:

  Sub-task




Assignee:

 Kylo Ginsberg




Created:


 03/Jan/14 11:20 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Kylo Test Sub-task Description












   

 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 e

Jira (PUP-1364) Kylo Test Issue

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1364



  Kylo Test Issue 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 03/Jan/14 11:21 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Kylo Test Issue Description












   

 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 rec

Jira (PUP-1362) Kylo Test Issue

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1362



  Kylo Test Issue 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 03/Jan/14 11:20 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Kylo Test Issue Description












   

 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 rec

Jira (PUP-1365) Kylo Test Sub-task

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1365



  Kylo Test Sub-task 










Issue Type:

  Sub-task




Assignee:

 Kylo Ginsberg




Created:


 03/Jan/14 11:21 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Kylo Test Sub-task Description












   

 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 e

Jira (PUP-1361) Kylo Test Issue

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1361



  Kylo Test Issue 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 03/Jan/14 11:20 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Kylo Test Issue Description












   

 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 rec

Jira (PUP-1359) Kylo Test Issue

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1359



  Kylo Test Issue 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 03/Jan/14 11:18 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Kylo Test Issue Description












   

 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 rec

Jira (PUP-1360) Kylo Test Sub-task

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1360



  Kylo Test Sub-task 










Issue Type:

  Sub-task




Assignee:

 Kylo Ginsberg




Created:


 03/Jan/14 11:18 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Kylo Test Sub-task Description












   

 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 e

Jira (PUP-1357) Kylo Test Issue

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1357



  Kylo Test Issue 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 03/Jan/14 11:09 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Kylo Test Issue Description












   

 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 rec

Jira (PUP-1358) Kylo Test Sub-task

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1358



  Kylo Test Sub-task 










Issue Type:

  Sub-task




Assignee:


 Unassigned




Created:


 03/Jan/14 11:09 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Kylo Test Sub-task Description












   

 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 an

Jira (PUP-1356) Kylo Test Issue

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1356



  Kylo Test Issue 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 03/Jan/14 11:03 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Kylo Test Issue Description












   

 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 rec

Jira (PUP-1355) Kylo Test Issue

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1355



  Kylo Test Issue 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 03/Jan/14 10:50 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Kylo Test Issue Description












   

 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 rec

Jira (PUP-1354) Kylo Test Issue

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1354



  Kylo Test Issue 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 03/Jan/14 10:50 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Kylo Test Issue Description












   

 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 rec

Jira (PUP-1144) No longer allows variables with leading underscores

Title: Message Title










 

 Kylo Ginsberg assigned an issue to Unassigned











 






 Puppet /  PUP-1144



  No longer allows variables with leading underscores 










Change By:

 Kylo Ginsberg




Assignee:

 Eric Sorenson












   

 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-1144) No longer allows variables with leading underscores

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1144



  No longer allows variables with leading underscores 










Change By:

 Kylo Ginsberg




Sprint:

 Week 2014-1-8 to 2014-1-15












   

 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-1353) PR (2221): (PUP-1282) Express Windows specific gem dependencies - joshcooper

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2221): (PUP-1282) Express Windows specific gem dependencies - joshcooper 










ferventcoder commented:
I'm getting the following error with this:
``` rake aborted! Platform specific gem dependency type must be 'gem_runtime_dependencies' or 'gem_development_dependencies', not 'bundle_platform' /Users/rob/code/puppetlabs/puppet/ext/packaging/tasks/gem.rake:108:in `block (2 levels) in create_platform_specific_gems' /Users/rob/code/puppetlabs/puppet/ext/packaging/tasks/gem.rake:101:in `each' /Users/rob/code/puppetlabs/puppet/ext/packaging/tasks/gem.rake:101:in `block in create_platform_specific_gems' /Users/rob/code/puppetlabs/puppet/ext/packaging/tasks/gem.rake:94:in `each' /Users/rob/code/puppetlabs/puppet/ext/packaging/tasks/gem.rake:94:in `create_platform_specific_gems' /Users/rob/code/puppetlabs/puppet/ext/packaging/tasks/gem.rake:123:in `block (2 levels) in ' /opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:236:in `call' /opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:236:in `block in execute' /opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:231:in `each' /opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:231:in `execute' /opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:175:in `block in invoke_with_call_chain' /opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize' /opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:168:in `invoke_with_call_chain' /opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/task.rb:161:in `invoke' /opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:149:in `invoke_task' /opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:106:in `block (2 levels) in top_level' /opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:106:in `each' /opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:106:in `block in top_level' /opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:115:in `run_with_threads' /opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:100:in `top_level' /opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:78:in `block in run' /opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:165:in `standard_exception_handling' /opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/rake-10.1.0/lib/rake/application.rb:75:in `run' /opt/boxen/rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/rake-10.1.0/bin/rake:33:in `' /opt/boxen/rbenv/versions/1.9.3-p392/bin/rake:23:in `load' /opt/boxen/rbenv/versions/1.9.3-p392/bin/rake:23:in `' Tasks: TOP => package:gem ```












   

 Add Comment

Jira (PUP-1353) PR (2221): (PUP-1282) Express Windows specific gem dependencies - joshcooper

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2221): (PUP-1282) Express Windows specific gem dependencies - joshcooper 










ferventcoder commented:
Does the .gemspec file need to be updated as well for stdlib and other module development so they properly pull in the dependencies? Or will that be satisfied with this fix?












   

 Add Comment











 













 Puppet /  PUP-1353



  PR (2221): (PUP-1282) Express Windows specific gem dependencies - joshcooper 







 h2. (PUP-1282) Express Windows specific gem dependencies   * Author: Josh Cooper <>  * Company:   * Github ID: [joshcooper|https://github.com/joshcooper]  * [Pull Request 2221 Discussion|https://github.com/puppetlabs/puppet/pull/2221]  * [Pull Request 2221 File Diff|https://github.com/puppetlabs/puppet/pull/2221/files]  h2. Pull Request Description   ...















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




 














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

Jira (PDB-106) Report processor in puppetdb-terminus fails during catalogue compilation failures

Title: Message Title

Jason Antman commented on an issue

Re: Report processor in puppetdb-terminus fails during catalogue compilation failures

I was getting this intermittently on PDB 1.4.0. I upgraded to 1.5.2 (CentOS 6, RPMs from PuppetLabs repo, installed and upgraded via puppetlabs/puppetdb module) and it's now happening... every time one of my nodes runs triggered by mcollective, but never when they run triggered via "puppet agent -t --verbose". There's nothing in /var/log/messages on the nodes to indicate that the runs failed.
I have a report that triggered this (I enabled report store for one run), but would prefer to pass it along out-of-band as it has some non-public information.
I ran the master with --no-daemonize --debug, but didn't get anything other than the already mentioned error message, other than confirming that it's coming from the Puppetdb report processor.
I'm trying to dig deeper into this now...

Add Comment

PuppetDB / PDB-106

Report processor in puppetdb-terminus fails during catalogue compilation failures

Sample content: {code} node "puppetdb1.vm" { somesyntaxerror } {code} When the report submitter tries to submit such a report, we get: {{Feb 18 19:15:31 puppetdb1 puppet-master[28878]: Report processor failed: undefined method `[]' for nil:NilClass}} On the puppetmaster ...

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

Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-01-03 Thread Jo Rhett (JIRA)

Title: Message Title










 

 Jo Rhett commented on an issue











 






  Re: Yum provider using "version-release" to validate installation. 










I completely agree with Jason in pretty much every aspect. This should have been a high priority issue, but has been ignored for years.
IMHO it would best to come up with the right answer and make it an incompatible change at a given release target. Trying to make this work backwards compatible is very unlikely.












   

 Add Comment











 













 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 







 When using yum provider Puppet complains(error output) when using only the version(string) of the package to install or installed at the time of verification. $snmp_version = "5.3.2.2"  package { "net-snmp": ensure => "${snmp_version}"; }Client output:debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: 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+unsubs

Jira (PUP-1244) Yum provider using "version-release" to validate installation.

Title: Message Title










 

 Jason Antman updated an issue











 






 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 










Attaching the full (and non-jira-parsed) output from debug runs










Change By:

 Jason Antman




Attachment:

 PUPPET-1244.txt












   

 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-1244) Yum provider using "version-release" to validate installation.

Title: Message Title










 

 Jason Antman commented on an issue











 






  Re: Yum provider using "version-release" to validate installation. 










This was opened 2010-04-12 against 0.24.8 and is still happening today with 3.4.1. I'd classify this as a high priority bug - what's reported by Puppet doesn't match what's actually being done, and even worse, on an initial run the package is actually installed even though the report says the resource failed, and on subsequent runs, the package is downgraded.
To be clear (see below), yum DOES install/upgrade the package (on every puppet run too), but REPORTS FAILURE as the post-yum-command version comparison fails.
I've attached the full --debug output of an example apply run, but what follows here are the important parts: ### [root@djaapafes7 ~]# puppet --version 3.3.2 [root@djaapafes7 ~]# /bin/rpm -q puppet --nosignature --nodigest --qf 'NAME: "% {NAME}" EPOCH: "%|EPOCH?{%{EPOCH}}:{0}|" VERSION: "%{VERSION}" RELEASE: "%{RELEASE}" ARCH: "%{ARCH}"\n' NAME: "puppet" EPOCH: "0" VERSION: "3.3.2" RELEASE: "1.el5" ARCH: "noarch" [root@djaapafes7 ~]# cat /home/jantman/temp/PUP1244.pp package {'puppet': ensure => '3.4.1' } [root@djaapafes7 ~]# puppet apply --debug /home/jantman/temp/PUP1244.pp ... Info: Applying configuration version '1388804396' Debug: Prefetching yum resources for package Debug: Executing '/bin/rpm --version' Debug: Executing '/bin/rpm -qa --nosignature --nodigest --qf '%{NAME}
 %|EPOCH?{%{EPOCH}}: {0}| %{VERSION} %{RELEASE} %{ARCH} :DESC: %{SUMMARY}\n'' Debug: Package[puppet](provider=yum): Ensuring => 3.4.1 Debug: Executing '/bin/rpm -q puppet --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}
| % {VERSION} %{RELEASE} %{ARCH} :DESC: %{SUMMARY}\n' Debug: Executing '/usr/bin/yum -d 0 -e 0 -y install puppet-3.4.1' Debug: Executing '/bin/rpm -q puppet --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION}
 % {RELEASE} %{ARCH} :DESC: %{SUMMARY}\n' Error: Could not update: Failed to update to version 3.4.1, got version 3.4.1-1.el5 instead Error: /Stage[main]//Package[puppet]/ensure: change from 3.3.2-1.el5 to 3.4.1 failed: Could not update: Failed to update to version 3.4.1, got version 3.4.1-1.el5 instead Debug: Finishing transaction 23456260688080 [root@djaapafes7 ~]# puppet --version 3.4.1 [root@djaapafes7 ~]# /bin/rpm -q puppet --nosignature --nodigest --qf 'NAME: "%{NAME}" EPOCH: "%|EPOCH?{%{EPOCH}}:{0}|" VERSION: "%{VERSION}" RELEASE: "%{RELEASE}
" ARCH: "% {ARCH}"\n' NAME: "puppet" EPOCH: "0" VERSION: "3.4.1" RELEASE: "1.el5" ARCH: "noarch"  ... and if we run it again...  [root@djaapafes7 ~]# puppet apply --debug /home/jantman/temp/PUP1244.pp ... Info: Applying configuration version '1388804480' Debug: Prefetching yum resources for package Debug: Executing '/bin/rpm --version' Debug: Executing '/bin/rpm -qa --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}
 :DESC: % {SUMMARY}\n'' Debug: Package[puppet](provider=yum): Ensuring => 3.4.1 Debug: Executing '/bin/rpm -q puppet --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH} :DESC: %{SUMMARY}
\n' Debug: Package[puppet](provider=yum): Downgrading package puppet from version 3.4.1-1.el5 to 3.4.1 Debug: Executing '/usr/bin/yum -d 0 -e 0 -y downgrade puppet-3.4.1' Debug: Executing '/bin/rpm -q puppet --nosignature --nodigest --qf % {NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH} :DESC: %{SUMMARY}\n' Error: Could not update: Failed to update to version 3.4.1, got version 3.4.1-1.el5 instead Error:

Jira (PUP-1364) Yum package arch and version ensuring failing

Title: Message Title










 

 Jason Antman commented on an issue











 






  Re: Yum package arch and version ensuring failing 










Yeah, this is a problem.
It seems to me that the only logical solution is to add an "architecture" parameter to the Package type, and have the provider append that to the package name/version/release string that it's trying to install. That should also be made part of namevar/resource identity, as it's perfectly feasible (and common) to install, say, openssl.x86_64 and openssl.i386












   

 Add Comment











 













 Puppet /  PUP-1364



  Yum package arch and version ensuring failing 







 After lots of trial and error I found a bug in our current Puppet version   Having a package line like so:  package { "firefox.x86_64": ensure => "3.0.12-1.el5.centos", require => Package["xulrunner.x86_64"] } Would fail with debug output:*_  debug: //Node[om012274.drd.int]/workstation/workstation_centos53/mozillasuite53/Pac...















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




 














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

Jira (PUP-1197) Add "downgrade" flag to package provider base class (boolean)

Title: Message Title










 

 Jason Antman updated an issue











 






 Puppet /  PUP-1197



  Add "downgrade" flag to package provider base class (boolean) 










I may be wrong about this, but it seems like what the reporter wants to achieve is a ">=X" specification. I.e. setting "ensure => '1.2.3'" and "downgrade => false" would effectively be the same as (if the provider supported such notation) saying "ensure => '>=1.2.3'"










Change By:

 Jason Antman




Component/s:

 Types and Providers




Labels:

 redmine  yum












   

 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-1365) Yum provider doesn't understand globs

Title: Message Title










 

 Jason Antman updated an issue











 






 Puppet /  PUP-1365



  Yum provider doesn't understand globs 










Change By:

 Jason Antman




Component/s:

 Types and Providers




Labels:

 redmine  yum












   

 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-958) PR (2137): (#23316) Updated yum package provider to support :holdable feature by - fatmcgav

Title: Message Title










 

 Jason Antman updated an issue











 






 Puppet /  PUP-958



  PR (2137): (#23316) Updated yum package provider to support :holdable feature by - fatmcgav 










Change By:

 Jason Antman




Component/s:

 Types and Providers




Labels:

 github  yum












   

 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-1073) Common package name in two different providers

Title: Message Title










 

 Jason Antman updated an issue











 






 Puppet /  PUP-1073



  Common package name in two different providers 










Change By:

 Jason Antman




Component/s:

 Types and Providers












   

 Add Comment











 










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




 














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

Jira (PUP-1364) Yum package arch and version ensuring failing

Title: Message Title










 

 Jason Antman updated an issue











 






 Puppet /  PUP-1364



  Yum package arch and version ensuring failing 










Change By:

 Jason Antman




Component/s:

 Types and Providers




Labels:

 customer redmine  yum












   

 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-1353) PR (2221): (PUP-1282) Express Windows specific gem dependencies - joshcooper

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2221): (PUP-1282) Express Windows specific gem dependencies - joshcooper 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 Puppet /  PUP-1353



  PR (2221): (PUP-1282) Express Windows specific gem dependencies - joshcooper 







 h2. (PUP-1282) Express Windows specific gem dependencies   * Author: Josh Cooper <>  * Company:   * Github ID: [joshcooper|https://github.com/joshcooper]  * [Pull Request 2221 Discussion|https://github.com/puppetlabs/puppet/pull/2221]  * [Pull Request 2221 File Diff|https://github.com/puppetlabs/puppet/pull/2221/files]  h2. Pull Request Description   ...















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




 














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

Jira (PUP-1352) PR (2220): (PUP-672) TrustedInformation handles a nil certificate. - jpartlow

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2220): (PUP-672) TrustedInformation handles a nil certificate. - jpartlow 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 Puppet /  PUP-1352



  PR (2220): (PUP-672) TrustedInformation handles a nil certificate. - jpartlow 







 h2. (PUP-672) TrustedInformation handles a nil certificate.   * Author: Josh Partlow <>  * Company:   * Github ID: [jpartlow|https://github.com/jpartlow]  * [Pull Request 2220 Discussion|https://github.com/puppetlabs/puppet/pull/2220]  * [Pull Request 2220 File Diff|https://github.com/puppetlabs/puppet/pull/2220/files]  h2. Pull Request Description   ...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-1345) PR (2213): (PUP-716) W.I.P For early review only - DO NOT MERGE - hlindberg

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2213): (PUP-716) W.I.P For early review only - DO NOT MERGE - hlindberg 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 Puppet /  PUP-1345



  PR (2213): (PUP-716) W.I.P For early review only - DO NOT MERGE - hlindberg 







 h2. (PUP-716) W.I.P For early review only - DO NOT MERGE   * Author: Henrik Lindberg <>  * Company: Cloudsmith Inc.  * Github ID: [hlindberg|https://github.com/hlindberg]  * [Pull Request 2213 Discussion|https://github.com/puppetlabs/puppet/pull/2213]  * [Pull Request 2213 File Diff|https://github.com/puppetlabs/puppet/pull/2213/files]  h2. Pull Request D...















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




 














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

Jira (PUP-683) Puppet yum provider for package resource does not appear to use 'release' tag to ensure latest

Title: Message Title










 

 Jason Antman updated an issue











 






 Puppet /  PUP-683



  Puppet yum provider for package resource does not appear to use 'release' tag to ensure latest 










Change By:

 Jason Antman




Component/s:

 Types and Providers




Labels:

 customer redmine  yum












   

 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-1244) Yum provider using "version-release" to validate installation.

Title: Message Title










 

 Jason Antman updated an issue











 






 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 










Change By:

 Jason Antman




Component/s:

 Types and Providers




Labels:

 redmine  yum












   

 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-1217) yum provider + package groups giving unnecessary errors

Title: Message Title










 

 Jason Antman updated an issue











 






 Puppet /  PUP-1217



  yum provider + package groups giving unnecessary errors 










Change By:

 Jason Antman




Component/s:

 Types and Providers




Labels:

 redmine  yum












   

 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-682) Comparing package versions in puppet behaves differently to yum

Title: Message Title










 

 Jason Antman updated an issue











 






 Puppet /  PUP-682



  Comparing package versions in puppet behaves differently to yum 










Change By:

 Jason Antman




Component/s:

 Types and Providers




Labels:

 customer redmine  yum












   

 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-1068) Puppet master can't submit reports to an HTTP server using basic auth

2014-01-03 Thread Joshua Partlow (JIRA)

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Puppet master can't submit reports to an HTTP server using basic auth 










Merged to master in 539d337












   

 Add Comment











 













 Puppet /  PUP-1068



  Puppet master can't submit reports to an HTTP server using basic auth 







 If you turn on HTTP basic auth in Puppet Dashboard's vhost config, Puppet is unable to communicate with it. Setting a `reporturl` of (for example)  will not cause puppet to authenticate itself to Dashboard.   The ENC script doesn't work either; see issue #5126. The approach in Matt and my patch in comment 7 c...















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




 














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

Jira (PUP-1351) PR (2219): (PUP-1068) Add basic auth to HTTP Connection and HTTP Reports - zaphod42

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2219): (PUP-1068) Add basic auth to HTTP Connection and HTTP Reports - zaphod42 










Pull request (PUP-1068) Add basic auth to HTTP Connection and HTTP Reports has been closed.












   

 Add Comment











 













 Puppet /  PUP-1351



  PR (2219): (PUP-1068) Add basic auth to HTTP Connection and HTTP Reports - zaphod42 







 h2. (PUP-1068) Add basic auth to HTTP Connection and HTTP Reports   * Author: Andrew Parker <>  * Company: Puppet Labs  * Github ID: [zaphod42|https://github.com/zaphod42]  * [Pull Request 2219 Discussion|https://github.com/puppetlabs/puppet/pull/2219]  * [Pull Request 2219 File Diff|https://github.com/puppetlabs/puppet/pull/2219/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

Jira (PUP-1351) PR (2219): (PUP-1068) Add basic auth to HTTP Connection and HTTP Reports - zaphod42

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2219): (PUP-1068) Add basic auth to HTTP Connection and HTTP Reports - zaphod42 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 Puppet /  PUP-1351



  PR (2219): (PUP-1068) Add basic auth to HTTP Connection and HTTP Reports - zaphod42 







 h2. (PUP-1068) Add basic auth to HTTP Connection and HTTP Reports   * Author: Andrew Parker <>  * Company: Puppet Labs  * Github ID: [zaphod42|https://github.com/zaphod42]  * [Pull Request 2219 Discussion|https://github.com/puppetlabs/puppet/pull/2219]  * [Pull Request 2219 File Diff|https://github.com/puppetlabs/puppet/pull/2219/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.googl

Jira (PUP-1144) No longer allows variables with leading underscores

2014-01-03 Thread Henrik Lindberg (JIRA)

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: No longer allows variables with leading underscores 










Fix pushed to stable for inclusion in 3.4.2. Fix is also on master since the behavior was also present if using the combination --parser future --evaluator current (which is available in 3.5.0).












   

 Add Comment











 













 Puppet /  PUP-1144



  No longer allows variables with leading underscores 







 It appears that puppet 3.4 has changed the rules for allowed variable names. A variable with a leading underscore (e.g. {{$_last}}), now results in an error.   https://github.com/puppetlabs/puppetlabs-apache/pull/540















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-1144) No longer allows variables with leading underscores

2014-01-03 Thread Henrik Lindberg (JIRA)

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: No longer allows variables with leading underscores 










reopened because this is a bug after all and it blocks people from using the --future parser in 3.4.0 with the apache module.












   

 Add Comment











 













 Puppet /  PUP-1144



  No longer allows variables with leading underscores 







 It appears that puppet 3.4 has changed the rules for allowed variable names. A variable with a leading underscore (e.g. {{$_last}}), now results in an error.   https://github.com/puppetlabs/puppetlabs-apache/pull/540















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-1144) No longer allows variables with leading underscores

2014-01-03 Thread Henrik Lindberg (JIRA)

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-1144



  No longer allows variables with leading underscores 










Change By:

 Henrik Lindberg




Fix Version/s:

 3.4.0




Fix Version/s:

 3.4.2












   

 Add Comment











 










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




 














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

Jira (PUP-1353) PR (2221): (PUP-1282) Express Windows specific gem dependencies - joshcooper

Title: Message Title










 

 gepetto-bot created an issue











 






 Puppet /  PUP-1353



  PR (2221): (PUP-1282) Express Windows specific gem dependencies - joshcooper 










Issue Type:

  Task




Assignee:


 Unassigned




Components:


 Community




Created:


 03/Jan/14 4:35 PM




Priority:

  Normal




Reporter:

 gepetto-bot










(PUP-1282) Express Windows specific gem dependencies


Author: Josh Cooper <>


Company:


Github ID: joshcooper


Pull Request 2221 Discussion


Pull Request 2221 File Diff


Pull Request Description

Previously, if a ruby module on windows tried to use puppet as a library, the calling module had to know about puppet's platform specific dependencies. This comes up when trying to develop and test puppet modules on windows.
This commit adds the windows specific gems to project_data.yaml, and up

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

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






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










Comments from HC on how to do FR:
let's see, you could start a daemonized puppet agent, touch the instrumentation log file mentioned and see it blow up, then restart and touch just changing nsecs and see it not blow up...I think. I might be missing some steps.












   

 Add Comment











 













 Puppet /  PUP-724



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














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




 














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

Jira (HI-126) Build windows specific gem

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Hiera /  HI-126



  Build windows specific gem 










Change By:

 Joshua Cooper




Fix Version/s:

 1.4.0












   

 Add Comment











 










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




 














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

Jira (PUP-1282) puppet gem does not include platform specific gem dependencies

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1282



  puppet gem does not include platform specific gem dependencies 










Change By:

 Joshua Cooper




Fix Version/s:

 3.5.0












   

 Add Comment











 










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




 














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

Jira (FACT-186) Build windows specific gem

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Facter /  FACT-186



  Build windows specific gem 










Change By:

 Joshua Cooper




Fix Version/s:

 2.0












   

 Add Comment











 










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




 














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

Jira (PUP-672) Informational certificate extensions should be exposed inside the Puppet DSL

2014-01-03 Thread Joshua Partlow (JIRA)

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Informational certificate extensions should be exposed inside the Puppet DSL 










PR 2220 has the fix for the external ca failure.












   

 Add Comment











 













 Puppet /  PUP-672



  Informational certificate extensions should be exposed inside the Puppet DSL 







 Additional information may be encoded in certificate extensions, and when present should be available in the Puppet DSL. Certificate extensions in a specific subtree of an OID should be parsed out in some manner and exposed in some manner, in a specific namespace that indicates that the information is encoded in the certificate itself.   The OID subtree ...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-1352) PR (2220): (PUP-672) TrustedInformation handles a nil certificate. - jpartlow

Title: Message Title










 

 gepetto-bot created an issue











 






 Puppet /  PUP-1352



  PR (2220): (PUP-672) TrustedInformation handles a nil certificate. - jpartlow 










Issue Type:

  Task




Assignee:


 Unassigned




Components:


 Community




Created:


 03/Jan/14 4:16 PM




Priority:

  Normal




Reporter:

 gepetto-bot










(PUP-672) TrustedInformation handles a nil certificate.


Author: Josh Partlow <>


Company:


Github ID: jpartlow


Pull Request 2220 Discussion


Pull Request 2220 File Diff


Pull Request Description

Acceptance caught an issue with an external ca not passing the certificate info (the acceptance/tests/external_ca_support/apache_external_root_ca.rb had this issue prior to +ExportCertData being added to the SSLOptions in acceptance/tests/external_ca_support/fixtures/httpd.conf).
Modifying th

Jira (PUP-1304) Is a new version created for the next version in the series?

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Is a new version created for the next version in the series? 










https://tickets.puppetlabs.com/browse/PUP/fixforversion/11311












   

 Add Comment











 













 Puppet /  PUP-1304



  Is a new version created for the next version in the series? 














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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-1304) Is a new version created for the next version in the series?

Title: Message Title










 

 Kylo Ginsberg assigned an issue to Kylo Ginsberg











 






 Puppet /  PUP-1304



  Is a new version created for the next version in the series? 










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 (PUP-1302) Is there a bug targeting at the release for every commit

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Is there a bug targeting at the release for every commit 










https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20fixVersion%20%3D%20%223.4.2%22%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC
Thought: don't mark the release tickets themselves with the release number, so the above url omits them?












   

 Add Comment











 













 Puppet /  PUP-1302



  Is there a bug targeting at the release for every commit 














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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-1303) Is there a commit for every bug targeted at the release

Title: Message Title










 

 Kylo Ginsberg assigned an issue to Kylo Ginsberg











 






 Puppet /  PUP-1303



  Is there a commit for every bug targeted at the release 










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 (PUP-1099) incorrect permissions in rpms

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1099



  incorrect permissions in rpms 










Change By:

 Kylo Ginsberg




Fix Version/s:

 3.4.2












   

 Add Comment











 










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




 














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

Jira (PUP-1302) Is there a bug targeting at the release for every commit

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Is there a bug targeting at the release for every commit 










The list is:


PUP-724


PUP-1255




PUP-1099





PUP-1015
 (aka redmine #23403)














   

 Add Comment











 













 Puppet /  PUP-1302



  Is there a bug targeting at the release for every commit 














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




 














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

Jira (PUP-1302) Is there a bug targeting at the release for every commit

Title: Message Title










 

 Kylo Ginsberg assigned an issue to Kylo Ginsberg











 






 Puppet /  PUP-1302



  Is there a bug targeting at the release for every commit 










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 (PUP-1349) PR (2217): Maint/master/revert 6857 test changes and match fedora - jpartlow

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2217): Maint/master/revert 6857 test changes and match fedora - jpartlow 










Pull request Maint/master/revert 6857 test changes and match fedora has been closed.












   

 Add Comment











 













 Puppet /  PUP-1349



  PR (2217): Maint/master/revert 6857 test changes and match fedora - jpartlow 







 h2. Maint/master/revert 6857 test changes and match fedora   * Author: Josh Partlow <>  * Company:   * Github ID: [jpartlow|https://github.com/jpartlow]  * [Pull Request 2217 Discussion|https://github.com/puppetlabs/puppet/pull/2217]  * [Pull Request 2217 File Diff|https://github.com/puppetlabs/puppet/pull/2217/files]  h2. Pull Request Description   M...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-1301) Are tests passing (spec, acceptance, all platforms)

Title: Message Title










 

 Kylo Ginsberg assigned an issue to Kylo Ginsberg











 






 Puppet /  PUP-1301



  Are tests passing (spec, acceptance, all platforms) 










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 (PUP-1355) PR (2217): Maint/master/revert 6857 test changes and match fedora - jpartlow

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2217): Maint/master/revert 6857 test changes and match fedora - jpartlow 










Pull request Maint/master/revert 6857 test changes and match fedora has been closed.












   

 Add Comment











 













 Puppet /  PUP-1355



  PR (2217): Maint/master/revert 6857 test changes and match fedora - jpartlow 







 h2. Maint/master/revert 6857 test changes and match fedora   * Author: Josh Partlow <>  * Company:   * Github ID: [jpartlow|https://github.com/jpartlow]  * [Pull Request 2217 Discussion|https://github.com/puppetlabs/puppet/pull/2217]  * [Pull Request 2217 File Diff|https://github.com/puppetlabs/puppet/pull/2217/files]  h2. Pull Request Description   M...















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




 














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

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

2014-01-03 Thread Joshua Partlow (JIRA)

Title: Message Title










 

 Joshua Partlow commented on an issue











 






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










Cherry-picked to puppet/stable in 98e9219 Merged to pe-puppet/3.2.x in 5af6e12












   

 Add Comment











 













 Puppet /  PUP-724



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














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




 














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

Jira (PUP-1351) PR (2219): (PUP-1068) Add basic auth to HTTP Connection and HTTP Reports - zaphod42

Title: Message Title










 

 gepetto-bot created an issue











 






 Puppet /  PUP-1351



  PR (2219): (PUP-1068) Add basic auth to HTTP Connection and HTTP Reports - zaphod42 










Issue Type:

  Task




Assignee:


 Unassigned




Components:


 Community




Created:


 03/Jan/14 3:29 PM




Priority:

  Normal




Reporter:

 gepetto-bot










(PUP-1068) Add basic auth to HTTP Connection and HTTP Reports


Author: Andrew Parker <>


Company: Puppet Labs


Github ID: zaphod42


Pull Request 2219 Discussion


Pull Request 2219 File Diff


Pull Request Description

This adds logic in Puppet::Reports::Http to properly handle HTTP basic auth using the form http://username:password@host/path
In order to make this work more clearly, this also adds actual parameters to the connection class's #get, #post, etc methods. The defaults are

Jira (PUP-736) Encoding mis-matches cause package prefetching to fail

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Encoding mis-matches cause package prefetching to fail 










After some discussion on HipChat we decided to provide a short-term quick-fix by yanking the functionality that added description fetching for rpm/apt. This functionality was introduced but never used by any other projects, so should be sfe to remove.
This is a quick-fix and doesn't address the broader issue of checking for encoding incompatibility in these providers. That work is still being scoped.












   

 Add Comment











 













 Puppet /  PUP-736



  Encoding mis-matches cause package prefetching to fail 







 One of our RPM packages has some UTF-8 characters in its description, leading to an exception ("Error: Could not prefetch package provider 'yum': invalid byte sequence in US-ASCII") in rpm.rb, causing no packages to be upgraded as the yumhelper.py invocation code raises that error.   Priority=High because it breaks file { ensure => latest; }.















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




 














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

Jira (PUP-1367) behavior change within 2.6 makes it impossible to override class parameters of "included" parametrized classes

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1367



  behavior change within 2.6 makes it impossible to override class parameters of "included" parametrized classes 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 03/Jan/14 3:09 PM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










In 2.6.1 the following recipe:
 class a( $b_c =  { 'b' => 'foo' }
) { notice $a::b_c if $a::b_c  { notice $a::b_c['b'] }
}
class b { class {'a': b_c => false }
}
class b::c inherits b { Class['a']{ b_c =>  { 'b' => 'bleh' }
 } }
class b::d  { include ::b::c }
include b::d 
produces the following output:
 $ puppet foo.pp  notice: Scope(Class[A]): bbleh notice: Scope(Class[A]): bleh 
Which is what I expected. However with 2.6.3 it produces the following output:



puppet foo.pp notice: Scope(Class[A]): false 


Imho likely the changes for #4778 and #5074 are responsible for that behavior change.

Jira (PUP-736) Encoding mis-matches cause package prefetching to fail

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-736



  Encoding mis-matches cause package prefetching to fail 










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-736) Encoding mis-matches cause package prefetching to fail

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-736



  Encoding mis-matches cause package prefetching to fail 










Change By:

 Kylo Ginsberg




Sprint:

 Week 2014-1-8 to 2014-1-15












   

 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-736) Encoding mis-matches cause package prefetching to fail

2014-01-03 Thread Charlie Sharpsteen (JIRA)

Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: Encoding mis-matches cause package prefetching to fail 










An easy re-production environment for this issue is Ubuntu 12.04. The kbd project, which is installed by default, contains smart quotes in the package description.












   

 Add Comment











 













 Puppet /  PUP-736



  Encoding mis-matches cause package prefetching to fail 







 One of our RPM packages has some UTF-8 characters in its description, leading to an exception ("Error: Could not prefetch package provider 'yum': invalid byte sequence in US-ASCII") in rpm.rb, causing no packages to be upgraded as the yumhelper.py invocation code raises that error.   Priority=High because it breaks file { ensure => latest; }.















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send 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-1366) yum provider doesn't respect items provided by a package, only the package name

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1366



  yum provider doesn't respect items provided by a package, only the package name 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 03/Jan/14 2:48 PM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










A simple use case:
In EL5 and earlier, the curl development headers were included in a package called curl-devel. In EL6 and later that package was renamed to libcurl-devel. However, the libcurl-devel package still provides curl-devel. 
When using something like 
 package  { "curl-devel": ensure => installed }
puppet looks for this package every time. 
 [root@centos6-32 ~]# puppet resource package libcurl-devel warning: Package kernel found in both yum and yum; skipping the yum version warning: Package gpg-pubkey found in both yum and yum; skipping the yum version package  { 'libcurl-devel': ensure => '7.19.7-26.el6_1.2', }
 [root@centos6-32 ~]# puppet resource package curl-devel warning: Package kernel found in both yum and yum; skipping the yum version warning: Package gpg-pubkey found in both yum and yum; skipping the yum version package  { 'curl-devel': ensure => 'absent', }
 [root@centos6-32 ~]# rpm -q --whatprovides curl-devel libcurl-devel-7.19.7-26.el6_1.2.i686 [root@centos6-32 ~]# 
The yum provider should basically use the way yum work to make this happen. If I do "yum install curl-devel" on EL6, it pulls in libcurl-d

Jira (PUP-1366) yum provider doesn't respect items provided by a package, only the package name

Title: Message Title










 

 Jason Antman updated an issue











 






 Puppet /  PUP-1366



  yum provider doesn't respect items provided by a package, only the package name 










Change By:

 Jason Antman




Component/s:

 Types and Providers




Labels:

 redmine  yum












   

 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-1365) Yum provider doesn't understand globs

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1365



  Yum provider doesn't understand globs 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 03/Jan/14 2:47 PM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










Yum understands globs in regards to version numbers. On the command line, if I say "`yum install puppet-2.6*`", I will get the latest version of 2.6 available, even if a 2.7 version exists in my repositories.
If I use this in a manifest, such as  `ensure => '2.6*'`, puppet attempts to install "literally `puppet-2.6*`", as if asterisk was a version number, producing an error err: /Stage[main]/Puppet/Package[puppet]/ensure: change from 2.6.14-1.el5 to 2.6* failed: Could not update: Failed to update to version 2.6*, got version 2.6.14-1.el5 instead
Yum exits with `$? = 0` with this format.












   

 Add Comment

Jira (PUP-1364) Yum package arch and version ensuring failing

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1364



  Yum package arch and version ensuring failing 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 03/Jan/14 2:46 PM




Labels:


 redmine customer




Priority:

  Normal




Reporter:

 redmine.exporter










After lots of trial and error I found a bug in our current Puppet version
Having a package line like so:
 package  { "firefox.x86_64": ensure => "3.0.12-1.el5.centos", require => Package["xulrunner.x86_64"] }

Would fail with debug output:  *_ debug: //Node[om012274.drd.int]/workstation/workstation_centos53/mozillasuite53/Package[firefox.x86_64]: Changing ensure debug: //Node[om012274.drd.int]/workstation/workstation_centos53/mozillasuite53/Package[firefox.x86_64]: 1 change(s) debug: Package[firefox.x86_64](provider=yum): Ensuring => 3.0.12-1.el5.centos debug: Puppet::Type::Package::ProviderYum: Executing '/usr/bin/yum -d 0 -e 0 -y install firefox.x86_64-3.0.12-1.el5.centos' debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm -q firefox.x86_64 --nosignature --nodigest --qf % {NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH} ' err: //Node[om012274.drd.int]/workstation/workstation_centos53/mozillasuite53/Package[firefox.x86_64]/ensure: change from absent to 3.0.12-1.el5.centos failed: Could not update: Could not find package firefox.x86_64 at /etc/puppet/manifests/CentOS.pp:149_*It didn't matter if I listed ver-release or just ver, same sort of error; it appends the version-[release] to the package name and arch. Which obviously fails as yum packages must be referred to like so:   name name.arch name

Jira (PUP-1363) yum helper fails when using a custom yum plugin with custom variables

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1363



  yum helper fails when using a custom yum plugin with custom variables 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 03/Jan/14 2:31 PM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










We have a custom yum plugin that provides a custom variable for use in our .repo files and the Puppet yum helper does not function correctly with custom variables.
First, we ensure our yum plugin is installed on all machines:
 package  { 'SNC-2-1-1-1:.:.:snc-yum': name => 'snc-yum', ensure => installed }
 
Then, we set up our repositories.
 sncyumrepo  { 'SNC-2-1-3-1:.:.:yumrepo-base': name => 'base', alias => 'base', descr => 'CentOS Base Repository', baseurl => 'http://repo/centos/$sncversion/os/$basearch/', enabled => 1, gpgcheck => 1, gpgkey => 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever', require => File['yumparentdir'] }
Notice the baseurl contains our custom variable: $sncversion. This is the variable that is provided by the yum plugin.
This will write our the base.repo file WITH that variable in the final output. The variable is the replaced by yum just like the built-in yum variable $releasever.
Then, we attempt to use the base.repo and it fails!
 package  { 'SNC-2-1-1-1:.:.:any-package': name => 'any-package', ensure => installed }

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

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1362



  Rubyize yumhelper.py to remove dependency on python 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 03/Jan/14 2:31 PM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










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.












   

 Add Comment

Jira (PUP-1350) PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 Puppet /  PUP-1350



  PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog 







 h2. (maint) Add a diagnostic check that lmhosts is running   * Author: Kylo Ginsberg <>  * Company:   * Github ID: [kylog|https://github.com/kylog]  * [Pull Request 2218 Discussion|https://github.com/puppetlabs/puppet/pull/2218]  * [Pull Request 2218 File Diff|https://github.com/puppetlabs/puppet/pull/2218/files]  h2. Pull Request Description ...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-1356) PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 Puppet /  PUP-1356



  PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog 







 h2. (maint) Add a diagnostic check that lmhosts is running   * Author: Kylo Ginsberg <>  * Company:   * Github ID: [kylog|https://github.com/kylog]  * [Pull Request 2218 Discussion|https://github.com/puppetlabs/puppet/pull/2218]  * [Pull Request 2218 File Diff|https://github.com/puppetlabs/puppet/pull/2218/files]  h2. Pull Request Description ...















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




 














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

Title: Message Title










 

 Joshua Cooper moved an issue











 






 Hiera /  HI-126



  Build windows specific gem 










Change By:

 Joshua Cooper




Key:

 FACT HI - 187 126




Project:

 Facter Hiera












   

 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-126) Build windows specific gem

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Hiera /  HI-126



  Build windows specific gem 










Change By:

 Joshua Cooper




Issue Type:

 Bug Task












   

 Add Comment











 










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




 














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

Jira (FACT-187) Build windows specific gem

Title: Message Title










 

 Joshua Cooper created an issue











 






 Facter /  FACT-187



  Build windows specific gem 










Issue Type:

  Bug




Assignee:

 Eric Sorenson




Created:


 03/Jan/14 1:49 PM




Labels:


 windows




Priority:

  Normal




Reporter:

 Joshua Cooper










See PUP-1282












   

 Add Comment











 










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

Jira (FACT-187) Build windows specific gem

Title: Message Title










 

 Joshua Cooper assigned an issue to Joshua Cooper











 






 Facter /  FACT-187



  Build windows specific gem 










Change By:

 Joshua Cooper




Assignee:

 Eric Sorenson 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 (FACT-186) Build windows specific gem

Title: Message Title










 

 Joshua Cooper created an issue











 






 Facter /  FACT-186



  Build windows specific gem 










Issue Type:

  Bug




Assignee:

 Eric Sorenson




Created:


 03/Jan/14 1:49 PM




Priority:

  Normal




Reporter:

 Joshua Cooper










See PUP-1282












   

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

Jira (FACT-186) Build windows specific gem

Title: Message Title










 

 Joshua Cooper assigned an issue to Joshua Cooper











 






 Facter /  FACT-186



  Build windows specific gem 










Change By:

 Joshua Cooper




Assignee:

 Eric Sorenson Joshua Cooper












   

 Add Comment











 










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




 














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

Jira (PDB-271) Update 1.5.x and 1.6.x docs

2014-01-03 Thread Ryan Senior (JIRA)

Title: Message Title










 

 Ryan Senior updated an issue











 






 PuppetDB /  PDB-271



  Update 1.5.x and 1.6.x docs 










Change By:

 Ryan Senior




Summary:

 Update 1.5.x and 1.6.x  docsReport  docs  still say "experimental









 Probably JDK 1.6  should  get updated  say it's deprecated : https://docs.puppetlabs.com/puppetdb/latest/#nix-server-with-jdk-16Report docs still say "experimental: http://docs.puppetlabs.com/puppetdb/1.5/api/wire_format/report_format.htmlhttp://docs.puppetlabs.com/puppetdb/1.5/api/commands.htmlhttp://docs.puppetlabs.com/puppetdb/1.6/api/wire_format/report_format.htmlhttp://docs.puppetlabs.com/puppetdb/1.6/api/commands.html












   

 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-271) Update 1.5.x and 1.6.x docsReport docs still say "experimental

2014-01-03 Thread Ryan Senior (JIRA)

Title: Message Title










 

 Ryan Senior updated an issue











 






 PuppetDB /  PDB-271



  Update 1.5.x and 1.6.x docsReport docs still say "experimental 










Change By:

 Ryan Senior




Summary:

 Report Update 1.5.x and 1.6.x docsReport  docs still say "experimental












   

 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-271) Report docs still say "experimental

2014-01-03 Thread Ryan Senior (JIRA)

Title: Message Title










 

 Ryan Senior created an issue











 






 PuppetDB /  PDB-271



  Report docs still say "experimental 










Issue Type:

  Bug




Affects Versions:


 1.6.0, 1.5.X




Assignee:


 Unassigned




Created:


 03/Jan/14 1:38 PM




Fix Versions:


 1.6.0, 1.5.X




Priority:

  Normal




Reporter:

 Ryan Senior










Probably should get updated:
http://docs.puppetlabs.com/puppetdb/1.5/api/wire_format/report_format.html http://docs.puppetlabs.com/puppetdb/1.5/api/commands.html
http://docs.puppetlabs.com/puppetdb/1.6/api/wire_format/report_format.html http://docs.puppetlabs.com/puppetdb/1.6/api/commands.html












   

 Add Comment

Jira (PUP-1361) Puppet `rake gen_manpages` manpages.task broken

2014-01-03 Thread Matthaus Owens (JIRA)

Title: Message Title










 

 Matthaus Owens created an issue











 






 Puppet /  PUP-1361



  Puppet `rake gen_manpages` manpages.task broken 










Issue Type:

  Bug




Affects Versions:


 3.2.1




Assignee:


 Unassigned




Created:


 03/Jan/14 1:24 PM




Priority:

  Normal




Reporter:

 Matthaus Owens










I saw the following on puppet 3.4.1-21-g98e9219, but seems to be broken for most/all of the 3 series so far.


matthaus@wyclef  /Users/matthaus/src/puppet [stable]> rake gen_manpages --trace
** Invoke gen_manpages (first_time)
** Execute gen_manpages
rake aborted!
"--name=": already defined in puppet
/Users/matthaus/src/puppet/lib/puppet/interface/option.rb:36:in `block in initialize'
/Users/matthaus/src/puppet/lib/puppet/interface/option.rb:18:in `each'
/Users/matthaus/src/puppet/lib/puppet/interface/option.rb:18:in `initialize'
/Users/matthaus/src/puppet/lib/puppet/interface/option_builder.rb:17:in `new'
/Users/matthaus/src/puppet/lib/puppet/interface/option_builder.rb:17:in `initialize'
/Users/matthaus/src/puppet/lib/puppet/interface/option_builder.rb:12:in `new'
/Users/matthaus/src/puppet/lib/puppet/interface/option_builder.rb:12:in `build'
/Users/matthaus/src/puppet/lib/puppet/interface/action_builder.rb:93:in `option'
/Users/matthaus/.puppet/var/lib/puppet/face/dashboard.rb:102:in `block (2 levels) in '
/Users/matthaus/src/puppet/lib/puppet/interface/action_builder.rb:146:in `instance_eval'
/Users/matthaus/src/puppet/lib/puppet/interface/action_builder.rb:146:in `initialize'
/Users/matthaus/src/puppet/lib/puppet/interface/action_builder.rb:17:in `new'
/Users/matthaus/src/puppet/lib/puppet/interface/action_builder.rb:17:in `build'
/Users/matthaus/src/pu

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

2014-01-03 Thread Justin Honold (JIRA)

Title: Message Title










 

 Justin Honold created an issue











 






 Facter /  FACT-185



  No EC2 facts shown on newly-built Amazon Linux host 










Issue Type:

  Bug




Affects Versions:


 1.7.4




Assignee:

 Eric Sorenson




Components:


 Community




Created:


 03/Jan/14 1:16 PM




Environment:


Amazon Linux AMI release 2013.09 ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]




Priority:

  Normal




Reporter:

 Justin Honold










`facter|grep ec2` yields only the 'domain' and 'fqdn' facts for me, not a gaggle of them including stuff like 'ec2_profile'. The same versions on another host are working fine. Any tips on troubleshooting? An strace isn't showing anything promising to me, although it confirms that it's firing up the ec2.rb library.

Jira (PUP-1300) Start 3.4.2 Final - Jan 6, 2014

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1300



  Start 3.4.2 Final - Jan 6, 2014 










Change By:

 Kylo Ginsberg




Summary:

 Start 3.4.2 Final -  Dec 31  Jan 6 ,  2013  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 (PDB-270) PR (783): Update documentation headers for 1.6.x - kbarber

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (783): Update documentation headers for 1.6.x - kbarber 










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












   

 Add Comment











 













 PuppetDB /  PDB-270



  PR (783): Update documentation headers for 1.6.x - kbarber 







 h2. Update documentation headers for 1.6.x   * Author: Ken Barber   * Company: Puppetlabs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 783 Discussion|https://github.com/puppetlabs/puppetdb/pull/783]  * [Pull Request 783 File Diff|https://github.com/puppetlabs/puppetdb/pull/783/files]  h2. Pull Request Description --...















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




 














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

Jira (PDB-270) PR (783): Update documentation headers for 1.6.x - kbarber

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (783): Update documentation headers for 1.6.x - kbarber 










Pull request Update documentation headers for 1.6.x has been closed.












   

 Add Comment











 













 PuppetDB /  PDB-270



  PR (783): Update documentation headers for 1.6.x - kbarber 







 h2. Update documentation headers for 1.6.x   * Author: Ken Barber   * Company: Puppetlabs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 783 Discussion|https://github.com/puppetlabs/puppetdb/pull/783]  * [Pull Request 783 File Diff|https://github.com/puppetlabs/puppetdb/pull/783/files]  h2. Pull Request Description --...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-1358) Push fixes to cover the PE 3.X series

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Push fixes to cover the PE 3.X series 










Andrew Parker merged 9f16821 into 2.8.x and 4ef269d into 3.1.x. The fix to the specs when run on 2012 3b4e5cb do not need to be backported, since those tests don't exist prior to pe-puppet/3.2.x












   

 Add Comment











 













 Puppet /  PUP-1358



  Push fixes to cover the PE 3.X series 














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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-226) PR (775): Remove unused `test:package` rake task - cprice404

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-226



  PR (775): Remove unused `test:package` rake task - cprice404 










Change By:

 Kenneth Barber




Sprint:

 20140101 to 20140108












   

 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-225) PR (774): (maint) Add fedora 20 to mock list - melissaanne

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-225



  PR (774): (maint) Add fedora 20 to mock list - melissaanne 










Change By:

 Kenneth Barber




Sprint:

 20140101 to 20140108












   

 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-248) PR (781): Update changelog for 1.6.0 - grimradical

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-248



  PR (781): Update changelog for 1.6.0 - grimradical 










Change By:

 Kenneth Barber




Sprint:

 20140101 to 20140108












   

 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-227) PR (107): Fix puppetlabs#106 and one other bug when disable_ssl = true - ebarrere

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-227



  PR (107): Fix puppetlabs#106 and one other bug when disable_ssl = true - ebarrere 










Change By:

 Kenneth Barber




Sprint:

 20140101 to 20140108












   

 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-222) PR (772): FOR REVIEW: Port PuppetDB to use trapperkeeper - cprice404

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-222



  PR (772): FOR REVIEW: Port PuppetDB to use trapperkeeper - cprice404 










Change By:

 Kenneth Barber




Sprint:

 20140101 to 20140108












   

 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-224) PR (773): FOR REVIEW: Port PuppetDB to use trapperkeeper - nwolfe

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-224



  PR (773): FOR REVIEW: Port PuppetDB to use trapperkeeper - nwolfe 










Change By:

 Kenneth Barber




Sprint:

 20140101 to 20140108












   

 Add Comment











 










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




 














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

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

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-243



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










Change By:

 Kenneth Barber




Sprint:

 20140101 to 20140108












   

 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