date:20140811

Title: Message Title










 

 Raphaël Pinson created an issue











 






 Facter /  FACT-639



  EC2 facts should not be confined to Xen 










Issue Type:

  Bug




Affects Versions:


 2.1.0




Assignee:

 Eric Sorenson




Created:


 11/Aug/14 2:14 AM




Priority:

  Normal




Reporter:

 Raphaël Pinson










EC2 facts are also declared on Openstack machines, which can use more than just Xen as hypervisor. The EC2 facts should thus not be confined to Xen.
This bug was introduced by https://github.com/puppetlabs/facter/commit/07f5dfbeee62aaab2c6028c21b5b308b13b3f267












   

 Add Comment











 










 Thi

Jira (FACT-639) EC2 facts should not be confined to Xen

2014-08-11 Thread Marian Neagul (JIRA)

Title: Message Title










 

 Marian Neagul commented on an issue











 






  Re: EC2 facts should not be confined to Xen 










We have same problem on our Eucalyptus private cloud. This is basically a show stopper.












   

 Add Comment











 













 Facter /  FACT-639



  EC2 facts should not be confined to Xen 







 EC2 facts are also declared on Openstack machines, which can use more than just Xen as hypervisor. The EC2 facts should thus not be confined to Xen.   This bug was introduced by https://github.com/puppetlabs/facter/commit/07f5dfbeee62aaab2c6028c21b5b308b13b3f267















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




 














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

Jira (FACT-639) EC2 facts should not be confined to Xen

Title: Message Title










 

 Raphaël Pinson commented on an issue











 






  Re: EC2 facts should not be confined to Xen 










PR at https://github.com/puppetlabs/facter/pull/748












   

 Add Comment











 













 Facter /  FACT-639



  EC2 facts should not be confined to Xen 







 EC2 facts are also declared on Openstack machines, which can use more than just Xen as hypervisor. The EC2 facts should thus not be confined to Xen.   This bug was introduced by https://github.com/puppetlabs/facter/commit/07f5dfbeee62aaab2c6028c21b5b308b13b3f267















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




 














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

Jira (PDB-814) Add latest-report? query field on reports endpoint

Title: Message Title










 

 Erik Dalén created an issue











 






 PuppetDB /  PDB-814



  Add latest-report? query field on reports endpoint 










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 11/Aug/14 4:26 AM




Priority:

  Normal




Reporter:

 Erik Dalén










It would be good to be able to query for this on the reports endpoint.
I know it isn't needed when querying for a single nodes report directly on this endpoint as you can order by time and limit to one report and thus get the latest one.
However that isn't possible when querying for several nodes at once, or when doing a reports subquery. For example a use case would be to get all failing nodes that have fact role=puppet with a query like this on v4/nodes:





["and", ["in", "certname", ["extract", "certname", ["select-reports", ["and", ["=", "status", "failed"], ["=", "latest-report?", true], ["=", ["fact", "role"], "puppet"]]












   

 Add Comment

Jira (PDB-814) Add latest-report? query field on reports endpoint

Title: Message Title










 

 Erik Dalén updated an issue











 






 PuppetDB /  PDB-814



  Add latest-report? query field on reports endpoint 










Change By:

 Erik Dalén









 It would be good to be able to query for this on the reports endpoint.I know it isn't needed when querying for a single nodes report directly on this endpoint as you can order by time and limit to one report and thus get the latest one.However that isn't possible when querying for several nodes at once, or when doing a reports subquery. For example a use case would be to get all failing nodes that have fact role=puppet with a query like this on v4/nodes:{code}["and",  ["in", "certname",["extract", "certname",  ["select-reports",["and",  ["=", "status", "failed"],  ["=", "latest-report?", true],  ["=", ["fact", "role"], "puppet"]] {code}












   

 Add Comment











 










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




 














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

Jira (PUP-1187) tagmail report sends email when nothing happens

2014-08-11 Thread Jens Pranaitis (JIRA)

Title: Message Title










 

 Jens Pranaitis commented on an issue











 






  Re: tagmail report sends email when nothing happens 










The patch didn't work for us, we still got emails although nothing happened.












   

 Add Comment











 













 Puppet /  PUP-1187



  tagmail report sends email when nothing happens 







 Since upgrading to the 2.7 series (2.6.8 -> 2.7.3), the tagmail report will send an email with 1 line, shown below, after every run. Before the upgrade, it would only send emails when something occurred during the puppet run.   Steps to reproduce:  Enable tagmail report  Execute a puppet run that produces no updates   Expected result:  No email sent  ...















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




 














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

Jira (PDB-808) Factsets endpoint has an issue with ordering with new schema, much like facts

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-808



  Factsets endpoint has an issue with ordering with new schema, much like facts 










Change By:

 Kenneth Barber




Affects Version/s:

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

Jira (PUP-2860) Optimize startup of puppet apply (future parser)

Title: Message Title










 

 Henrik Lindberg assigned an issue to Henrik Lindberg











 






 Puppet /  PUP-2860



  Optimize startup of puppet apply (future parser) 










Change By:

 Henrik Lindberg




Assignee:

 Henrik Lindberg












   

 Add Comment











 










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




 














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

Jira (PUP-2860) Optimize startup of puppet apply (future parser)

Title: Message Title

Henrik Lindberg commented on an issue

Re: Optimize startup of puppet apply (future parser)

The reason for the jump is that the benchmark itself has changed - the earlier version did not include the startup time in the measured time. On my machine the older benchmark shows around 0.40 in on initial run, and after the optimization in shows 0.70. The 0.40 does not include the startup of puppet itself.
To confirm, I started at commit eadb59f (the starting point of the work on 2860) and measured it with the empty_catalog benchmark as it is on master. When running this, the initial run shows the optimized version to be slightly faster 0.70 vs 0.75.
For the defined_types4 benchmark, they come out about equal (larger deviation since the run is slightly longer and it does a lot more IO).
So, I believe that the changes are good although giving only a small performance boost (we also gain the separation of meta model and implementation).
We need to deal with how to handle changing benchmarks. (rename them?) Also, for reporting, the empty_catalog benchmark is kind of meaningless to run 10 times as it is really the cold start that is the focus of that benchmark (OTOH, the remaining 9 runs are so fast (0.0 to 0.01) that it probably does not matter).
Moving back to "ready for review".

Add Comment

Puppet / PUP-2860

Optimize startup of puppet apply (future parser)

The {{puppet apply}} command is very often used as a development tool testing small snippets of puppet as well as larger scenarios. Users may thus the command over and over again. Any delays are very irritating (the smaller the snippet being tested, the more irritation). This creates an impression of Puppet's speed when used in production. (which is f...

Jira (FACT-618) Cherry-pick / reimplement facts on master

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Cherry-pick / reimplement facts on master 










William Hopper If we can export the originals, that brings comments and description across, and adds the backlink to projects.puppetlabs.com, so that'd be nice. Otoh, I just looked at one of them and projects.puppetlabs.com said "this issue is unavailable for export" and I'm not sure why. So that might be a non-starter.
If we can't export the originals, yeah, just create a fresh ticket and add the backlink for whomever is interested in the historical description/comments.
And either way, make them children of this epic. And target them all at 2.2.0.
Sorry for all the ticket-work - but it will be a win when we come to make release notes 












   

 Add Comment











 













 Facter /  FACT-618



  Cherry-pick / reimplement facts on master 







 In FACT-472 we decided to overwrite facter-2 onto the master branch which left a number of commits on master effectively removed. Although this was the least bad solution to the state of facter branches, it left a number of valuable contributions "orphaned".   The purpose of this epic is to first inventory those orphaned contributions, and then cherry-pi...















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

Jira (PUP-3001) Reintroduce dynamic scoping for resource defaults

Title: Message Title










 

 Henrik Lindberg assigned an issue to Henrik Lindberg











 






 Puppet /  PUP-3001



  Reintroduce dynamic scoping for resource defaults 










Change By:

 Henrik Lindberg




Assignee:

 Andy Parker Henrik Lindberg












   

 Add Comment











 










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




 














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

Jira (PUP-3042) If a catalog has a dependency cycle, it does not count as failed

2014-08-11 Thread Lee Lowder (JIRA)

Title: Message Title










 

 Lee Lowder created an issue











 






 Puppet /  PUP-3042



  If a catalog has a dependency cycle, it does not count as failed 










Issue Type:

  Bug




Affects Versions:


 3.6.2




Assignee:


 Unassigned




Created:


 11/Aug/14 9:09 AM




Priority:

  Normal




Reporter:

 Lee Lowder










If a catalog has a dependency cycle in it, the catalog fails to apply, but it counts it as a successful run.


# puppet agent -t
Info: Retrieving plugin
Info: Loading facts in /opt/puppet/share/puppet/modules/postgresql/lib/facter/postgres_default_version.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/stdlib/lib/facter/root_home.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/stdlib/lib/facter/facter_dot_d.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/stdlib/lib/facter/puppet_vardir.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/stdlib/lib/facter/pe_version.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/pe_staging/lib/facter/staging_http_get.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/puppet_enterprise/lib/facter/pe_build.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/puppet_enterprise/lib/facter/windows.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/puppet_enterprise/lib/facter/platform_tag.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/firewall/lib/facter/iptables_version.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/firewall/lib/facter/iptables_persistent_version.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/firewall/lib/facter/ip6tables_version.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/pe_puppe

Jira (PDB-815) PR (1035): (maint) fix order on environments for facts - wkalt

Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-815



  PR (1035): (maint) fix order on environments for facts - wkalt 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 11/Aug/14 9:18 AM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










(maint) fix order on environments for facts


Author: Wyatt Alt <>


Company:


Github ID: wkalt


Pull Request 1035 Discussion


Pull Request 1035 File Diff


Pull Request Description

this fixes an issue with ordering by environment on the facts endpoint and patches the corresponding blind spot in our tests.

(webhooks-id: db32a0e799a7f62745c62a2bd91b7194)

Jira (PUP-511) Specify Resource Expression Evaluation

Title: Message Title










 

 Kurt Wall assigned an issue to Unassigned











 






 Puppet /  PUP-511



  Specify Resource _expression_ Evaluation 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall












   

 Add Comment











 










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




 














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

Jira (PUP-2898) Long form Resource Type reference fools "future parser" this is an override

Title: Message Title










 

 Kurt Wall assigned an issue to Unassigned











 






 Puppet /  PUP-2898



  Long form Resource Type reference fools "future parser" this is an override 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall












   

 Add Comment











 










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




 














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

Jira (PUP-894) Too easy to hit "CRL not yet valid for " (and not very informative)

2014-08-11 Thread Branan Purvine-Riley (JIRA)

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Too easy to hit "CRL not yet valid for " (and not very informative) 










This hit acceptance testing again last night: https://jenkins.puppetlabs.com/job/Puppet-Package-Acceptance-stable/label=acc-coord,platform=squeeze/514/












   

 Add Comment











 













 Puppet /  PUP-894



  Too easy to hit "CRL not yet valid for " (and not very informative) 







 Currently we set the CRL time range to start at 1 second in the past:   https://github.com/puppetlabs/puppet/blob/a8311df5438601a3394d38e37f671626969d50db/lib/puppet/ssl/certificate_revocation_list.rb#L85   However, this creates a window where an agent with a small amount of clock skew can hit the `CRL not yet valid for ` message. This affects bo...















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




 














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

Jira (FACT-619) Inventory orphaned contributions on master

Title: Message Title










 

 William Hopper assigned an issue to William Hopper











 






 Facter /  FACT-619



  Inventory orphaned contributions on master 










Change By:

 William Hopper




Assignee:

 William Hopper












   

 Add Comment











 










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




 














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

Jira (FACT-640) Backport GID fact to Facter / master

Title: Message Title










 

 William Hopper created an issue











 






 Facter /  FACT-640



  Backport GID fact to Facter / master 










Issue Type:

  Improvement




Affects Versions:


 2.2.0




Assignee:

 William Hopper




Created:


 11/Aug/14 9:46 AM




Fix Versions:


 2.2.0




Priority:

  Normal




Reporter:

 William Hopper










This commit was lost in the facter-2 / master merge.












   

 Add Comment

Jira (FACT-641) Backport lost Solaris 10 zfs_version fix back into Facter / master

Title: Message Title










 

 William Hopper created an issue











 






 Facter /  FACT-641



  Backport lost Solaris 10 zfs_version fix back into Facter / master 










Issue Type:

  Improvement




Affects Versions:


 2.2.0




Assignee:

 William Hopper




Created:


 11/Aug/14 9:49 AM




Fix Versions:


 2.2.0




Priority:

  Normal




Reporter:

 William Hopper










This commit was lost in the facter-2 / master merge.












   

 Add Comment

Jira (FACT-642) Backport lost zpool_version fix back into Facter / master

Title: Message Title










 

 William Hopper created an issue











 






 Facter /  FACT-642



  Backport lost zpool_version fix back into Facter / master 










Issue Type:

  Improvement




Affects Versions:


 2.2.0




Assignee:

 William Hopper




Created:


 11/Aug/14 9:50 AM




Fix Versions:


 2.2.0




Priority:

  Normal




Reporter:

 William Hopper










This commit was lost in the facter-2 / master merge.












   

 Add Comment

Jira (FACT-643) Backport lost Rackspace fact into Facter / master

Title: Message Title










 

 William Hopper created an issue











 






 Facter /  FACT-643



  Backport lost Rackspace fact into Facter / master 










Issue Type:

  Improvement




Affects Versions:


 2.2.0




Assignee:

 William Hopper




Created:


 11/Aug/14 9:59 AM




Fix Versions:


 2.2.0




Priority:

  Normal




Reporter:

 William Hopper










This commit was lost in the facter-2 / master merge.












   

 Add Comment

Jira (PUP-2994) puppet parser validate shouldn't puke on exported resources

2014-08-11 Thread Hailee Kenney (JIRA)

Title: Message Title










 

 Hailee Kenney assigned an issue to Hailee Kenney











 






 Puppet /  PUP-2994



  puppet parser validate shouldn't puke on exported resources 










Change By:

 Hailee Kenney




Assignee:

 Hailee Kenney












   

 Add Comment











 










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




 














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

Jira (FACT-642) Backport lost zpool_version fix into Facter / master

Title: Message Title










 

 William Hopper updated an issue











 






 Facter /  FACT-642



  Backport lost zpool_version fix into Facter / master 










Change By:

 William Hopper




Summary:

 Backport lost zpool_version fix  back  into Facter / master












   

 Add Comment











 










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




 














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

Jira (FACT-642) Backport lost zpool_version fix back into Facter / master

Title: Message Title










 

 William Hopper assigned an issue to William Hopper











 






 Facter /  FACT-642



  Backport lost zpool_version fix back into Facter / master 










Change By:

 William Hopper




Assignee:

 William Hopper












   

 Add Comment











 










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




 














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

Jira (FACT-641) Backport lost Solaris 10 zfs_version fix into Facter / master

Title: Message Title










 

 William Hopper updated an issue











 






 Facter /  FACT-641



  Backport lost Solaris 10 zfs_version fix into Facter / master 










Change By:

 William Hopper




Summary:

 Backport lost Solaris 10 zfs_version fix  back  into Facter / master












   

 Add Comment











 










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




 














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

Jira (PUP-1515) Invalid parameter provider for custom types/providers

Title: Message Title










 

 Andy Parker assigned an issue to Charlie Sharpsteen











 







Charlie Sharpsteen is going to take a look into this and see if this is definitively related to PUP-731 or not. If it is, then there isn't really anything we can do about it with the current master setups. If it isn't, then his investigation should uncover a bit clearer the source of the problem.









 Puppet /  PUP-1515



  Invalid parameter provider for custom types/providers 










Change By:

 Andy Parker




Assignee:

 Eric Sorenson Charlie Sharpsteen












   

 Add Comment











 










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




 














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

Jira (FACT-644) Backport lost XCP operatingsystem fact fix into Facter / master

Title: Message Title










 

 William Hopper created an issue











 






 Facter /  FACT-644



  Backport lost XCP operatingsystem fact fix into Facter / master 










Issue Type:

  Improvement




Affects Versions:


 2.2.0




Assignee:

 William Hopper




Created:


 11/Aug/14 10:02 AM




Fix Versions:


 2.2.0




Priority:

  Normal




Reporter:

 William Hopper










This commit was lost in the facter-2 / master merge.












   

 Add Comment

Jira (FACT-618) Cherry-pick / reimplement facts on master

Title: Message Title










 

 William Hopper assigned an issue to William Hopper











 






 Facter /  FACT-618



  Cherry-pick / reimplement facts on master 










Change By:

 William Hopper




Assignee:

 Eric Sorenson William Hopper












   

 Add Comment











 










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




 














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

Jira (FACT-642) Backport lost zpool_version fix into Facter / master

Title: Message Title










 

 William Hopper updated an issue











 






 Facter /  FACT-642



  Backport lost zpool_version fix into Facter / master 










Change By:

 William Hopper




Assignee:

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

Jira (PDB-815) PR (1035): (maint) fix order on environments for facts - wkalt

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (1035): (maint) fix order on environments for facts - wkalt 










Pull request (maint) fix order on environments for facts has been closed.












   

 Add Comment











 













 PuppetDB /  PDB-815



  PR (1035): (maint) fix order on environments for facts - wkalt 







 h2. (maint) fix order on environments for facts   * Author: Wyatt Alt <>  * Company:   * Github ID: [wkalt|https://github.com/wkalt]  * [Pull Request 1035 Discussion|https://github.com/puppetlabs/puppetdb/pull/1035]  * [Pull Request 1035 File Diff|https://github.com/puppetlabs/puppetdb/pull/1035/files]  h2. Pull Request Description   this fixes an iss...















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




 














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

Jira (FACT-619) Inventory orphaned contributions on master

Title: Message Title










 

 William Hopper commented on an issue











 






  Re: Inventory orphaned contributions on master 










As mentioned in this issue's epic, a spreadsheet has been created with inventoried commits. At present, ticketed commits from projects.puppetlabs.com have been inventoried, and there may be more changes that we want that were not ticketed.












   

 Add Comment











 













 Facter /  FACT-619



  Inventory orphaned contributions on master 














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




 














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

Jira (PDB-815) PR (1035): (maint) fix order on environments for facts - wkalt

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (1035): (maint) fix order on environments for facts - wkalt 










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












   

 Add Comment











 













 PuppetDB /  PDB-815



  PR (1035): (maint) fix order on environments for facts - wkalt 







 h2. (maint) fix order on environments for facts   * Author: Wyatt Alt <>  * Company:   * Github ID: [wkalt|https://github.com/wkalt]  * [Pull Request 1035 Discussion|https://github.com/puppetlabs/puppetdb/pull/1035]  * [Pull Request 1035 File Diff|https://github.com/puppetlabs/puppetdb/pull/1035/files]  h2. Pull Request Description   this fixes an iss...















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




 














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

Jira (PDB-815) PR (1035): (maint) fix order on environments for facts - wkalt

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (1035): (maint) fix order on environments for facts - wkalt 










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












   

 Add Comment











 













 PuppetDB /  PDB-815



  PR (1035): (maint) fix order on environments for facts - wkalt 







 h2. (maint) fix order on environments for facts   * Author: Wyatt Alt <>  * Company:   * Github ID: [wkalt|https://github.com/wkalt]  * [Pull Request 1035 Discussion|https://github.com/puppetlabs/puppetdb/pull/1035]  * [Pull Request 1035 File Diff|https://github.com/puppetlabs/puppetdb/pull/1035/files]  h2. Pull Request Description   this fixes an iss...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an 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-815) PR (1035): (maint) fix order on environments for facts - wkalt

2014-08-11 Thread Wyatt Alt (JIRA)

Title: Message Title










 

 Wyatt Alt updated an issue











 






 PuppetDB /  PDB-815



  PR (1035): (maint) fix order on environments for facts - wkalt 










Change By:

 Wyatt Alt




Story Points:

 1












   

 Add Comment











 










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




 














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

Jira (PDB-815) PR (1035): (maint) fix order on environments for facts - wkalt

2014-08-11 Thread Wyatt Alt (JIRA)

Title: Message Title










 

 Wyatt Alt assigned an issue to Wyatt Alt











 






 PuppetDB /  PDB-815



  PR (1035): (maint) fix order on environments for facts - wkalt 










Change By:

 Wyatt Alt




Assignee:

 Wyatt Alt












   

 Add Comment











 










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




 














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

Jira (PDB-815) PR (1035): (maint) fix order on environments for facts - wkalt

2014-08-11 Thread Wyatt Alt (JIRA)

Title: Message Title










 

 Wyatt Alt updated an issue











 






 PuppetDB /  PDB-815



  PR (1035): (maint) fix order on environments for facts - wkalt 










Change By:

 Wyatt Alt




Sprint:

 20140730 to 20140813












   

 Add Comment











 










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




 














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

Jira (PUP-3033) YARDoc/puppet doc Exploration

2014-08-11 Thread Hailee Kenney (JIRA)

Title: Message Title










 

 Hailee Kenney commented on an issue











 






  Re: YARDoc/puppet doc Exploration 










Waiting to see if we get a few more responses to the puppet-dev thread before moving forward with this.












   

 Add Comment











 













 Puppet /  PUP-3033



  YARDoc/puppet doc Exploration 







 Look into the currently existing puppet doc tool and finish up what needs to be done to start development on the current prototype.















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




 














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

Jira (PUP-3041) Expose actual environment path to scope in DSL

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Expose actual environment path to scope in DSL 










I think this sounds like a good idea. I'm not sure if $settings is the right place, however, since it isn't a setting per se.












   

 Add Comment











 













 Puppet /  PUP-3041



  Expose actual environment path to scope in DSL 







 The new directory environment support is slick BUT one big problem is that there is no really good way to discover from within a catalog compile what the base path to the environment you are in is.   It would be great if there was something akin to $settings::my_environment_path exposed into the scope available to the DSL which adjusted to the root of wh...















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




 














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

Jira (PDB-816) Configuration option, to 'allow' structured facts

Title: Message Title










 

 Kenneth Barber created an issue











 






 PuppetDB /  PDB-816



  Configuration option, to 'allow' structured facts 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 11/Aug/14 10:37 AM




Priority:

  Normal




Reporter:

 Kenneth Barber










This ticket expresses not only the change to allow structured facts to flow from the terminus, but also the discussion that has to be had to decide the default and the exact places where this needs to happen.
At the moment, I'm presuming we want an option on the terminus, but now that we've provided backwards compatible structured facts display as JSON it might be enough. The contention is that this does not match the legacy Ruby serialization however, so having the option in the terminus might be useful.
More discussion and thought needed.












   

 Add Comment

Jira (PDB-816) Configuration option, to 'allow' structured facts

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-816



  Configuration option, to 'allow' structured facts 










Change By:

 Kenneth Barber




Fix Version/s:

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

Jira (PDB-816) Configuration option, to 'allow' structured facts

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-816



  Configuration option, to 'allow' structured facts 










Change By:

 Kenneth Barber




Sprint:

 20140813 to 20140827












   

 Add Comment











 










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




 














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

Jira (PUP-3025) resource_type search can produce errors if storedconfigs is not configured.

2014-08-11 Thread Hailee Kenney (JIRA)

Title: Message Title










 

 Hailee Kenney commented on an issue











 






  Re: resource_type search can produce errors if storedconfigs is not configured. 










After merging the fix for PUP-2994 I tried this out again. That warning doesn't seem to appear anymore when running with --parser future.












   

 Add Comment











 













 Puppet /  PUP-3025



  resource_type search can produce errors if storedconfigs is not configured. 







 (NOTE: the following is run against 2.7 (currently next), I have also seen the same warnings in 2.6.x)   If I have a manifest which tries to export resources, then I get the following warning when retrieving the resource_type:   {code}  # cat /tmp/foo.pp class foo ($bar) {    @@notify { 'foo': }  }   [root@mypuppetmaster motd]# puppet resource_type se...















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




 














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

Jira (PUP-744) Pool HTTPS connections

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Pool HTTPS connections 










Notes for Functional Review:
1) Verifying that it speeds things up. Josh has some great notes in https://github.com/puppetlabs/puppet/pull/2863 on how to test this. 2) Andy also suggested trying against multiple masters or separate CA or external CA.












   

 Add Comment











 













 Puppet /  PUP-744



  Pool HTTPS connections 







 Reduce network traffic and latency















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




 














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

Jira (PUP-3043) 100% CPU usage

2014-08-11 Thread redmine.exporter (JIRA)

Title: Message Title

redmine.exporter created an issue

Puppet / PUP-3043

100% CPU usage

Issue Type:

Bug

Assignee:

Unassigned

Created:

11/Aug/14 11:11 AM

Labels:

redmine

Priority:

Normal

Reporter:

redmine.exporter

Hi,
I've been experimenting with Puppet for a few days now, and overall I'm pretty impressed on how easy Puppet makes it to manage configurations. However, one thing has been ruÃ¯ning my enthusiasm thoroughly, and that is the massive CPU consumption of Puppet.
At first I used puppet to source in and manage a few hundred megabytes of data, so I presumed Puppet just wasn't made to provide such large amounts of data. So I set up my own apt repository and created some custom packages to as an alternative way to transfer data.
I also learned about the checksum file property, and that the default value of md5 can cause a lot of CPU consumption. So I turned checksumming of (checksum => undef) .
But now puppet is still happily eating away 100% CPU for tens of minutes at a time, with no apparent things happening. (puppetd -tv --trace --debug, but nothing appearing in the console while Puppet is cooking the CPU.)
I believe the following resource is to blame: file { "/some/data/dir": owner => "$username", group => "$username", recurse => "true", ensure => "directory", checksum => undef }
I just want this resource to make sure that all files in the directory are owned by user and group $username. /some/data/dir contains 300M in 6000+ files. This resource executes swiftly, but after the

Jira (PUP-2526) puppet agent retry failed http requests

Title: Message Title

Andy Parker commented on an issue

Re: puppet agent retry failed http requests

Marc Seeger, Peter Drake, please help us to move this forward. Arguing from what the RFC for HTTP says is only one bit of information needed for this change, but is not the only, nor is the it necessarily the most important. Unfortunately puppet doesn't always adhere to the desired HTTP practices when it communicates (sometimes what should be a GET is performed as a POST). That means that we would really like to know exactly what kinds of problems are being encountered. I believe that you have already seen several cases of this occurring and determined that retries would help, but the rest of us need to know and understand what these cases are. I have requested is for you to provide some examples (logs of the failure would be ideal) of the kinds of failures that you are trying to resolve with this change. I'd really like to fix this, but I need to know what exactly is going to be fixed.
To Felix Frank's point, this behavior has to be opt in because the puppet HTTP client code is reused in many different contexts. Some of those contexts are particular network setups used for master/agent communication, others are third party plugins that use the client code to communicate with completely different systems where the assumptions about the idempotency of GET/HEAD and retries cannot be made.

Add Comment

Puppet / PUP-2526

puppet agent retry failed http requests

It would be nice if puppet agent had the ability had the ability to retry failed http requests to the puppet master. I have multiple puppet masters sitting behind a load balancer in AWS (ELB). Whenever we update a puppet master, the node is removed from the load balancer while the update occurs. Unfortunately the AWS ELB does not allow quiescent remova...

Jira (PDB-797) Add 'name' field to 'fact-nodes'

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-797



  Add 'name' field to 'fact-nodes' 










Change By:

 Kenneth Barber




Summary:

 Add ' fact name ' field to 'fact-nodes'












   

 Add Comment











 










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




 














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

Jira (PDB-816) Configuration option, to 'allow' structured facts

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-816



  Configuration option, to 'allow' structured facts 










Change By:

 Kenneth Barber




Sprint:

 20140813 20140730  to  20140827  20140813












   

 Add Comment











 










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




 














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

Jira (PDB-816) Configuration option, to 'allow' structured facts

Title: Message Title










 

 Kenneth Barber assigned an issue to Kenneth Barber











 






 PuppetDB /  PDB-816



  Configuration option, to 'allow' structured facts 










Change By:

 Kenneth Barber




Assignee:

 Kenneth Barber












   

 Add Comment











 










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




 














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

Jira (PUP-2526) puppet agent retry failed http requests

2014-08-11 Thread Marc Seeger (JIRA)

Title: Message Title

Marc Seeger commented on an issue

Re: puppet agent retry failed http requests

Any networking problem during a puppet run (dropped packets, routing issues, DNS issues, ...) can lead to failures like these:

web-7638: 2014-01-10T11:24:12+00:00 daemon.err web- puppet-agent[28071]: (/Stage[main]/Apt/File[sources.list]) Could not evaluate: Connection timed out - connect(2) Could not retrieve file metadata for puppet:///modules//.../eu-west-1.sources.list-lucid: Connection timed out - connect(2)

Since puppet doesn't currently retry these failures, the rest of the run will error out with a "failed dependency". Especially when pushing out a combination of "new binary and new config file", this can get annoying.
Among lots of other events, this could for example happen whenever Amazon does something like this:

10:22 AM PDT We are investigating network connectivity issues for some instances in the US-EAST-1 Region. 11:09 AM PDT Between 10:03 AM and 10:18 AM PDT we experienced connectivity issues for some instances in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.

Add Comment

Puppet / PUP-2526

puppet agent retry failed http requests

Jira (PUP-3001) Reintroduce dynamic scoping for resource defaults

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Reintroduce dynamic scoping for resource defaults 










change reverted, 4x now uses the same default lookup as 3x.












   

 Add Comment











 













 Puppet /  PUP-3001



  Reintroduce dynamic scoping for resource defaults 







 After lengthy [discussion|https://groups.google.com/forum/#!msg/puppet-dev/7sgPBwxOhfE/jarWejgOgUwJ] and [evaluation|https://groups.google.com/forum/#!msg/puppet-dev/aYfA1lTWgW0/dIze_695XGAJ], the [decision was made|https://groups.google.com/d/msg/puppet-dev/8B-CUBqI_Hk/0W6hUas9_VwJ] that the change to scoping of resource defaults in PUP-867 is not a good...















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




 














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

Jira (PUP-2971) install_options are not passed to yum when listing packages

Title: Message Title










 

 Michael Smith assigned an issue to Michael Smith











 






 Puppet /  PUP-2971



  install_options are not passed to yum when listing packages 










Change By:

 Michael Smith




Assignee:

 Michael Smith












   

 Add Comment











 










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




 














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

Jira (PUP-2817) Solaris Zone properties ip, dataset and inherit are not set upon zone creation

2014-08-11 Thread Rahul Gopinath (JIRA)

Title: Message Title










 

 Rahul Gopinath commented on an issue











 






  Re: Solaris Zone properties ip, dataset and inherit are not set upon zone creation 










I seem to be able to run the init.pp from ENTERPRISE 273 ticket


class monitise_zone {
  zone { 'myzone1':
ensure => 'running',
path => '/zones/myzone1',
ip => 'ixgbe0:172.16.12.68:172.16.13.254',
create_args => "\nadd net\nset address=172.16.12.6\nset physical=ixgbe0\nend",
#create_args => "add net set address=172.16.12.6 set physical=ixgbe0",
iptype => 'shared',
  }
}
include monitise_zone



resulting in


# zonecfg -z myzone1 info
zonename: myzone1
zonepath: /zones/myzone1
brand: native
autoboot: true
bootargs: 
pool: 
limitpriv: 
scheduling-class: 
ip-type: shared
hostid: 
net:
address: 172.16.12.6
physical: ixgbe0
defrouter not specified



what should I see here instead?












   

 Add Comment











 













 Puppet /  PUP-2817



  Solaris Zone properties ip, dataset and inherit are not set upon zone creation 







 The {{ip}}, {{dataset}} and {{inherit}} properties of the Zone type each have [insync methods|https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/type/zone.rb#L252-L253] that respond with {{true}} when passed a {{nil}} property value. When a zone resource is first created, the property hash looks like:   {code}  {    ensure => :absent  }  {code}  ...

Jira (PUP-2971) install_options are not passed to yum when listing packages

Title: Message Title










 

 Michael Smith commented on an issue











 






  Re: install_options are not passed to yum when listing packages 










Issue reported in comments to 

PUP-1060
.












   

 Add Comment











 













 Puppet /  PUP-2971



  install_options are not passed to yum when listing packages 







 According to reports in PUP-1060, the enablerepo and disablerepo options are no longer working. At least one of the reports points out that the {{install_options}} is not longer passed to the yum command that lists packages. This results in packages not being found in enabled repos.  















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




 














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

Jira (PUP-3037) Pluginsync notices on Windows reports file paths with forward slashes

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Pluginsync notices on Windows reports file paths with forward slashes 










This might be nice with windows, but carries a fine line for fixes. The implementation should only convert these for the message it's reporting on (not the actual resource's path) and I'm really not sure if it should convert the File resource name.












   

 Add Comment











 













 Puppet /  PUP-3037



  Pluginsync notices on Windows reports file paths with forward slashes 







 Pluginsync/loading facts notices on Windows output file paths with forward slashes:   {quote}  Notice: /File[C:/ProgramData/PuppetLabs/puppet/var/lib/puppet/provider/rabbitmq_ vhost]/ensure: removed  Info: Loading facts in C:/ProgramData/PuppetLabs/puppet/var/lib/facter/concat_basedir.rb  {quote}  This is clearly a lie. When I copy those paths and try t...















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




 














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

Jira (PDB-813) Port certificate whitelist handling from PuppetDB into trapperkeeper-webserver-jetty9

2014-08-11 Thread Ryan Senior (JIRA)

Title: Message Title










 

 Ryan Senior assigned an issue to Ryan Senior











 






 PuppetDB /  PDB-813



  Port certificate whitelist handling from PuppetDB into trapperkeeper-webserver-jetty9 










Change By:

 Ryan Senior




Assignee:

 Ryan Senior












   

 Add Comment











 










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




 














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

Jira (PDB-813) Port certificate whitelist handling from PuppetDB into trapperkeeper-webserver-jetty9

2014-08-11 Thread Ryan Senior (JIRA)

Title: Message Title










 

 Ryan Senior updated an issue











 






 PuppetDB /  PDB-813



  Port certificate whitelist handling from PuppetDB into trapperkeeper-webserver-jetty9 










Change By:

 Ryan Senior




Sprint:

 20140827 20140813  to  20140910  20140827












   

 Add Comment











 










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




 














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

Jira (PDB-813) Port certificate whitelist handling from PuppetDB into trapperkeeper-webserver-jetty9

2014-08-11 Thread Ryan Senior (JIRA)

Title: Message Title










 

 Ryan Senior updated an issue











 






 PuppetDB /  PDB-813



  Port certificate whitelist handling from PuppetDB into trapperkeeper-webserver-jetty9 










Change By:

 Ryan Senior




Sprint:

 20140813 20140730  to  20140827  20140813












   

 Add Comment











 










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




 














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

Jira (PUP-1280) Windows agent daemon script always captures runinterval as nil

Title: Message Title










 

 Nicholas Fagerlund updated an issue











 






 Puppet /  PUP-1280



  Windows agent daemon script always captures runinterval as nil 










Change By:

 Nicholas Fagerlund




Summary:

 windows agents don't parse Windows agent daemon script always captures  runinterval as  a duration setting  nil












   

 Add Comment











 










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




 














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

Jira (PUP-1280) Windows agent daemon script always captures runinterval as empty string

Title: Message Title










 

 Nicholas Fagerlund updated an issue











 






 Puppet /  PUP-1280



  Windows agent daemon script always captures runinterval as empty string 










Change By:

 Nicholas Fagerlund




Summary:

 Windows agent daemon script always captures runinterval as  nil  empty string












   

 Add Comment











 










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




 














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

Jira (PUP-1280) Windows agent daemon script always captures runinterval as nil

Title: Message Title










 

 Nicholas Fagerlund updated an issue











 






 Puppet /  PUP-1280



  Windows agent daemon script always captures runinterval as nil 










Change By:

 Nicholas Fagerlund









 When running as a service, puppet on windows runs `puppet agent --configprint runinterval` and assumes the result is in seconds. It then runs `puppet agent --onetime` every runinterval seconds.In 3.0.0, runinterval was changed to a `duration` setting, so it can be of the form 5m, 2h, etc . This was done in commit [2cb9b503](https://github.com/puppetlabs/puppet/commit/2cb9b503c427c75b45ba47a0ea538ae95342bee2) *Update, with Puppet 3.6:* {{--configprint runinterval}} will always return the value in seconds, even if it was set with something like {{2h}}. The real problem is that the following line in daemon.rb:{code}runinterval = %x{ "#{puppet}" agent --configprint runinterval }{code}...will always set runinterval to nil 












   

 Add Comment











 










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




 














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

Jira (PUP-1280) Windows agent daemon script always captures runinterval as empty string

Title: Message Title










 

 Nicholas Fagerlund updated an issue











 






 Puppet /  PUP-1280



  Windows agent daemon script always captures runinterval as empty string 










Change By:

 Nicholas Fagerlund









 When running as a service, puppet on windows runs `puppet agent --configprint runinterval` and assumes the result is in seconds. It then runs `puppet agent --onetime` every runinterval seconds.In 3.0.0, runinterval was changed to a `duration` setting, so it can be of the form 5m, 2h, etc . This was done in commit [2cb9b503](https://github.com/puppetlabs/puppet/commit/2cb9b503c427c75b45ba47a0ea538ae95342bee2)*Update, with Puppet 3.6:* {{--configprint runinterval}} will always return the value in seconds, even if it was set with something like {{2h}}. The real problem is that the following line in daemon.rb:{code}runinterval = %x{ "#{puppet}" agent --configprint runinterval }{code}...will always set runinterval to  nil  the empty string. I've tried replacing the contents of the command and doing some debug messages, but for some reason it's impossible to capture the proper output of a command at this point in the daemon script.  












   

 Add Comment











 










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




 














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

Jira (PUP-1280) Windows agent daemon script always captures runinterval as empty string

Title: Message Title










 

 Nicholas Fagerlund commented on an issue











 






  Re: Windows agent daemon script always captures runinterval as empty string 










Updated the summary and description with the problem as I've observed it. I'm at the limit of what I can do, so I'll just document that runinterval is 100% broken for now. 












   

 Add Comment











 













 Puppet /  PUP-1280



  Windows agent daemon script always captures runinterval as empty string 







 When running as a service, puppet on windows runs `puppet agent --configprint runinterval` and assumes the result is in seconds. It then runs `puppet agent --onetime` every runinterval seconds.   In 3.0.0, runinterval was changed to a `duration` setting, so it can be of the form 5m, 2h, etc

Jira (PUP-2349) Deprecate non-string modes on file type

Title: Message Title










 

 Kylo Ginsberg assigned an issue to Kylo Ginsberg











 






 Puppet /  PUP-2349



  Deprecate non-string modes on file type 










Change By:

 Kylo Ginsberg




Assignee:

 Kylo Ginsberg












   

 Add Comment











 










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




 














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

Jira (PUP-2898) Long form Resource Type reference fools "future parser" this is an override

Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-2898



  Long form Resource Type reference fools "future parser" this is an override 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall












   

 Add Comment











 










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




 














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

Jira (PDB-817) PR (1038): (maint) Fix old acceptance test refspec issue - kbarber

Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-817



  PR (1038): (maint) Fix old acceptance test refspec issue - kbarber 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 11/Aug/14 1:31 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










(maint) Fix old acceptance test refspec issue


Author: Ken Barber 


Company: Puppet Labs Inc.


Github ID: kbarber


Pull Request 1038 Discussion


Pull Request 1038 File Diff


Pull Request Description

The old refspec for acceptance testing source code only really worked for the PR testing workflow. This patch makes it work for the command line or polling based workflow as well.
Without it, it makes it hard to run beaker acceptance tests from the command line.
S

Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

Title: Message Title










 

 Rob Reynolds commented on an issue











 






  Re: Spurious 'trigger changed' messages generated by scheduled task provider 










It appears the day_of_week versus on and start_date are what might be triggering this.












   

 Add Comment











 













 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 







 The Windows scheduled task (scheduled_task) provider will generate spurious messages during Puppet runs which suggest that scheduled task resources are being reapplied during each run even when the task is present and its associated resource has not been modified. The messages in question look like the following:   {noformat}notice: /Stage[main]/Schedtas...















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




 














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

Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Rob Reynolds




Component/s:

 Client












   

 Add Comment











 










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




 














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

Jira (PUP-1291) scheduled_task : add support for "every X minutes or hours" mode

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-1291



  scheduled_task : add support for "every X minutes or hours" mode 










Change By:

 Rob Reynolds




Component/s:

 Client












   

 Add Comment











 










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




 














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

Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Rob Reynolds









 The Windows scheduled task  (scheduled_task)  provider will generate spurious messages during Puppet runs which suggest that scheduled task resources are being reapplied during each run even when the task is present and its associated resource has not been modified. The messages in question look like the following:{noformat}notice: /Stage[main]/Schedtask/Scheduled_task[restart_some_service]/trigger: trigger changed '{'every' => '1', 'on' => ['sun'], 'schedule' => 'weekly', 'start_date' => '2012-10-22', 'start_time' => '01:00'}' to '[{'day_of_week' => ['sun'], 'schedule' => 'weekly', 'start_time' => '01:00'}]'{noformat}The resource associated with the task looks like this:{noformat}  scheduled_task { 'restart_some_service':ensure  => present,enabled => true,command => 'c:\windows\restart_some_service.bat',user=> 'SYSTEM',trigger => {  schedule=> weekly,  day_of_week => [sun],  start_time  => '01:00',},require => File['restart_some_service.bat'],  }{noformat}This seems to be some kind of artifact of date conversion/formatting or something. While Puppet reports a change, examining the history tab for the task shows no changes aside from the initial creation of the task and subsequent 'real' changes which were initiated by actually modifying the resource. The notices will be generated regardless of whether there is a real change to report. 












   

 Add Comment











 










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




 














-- 
You received this message because you are subscrib

Jira (PUP-2971) install_options are not passed to yum when listing packages

Title: Message Title










 

 Michael Smith commented on an issue











 






  Re: install_options are not passed to yum when listing packages 










Functional Review
I tested on the latest docker image of CentOS 7, running Puppet following the running from source instructions.
Verified the problem with sample code from Sylvain Mougenot's comments on 

PUP-1060
, using SHA 789e00b.



bash-4.2# bundle exec puppet apply pkg/enablerepo.pp
Notice: Compiled catalog for b7167568faf0 in environment production in 0.34 seconds
Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false.
   (at /src/puppet/lib/puppet/type/package.rb:430:in `block (3 levels) in ')
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list nginx' returned 1: Error: No matching Packages to list
Error: /Stage[main]/Main/Package[nginx]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y list nginx' returned 1: Error: No matching Packages to list
Notice: Finished catalog run in 0.55 seconds



Used same examples to verify fix using SHA c6ba27e.



bash-4.2# bundle exec puppet apply pkg/enablerepo.pp Notice: Compiled catalog for b7167568faf0 in environment production in 0.36 seconds
Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false.
   (at /src/puppet/lib/puppet/type/package.rb:430:in `block (3 levels) in ')
Notice: /Stage[main]/Main/Package[nginx]/ensure: created
Notice: Finished catalog run in 2.25 seconds



Tried several bad options for install_options to see that error messages looked ok, and they did.












   

 Add Comment

Jira (PUP-3044) Expand Puppet File Permissions

2014-08-11 Thread Lindsey Smith PO (JIRA)

Title: Message Title










 

 Lindsey Smith PO created an issue











 






 Puppet /  PUP-3044



  Expand Puppet File Permissions 










Issue Type:

  Improvement




Assignee:


 Unassigned




Created:


 11/Aug/14 1:50 PM




Labels:


 support




Priority:

  Normal




Reporter:

 Lindsey Smith PO










Please consider expanding puppet file permissions beyond posix, specifically, linux-based setfacl extended users and groups, as well as permission inheritance. 












   

 Add Comment











 










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

Jira (PUP-2971) install_options are not passed to yum when listing packages

Title: Message Title










 

 Michael Smith assigned an issue to Unassigned











 






 Puppet /  PUP-2971



  install_options are not passed to yum when listing packages 










Change By:

 Michael Smith




Assignee:

 Michael Smith












   

 Add Comment











 










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




 














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

Jira (PUP-2898) Long form Resource Type reference fools "future parser" this is an override

Title: Message Title










 

 Kurt Wall updated an issue











 






 Puppet /  PUP-2898



  Long form Resource Type reference fools "future parser" this is an override 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall












   

 Add Comment











 










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




 














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

Jira (PUP-2898) Long form Resource Type reference fools "future parser" this is an override

Title: Message Title










 

 Kurt Wall commented on an issue











 






  Re: Long form Resource Type reference fools "future parser" this is an override 










Verified in master at SHA=cd3a89e286705a735be659e30b919d5b6fe17900. The regression that Joshua Partlow and Hailee Kenney found is no longer present:



# x.pp
file {
  "/tmp/foo":;
  "/tmp/foo/bar":;
}

$ be puppet apply --parser future x.pp
Notice: Compiled catalog for breve.corp.puppetlabs.net in environment production in 0.42 seconds
Notice: Finished catalog run in 0.03 seconds



Nor do long form resource type references confuse future parser:



# y.pp
File { checksum => 'sha256', content => "8675309\n", }
#Resource[File] { checksum => 'sha256', content => "8675309\n", }
#Resource['file'] { checksum => 'sha256', content => "8675309\n", }

file { '/tmp/jenny':
  ensure => present,
  checksum => md5,
}

file { '/tmp/your-number':
  ensure => present,
}

$ be puppet apply y.pp --parser future
Notice: Compiled catalog for breve.corp.puppetlabs.net in environment production in 0.40 seconds
Notice: /Stage[main]/Main/File[/tmp/jenny]/ensure: created
Notice: /Stage[main]/Main/File[/tmp/your-number]/ensure: created
Notice: Finished catalog run in 0.04 seconds
$ cat  /tmp/your-number
8675309 
$ cat /tmp/jenny 
8675309



Uncommenting the first Resource statement (and hashing out the File statement:



$ be puppet apply y.pp --parser future --verbose 
Notice: Compiled catalog for breve.corp.puppetlabs.net in environment production in 0.41 seconds
Info: Applying configuration version '1407790416'
Notice: /Stage[main]/Main/File[/tmp/jenny]/ensure: created
Notice: /Stage[main]/Main/File[/tmp/your-number]/ensure: created
Notice: Finished catalog run in 0.04 seconds
$ cat /tmp/jenny 
8675309
$ cat /tmp/your-number 
8675309



Uncommenting the second Resource statement and hashing out the first:



$ be puppet apply y.pp --parser future --verbose 
Notice: Compiled catalog for breve.corp.puppetlabs.net in environment production in 0.40 seconds
Info: Applying configuration version '1407790551'
Notice: /Stage[main]/Main/File[/tmp/jenny]/ensure: created
Notice: /Stage[main]/Main/File[/tmp/your-number]/ensure: created
Notice: Finished catalog run in 0.04 seconds
$ cat /tmp/jenny /tmp/your-number 
8675309
$ cat /tmp/your-number 
8675309



Changing the default file content to force Puppet to refresh them. You can see that /tmp/jenny is checksummed with the overridden value, md5, whereas /tmp/your-number is checksummed using sha256. This works for all the resource declarations.



# z.pp
#File { checksum => 'sha256', content => "nunya\n", }
#Resource[File] { checksum => 'sha256', content => "nunya\n" }
Resourc

Jira (PUP-2879) `puppet resource service` not working for `cryptdisks-udev`

Title: Message Title










 

 Eric Thompson assigned an issue to Eric Thompson











 






 Puppet /  PUP-2879



  `puppet resource service` not working for `cryptdisks-udev` 










Change By:

 Eric Thompson




Assignee:

 Eric Thompson












   

 Add Comment











 










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




 














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

Jira (PUP-2728) zypper should always be the default package provider for Suse osfamily

2014-08-11 Thread Joshua Partlow (JIRA)

Title: Message Title










 

 Joshua Partlow assigned an issue to Joshua Partlow











 






 Puppet /  PUP-2728



  zypper should always be the default package provider for Suse osfamily 










Change By:

 Joshua Partlow




Assignee:

 Joshua Partlow












   

 Add Comment











 










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




 














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

Jira (FACT-632) weighted fact not resolved correctly

2014-08-11 Thread Ben Roberts (JIRA)

Title: Message Title










 

 Ben Roberts commented on an issue











 






  Re: weighted fact not resolved correctly 










Looks like this might have been user error on my part. Adding the following line of code to the top of the fact results in the desired behavior.
+require 'facter/util/operatingsystem'


facter -p operatingsystem Sabayon


facter -p | grep operatingsystem operatingsystem => Sabayon














   

 Add Comment











 













 Facter /  FACT-632



  weighted fact not resolved correctly 







 While trying to override the operatingsystem fact for a gentoo derivative (using the Cumulus Linux example from the facter source code as a template) I've run into an issue where the fact resolves correctly in some situations, but not others.   h2. Weighted fact  {code:title=modules/sabayon/lib/facter/operatingsystem.rb}   Facter.add(:operatingsystem) do...















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

Jira (PUP-1280) Windows agent daemon script always captures runinterval as empty string

Title: Message Title










 

 Nicholas Fagerlund commented on an issue











 






  Re: Windows agent daemon script always captures runinterval as empty string 










Once this bug is fixed, docs will need to reverse the changes in commit 87b7f44 for the fixed version of Puppet.












   

 Add Comment











 













 Puppet /  PUP-1280



  Windows agent daemon script always captures runinterval as empty string 







 When running as a service, puppet on windows runs `puppet agent --configprint runinterval` and assumes the result is in seconds. It then runs `puppet agent --onetime` every runinterval seconds.   In 3.0.0, runinterval was changed to a `duration` setting, so it can be of the form 5m, 2h, etc

Jira (PUP-2972) Implementation of +=/-= is potentially confusing

Title: Message Title










 

 Andy Parker updated an issue











 






 Puppet /  PUP-2972



  Implementation of +=/-= is potentially confusing 










Change By:

 Andy Parker




Component/s:

 DOCS












   

 Add Comment











 










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




 














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

Jira (PUP-1044) FileBucket should not keep files in memory

Title: Message Title










 

 Andy Parker assigned an issue to Henrik Lindberg











 






 Puppet /  PUP-1044



  FileBucket should not keep files in memory 










Change By:

 Andy Parker




Assignee:

 Henrik Lindberg












   

 Add Comment











 










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




 














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

Jira (PUP-2972) Implementation of +=/-= is potentially confusing

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Implementation of +=/-= is potentially confusing 










SPEC PR-16 merged (was mislabeled PR-26).












   

 Add Comment











 













 Puppet /  PUP-2972



  Implementation of +=/-= is potentially confusing 







 It seems to me that += and -= are more confusing than useful, and I would argue that they simply shouldn't exist.   Right now (with "--parser future"), these operators implicitly create a new variable that may shadow one from an outer scope, appending/removing the RHS to the outer scope variable if it exists. If the variable has already been defined in t...















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




 














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

Jira (PDB-817) PR (1038): (maint) Fix old acceptance test refspec issue - kbarber

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (1038): (maint) Fix old acceptance test refspec issue - kbarber 










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












   

 Add Comment











 













 PuppetDB /  PDB-817



  PR (1038): (maint) Fix old acceptance test refspec issue - kbarber 







 h2. (maint) Fix old acceptance test refspec issue   * Author: Ken Barber   * Company: Puppet Labs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 1038 Discussion|https://github.com/puppetlabs/puppetdb/pull/1038]  * [Pull Request 1038 File Diff|https://github.com/puppetlabs/puppetdb/pull/1038/files]  h2. Pull Request De...















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




 














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

Jira (PUP-3001) Reintroduce dynamic scoping for resource defaults

Title: Message Title










 

 Andy Parker assigned an issue to Andy Parker











 






 Puppet /  PUP-3001



  Reintroduce dynamic scoping for resource defaults 










Change By:

 Andy Parker




Assignee:

 Andy Parker












   

 Add Comment











 










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




 














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

Jira (PUP-2972) Implementation of +=/-= is potentially confusing

Title: Message Title










 

 Andy Parker assigned an issue to Henrik Lindberg











 






 Puppet /  PUP-2972



  Implementation of +=/-= is potentially confusing 










Change By:

 Andy Parker




Assignee:

 Henrik Lindberg












   

 Add Comment











 










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




 














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

Jira (FACT-619) Inventory orphaned contributions on master

Title: Message Title










 

 William Hopper commented on an issue











 






  Re: Inventory orphaned contributions on master 










I've now gone through the git log itself and found quite a few other orphaned commits, which are now documented in the spreadsheet.












   

 Add Comment











 













 Facter /  FACT-619



  Inventory orphaned contributions on master 














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




 














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

Jira (PUP-2972) Implementation of +=/-= is potentially confusing

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Implementation of +=/-= is potentially confusing 










Merged into master in 327e28












   

 Add Comment











 













 Puppet /  PUP-2972



  Implementation of +=/-= is potentially confusing 







 It seems to me that += and -= are more confusing than useful, and I would argue that they simply shouldn't exist.   Right now (with "--parser future"), these operators implicitly create a new variable that may shadow one from an outer scope, appending/removing the RHS to the outer scope variable if it exists. If the variable has already been defined in t...















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




 














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

Jira (PUP-3001) Reintroduce dynamic scoping for resource defaults

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Reintroduce dynamic scoping for resource defaults 










Merged into master in 327e28












   

 Add Comment











 













 Puppet /  PUP-3001



  Reintroduce dynamic scoping for resource defaults 







 After lengthy [discussion|https://groups.google.com/forum/#!msg/puppet-dev/7sgPBwxOhfE/jarWejgOgUwJ] and [evaluation|https://groups.google.com/forum/#!msg/puppet-dev/aYfA1lTWgW0/dIze_695XGAJ], the [decision was made|https://groups.google.com/d/msg/puppet-dev/8B-CUBqI_Hk/0W6hUas9_VwJ] that the change to scoping of resource defaults in PUP-867 is not a good...















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




 














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

Jira (PUP-3001) Reintroduce dynamic scoping for resource defaults

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Reintroduce dynamic scoping for resource defaults 










Have not looked at what the spec says - any need to change it?












   

 Add Comment











 













 Puppet /  PUP-3001



  Reintroduce dynamic scoping for resource defaults 







 After lengthy [discussion|https://groups.google.com/forum/#!msg/puppet-dev/7sgPBwxOhfE/jarWejgOgUwJ] and [evaluation|https://groups.google.com/forum/#!msg/puppet-dev/aYfA1lTWgW0/dIze_695XGAJ], the [decision was made|https://groups.google.com/d/msg/puppet-dev/8B-CUBqI_Hk/0W6hUas9_VwJ] that the change to scoping of resource defaults in PUP-867 is not a good...















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




 














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

Jira (PUP-3001) Reintroduce dynamic scoping for resource defaults

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Reintroduce dynamic scoping for resource defaults 










That completely slipped my mind. The specification currently just says "TODO: SCOPING RULES." It needs to be filled in since these rules will be with us for the duration of the 4.x version of the language.












   

 Add Comment











 













 Puppet /  PUP-3001



  Reintroduce dynamic scoping for resource defaults 







 After lengthy [discussion|https://groups.google.com/forum/#!msg/puppet-dev/7sgPBwxOhfE/jarWejgOgUwJ] and [evaluation|https://groups.google.com/forum/#!msg/puppet-dev/aYfA1lTWgW0/dIze_695XGAJ], the [decision was made|https://groups.google.com/d/msg/puppet-dev/8B-CUBqI_Hk/0W6hUas9_VwJ] that the change to scoping of resource defaults in PUP-867 is not a good...















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




 














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

Jira (PUP-3001) Reintroduce dynamic scoping for resource defaults

Title: Message Title










 

 Andy Parker assigned an issue to Henrik Lindberg











 






 Puppet /  PUP-3001



  Reintroduce dynamic scoping for resource defaults 










Change By:

 Andy Parker




Assignee:

 Henrik Lindberg












   

 Add Comment











 










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




 














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

Jira (PUP-2972) Implementation of +=/-= is potentially confusing

Title: Message Title










 

 Andy Parker assigned an issue to Andy Parker











 






 Puppet /  PUP-2972



  Implementation of +=/-= is potentially confusing 










Change By:

 Andy Parker




Assignee:

 Henrik Lindberg Andy Parker












   

 Add Comment











 










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




 














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

Jira (PUP-2879) `puppet resource service` not working for `cryptdisks-udev`

Title: Message Title










 

 Eric Thompson commented on an issue











 






  Re: `puppet resource service` not working for `cryptdisks-udev` 










so, should this be pulled through? i can't reproduce right now as statd-mounting has same problem with parameter "MOUNTPOINT" : $> initctl status statd-mounting initctl: Unknown parameter: MOUNTPOINT (ubuntu 14.04 on SHA 327e28d)












   

 Add Comment











 













 Puppet /  PUP-2879



  `puppet resource service` not working for `cryptdisks-udev` 







 Issuing _puppet resource service cryptdisks-udev_ outputs  bq. Error: Could not run: Execution of '/sbin/status cryptdisks-udev' returned 1: status: Unknown parameter: DEVNAME   Since puppet stops there _puppet resource service_ won't work as well.















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




 














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

Jira (PUP-2879) `puppet resource service` not working for `cryptdisks-udev`

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: `puppet resource service` not working for `cryptdisks-udev` 










Eric Thompson this fix is completely specific to the cryptdisks-udev service. The more general problem will be addressed in PUP-3040.
But how did you end up with statd-mounting? I.e. did you specifically install something on top of a base Ubuntu 14.04 image? If that's going to be common we could add that to the (ever growing) blacklist.












   

 Add Comment











 













 Puppet /  PUP-2879



  `puppet resource service` not working for `cryptdisks-udev` 







 Issuing _puppet resource service cryptdisks-udev_ outputs  bq. Error: Could not run: Execution of '/sbin/status cryptdisks-udev' returned 1: status: Unknown parameter: DEVNAME   Since puppet stops there _puppet resource service_ won't work as well.















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




 














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

Jira (PUP-2879) `puppet resource service` not working for `cryptdisks-udev`

Title: Message Title










 

 Eric Thompson commented on an issue











 






  Re: `puppet resource service` not working for `cryptdisks-udev` 










Kylo Ginsberg see my edits in above comment. it's the "ubuntu-14.04-64-nocm" box from vagrant cloud. so ostensibly it's a clean install












   

 Add Comment











 













 Puppet /  PUP-2879



  `puppet resource service` not working for `cryptdisks-udev` 







 Issuing _puppet resource service cryptdisks-udev_ outputs  bq. Error: Could not run: Execution of '/sbin/status cryptdisks-udev' returned 1: status: Unknown parameter: DEVNAME   Since puppet stops there _puppet resource service_ won't work as well.















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




 














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

Jira (PDB-818) Add select-reports subquery

Title: Message Title










 

 Erik Dalén created an issue











 






 PuppetDB /  PDB-818



  Add select-reports subquery 










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 11/Aug/14 4:35 PM




Priority:

  Normal




Reporter:

 Erik Dalén










There should be a select-reports subquery to be able to find nodes with failing runs etc.












   

 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 Goo

Jira (PDB-819) Add select-events subquery operator

Title: Message Title










 

 Erik Dalén created an issue











 






 PuppetDB /  PDB-819



  Add select-events subquery operator 










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 11/Aug/14 4:36 PM




Priority:

  Normal




Reporter:

 Erik Dalén










The select-events query should also be supported for more flexibility in queries.












   

 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 Goo

Jira (PUP-2879) `puppet resource service` not working for `cryptdisks-udev`

Title: Message Title










 

 Eric Thompson updated an issue











 






 Puppet /  PUP-2879



  `puppet resource service` not working for `cryptdisks-udev` 










Change By:

 Eric Thompson




Assignee:

 Eric Thompson












   

 Add Comment











 










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




 














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

Jira (PUP-2745) Puppet 3.6.1 issue with Forge API v3

2014-08-11 Thread Anderson Mills (JIRA)

Title: Message Title










 

 Anderson Mills assigned an issue to Anderson Mills











 






 Puppet /  PUP-2745



  Puppet 3.6.1 issue with Forge API v3 










Change By:

 Anderson Mills




Assignee:

 Anderson Mills












   

 Add Comment











 










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




 














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

Jira (PUP-2914) Update packages to use RGen 0.7.0

2014-08-11 Thread Melissa Stone (JIRA)

Title: Message Title










 

 Melissa Stone commented on an issue











 






  Re: Update packages to use RGen 0.7.0 










If we update to 0.6.6, will that also cause problems for older versions of puppet? We're having trouble figuring out the best way to proceed with this dependency update. There isn't a good way to update the rgen packaging to prevent it from being installed along side earlier versions of puppet. We could vendor rgen, but that has it's own excitement. 
Matthaus Owens, Michael Stahnke, Moses Mendoza I know you were also involved in the conversation. We should probably figure out a path forward soon, seeing as 3.7 is targeted for release at the end of this month.












   

 Add Comment











 













 Puppet /  PUP-2914



  Update packages to use RGen 0.7.0 







 PUP-2831 updated puppet to work with rgen 0.7.0. Before those fixes it made some mistakes that caused 0.7.0 to create issues, which might cause a problem for old packages of puppet that simply rely on {{>= 0.6.5}}.   We need to update the various packages that we make to depend on 0.7.0 and publish an RGen 0.7.0 package.















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




 














-- 
You received this

Jira (PUP-511) Specify Resource Expression Evaluation