Jira (PUP-2317) Future parser does not honor dynamic environments with modulepath in Puppet 3.5.1

[William Van Hevelingen (JIRA)]

Title: Message Title










 

 William Van Hevelingen created an issue











 






 Puppet /  PUP-2317



  Future parser does not honor dynamic environments with modulepath in Puppet 3.5.1 










Issue Type:

  Bug




Affects Versions:


 3.5.1




Assignee:


 Unassigned




Created:


 22/Apr/14 12:10 AM




Priority:

  Normal




Reporter:

 William Van Hevelingen










Puppet 3.5.1 with Future parser enabled does not honor modulepath or manifest config with $environment. It works as expected when disabling future parser.












   

 Add Comment











 










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

Jira (PUP-2317) Future parser does not honor dynamic environments with modulepath in Puppet 3.5.1

[Daniele Sluijters (JIRA)]

Title: Message Title










 

 Daniele Sluijters updated an issue











 






 Puppet /  PUP-2317



  Future parser does not honor dynamic environments with modulepath in Puppet 3.5.1 










Change By:

 Daniele Sluijters




Priority:

 Normal Critical












   

 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-567) Export with reports fails with java.io.IOException: This archives contains unclosed entries

[JIRA]

Title: Message Title










 

 Thomas Weißschuh commented on an issue











 






  Re: Export with reports fails with java.io.IOException: This archives contains unclosed entries 










Thanks! However I want to note again, that several other hosts with the exact same configuration-version (with a slash) export totally fine.
Would it be possible to get a the update of commons-compress in a 1.6.x release, as this fixes the issue for us and would not break compatibility?












   

 Add Comment











 













 PuppetDB /  PDB-567



  Export with reports fails with java.io.IOException: This archives contains unclosed entries 







 Doing {{puppetdb export}} always fails at the first report of a certain host with the following stacktrace. Reports of other nodes being performed this certain node run fine.   {code}  Writing report '2014-04-03T08:44:43.158Z-heads/production-0-g6e18d80' for node ''  java.io.IOException: This archives contains unclosed entries.   at o...















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




 














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

Jira (PUP-2271) yumrepo attributes cannot be set to '_none_'

[David Sastre Medina (JIRA)]

Title: Message Title










 

 David Sastre Medina commented on an issue











 






  Re: yumrepo attributes cannot be set to '_none_' 










A simplistic fix that works for me is:
— /usr/lib/ruby/site_ruby/1.8/puppet/type/yumrepo.rb.orig 2014-04-22 12:09:22.361808360 +0200 +++ /usr/lib/ruby/site_ruby/1.8/puppet/type/yumrepo.rb 2014-04-22 12:08:09.982180121 +0200 @@ -229,6 +229,7 @@ newvalues(/.*/, :absent) validate do |value| next if value.to_s == 'absent' + next if value.to_s == 'none' parsed = URI.parse(value)
 unless VALID_SCHEMES.include?(parsed.scheme)












   

 Add Comment











 













 Puppet /  PUP-2271



  yumrepo attributes cannot be set to '_none_' 







 The {{yumrepo}} attribute cannot be set to the value "_none_" even though this is a supported value for the yum {{proxy}} parameter. We should fix this.   {code}  $ puppet apply -e "yumrepo {'base': proxy => '_none_'}"  Notice: Compiled catalog for localhost.localdomain in environment production in 0.03 seconds  Error: Parameter proxy failed on Yumrepo[b...















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




 














-- 
You received this message because you are subscribed

Jira (PDB-570) Remove planetarium endpoint and tests

[Ryan Senior (JIRA)]

Title: Message Title










 

 Ryan Senior updated an issue











 






 PuppetDB /  PDB-570



  Remove planetarium endpoint and tests 










Change By:

 Ryan Senior




Sprint:

 20140409 to 20140423












   

 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-570) Remove planetarium endpoint and tests

[Ryan Senior (JIRA)]

Title: Message Title










 

 Ryan Senior assigned an issue to Ryan Senior











 






 PuppetDB /  PDB-570



  Remove planetarium endpoint and tests 










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-561) Rename name to certname in nodes endpoint

[Ryan Senior (JIRA)]

Title: Message Title










 

 Ryan Senior updated an issue











 






 PuppetDB /  PDB-561



  Rename name to certname in nodes endpoint 










Change By:

 Ryan Senior




Sprint:

 20140409 to 20140423












   

 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-561) Rename name to certname in nodes endpoint

[Ryan Senior (JIRA)]

Title: Message Title










 

 Ryan Senior assigned an issue to Ryan Senior











 






 PuppetDB /  PDB-561



  Rename name to certname in nodes endpoint 










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 (PUP-1114) Deprecate environment configuration in puppet.conf

[Kurt Wall (JIRA)]

Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-1114



  Deprecate environment configuration in puppet.conf 










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-2318) Ruby open classes functionality breaks when used in ERB templates

[Mike Reznik (JIRA)]

Title: Message Title










 

 Mike Reznik created an issue











 






 Puppet /  PUP-2318



  Ruby open classes functionality breaks when used in ERB templates 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 22/Apr/14 6:13 AM




Priority:

  Normal




Reporter:

 Mike Reznik












<%
class Array
 def to_sudo
  self.map{|i| "/some/path/to/prepend/*/#{i}" }.join(',')
 end
end

command_list1 = %w (command1.sh command2.sh command3.sh).to_sudo
command_list2 = %w (command4.sh command5.sh command6.sh).to_sudo
%>

Cmnd_Alias CMD1 = <%= command_list1 %>
Cmnd_Alias CMD2 = <%= command_list2 %>



The ERB template above complies and produces the desired output when ran directly on command-line. However, when executed via Puppet, it produces the following error:


Detail: undefined method `to_sudo' for #















   

 Add Comment






 

Jira (PUP-2318) Ruby open classes functionality breaks when used in ERB templates

[Mike Reznik (JIRA)]

Title: Message Title










 

 Mike Reznik updated an issue











 






 Puppet /  PUP-2318



  Ruby open classes functionality breaks when used in ERB templates 










Change By:

 Mike Reznik









 {noformat}<%class Array def to_sudo  self.map{|i| "/some/path/to/prepend/*/#{i}" }.join(',') endendcommand_list1 = %w (command1.sh command2.sh command3.sh).to_sudocommand_list2 = %w (command4.sh command5.sh command6.sh).to_sudo%>Cmnd_Alias CMD1 = <%= command_list1 %>Cmnd_Alias CMD2 = <%= command_list2 %>{noformat}The ERB template above complies and produces the desired output when  ran  run  directly on command-line. However, when executed via Puppet, it produces the following error:{noformat}Detail: undefined method `to_sudo' for #{noformat}












   

 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-217) Add support for CORS or JSONP

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-217



  Add support for CORS or JSONP 










Change By:

 Kenneth Barber




Summary:

 Respond to "Content-Type: application/jsonp" Add support for CORS or JSONP












   

 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-217) Add support for JSONP

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-217



  Add support for JSONP 










Change By:

 Kenneth Barber




Summary:

 Add support for  CORS or  JSONP












   

 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-587) Add API support for CORS

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-587



  Add API support for CORS 










Change By:

 Kenneth Barber




Summary:

 puppetdb should have an option to allow cross-domain requests Add API support for CORS












   

 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-587) Add API support for CORS

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Add API support for CORS 










JSONP support covered by this ticket: PDB-217












   

 Add Comment











 













 PuppetDB /  PDB-587



  Add API support for CORS 







 To allow interesting client-side _javascript_ usage of puppetdb, there should be a mechanism to define a Cross Origin Filter to allow cross-domain requests.   More information:  http://wiki.eclipse.org/Jetty/Feature/Cross_Origin_Filter   Currently, I get errors like this in my _javascript_:  XMLHttpRequest cannot load http://puppetdb.xxx.xxx:8080/v3/nodes/x...















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




 














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

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-587



  Add API support for CORS 










Change By:

 Kenneth Barber




Story Points:

 5












   

 Add Comment











 










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




 














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

Jira (PUP-2317) Future parser does not honor dynamic environments with modulepath in Puppet 3.5.1

[Daniele Sluijters (JIRA)]

Title: Message Title










 

 Daniele Sluijters commented on an issue











 






  Re: Future parser does not honor dynamic environments with modulepath in Puppet 3.5.1 










William Van Hevelingen also mentioned on IRC that downgrading to 3.4.x fixed the issue, with future parser enabled.












   

 Add Comment











 













 Puppet /  PUP-2317



  Future parser does not honor dynamic environments with modulepath in Puppet 3.5.1 







 Puppet 3.5.1 with Future parser enabled does not honor modulepath or manifest config with $environment. It works as expected when disabling future parser.















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




 














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

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Add support for JSONP 










There is probably a high chance supporting JSONP is not necessary if we support CORS: PDB-587 ... however some browser versions might still not support CORS so its worth checking.












   

 Add Comment











 













 PuppetDB /  PDB-217



  Add support for JSONP 







 At HomeAway, we currently use JIRA for everything under the sun, and all of our internal tools have jsonp apis so that we can build _javascript_ dashboards in wiki pages.   We would *love* for puppetdb to support jsonp in its API with a callback= parameter to give the name of the wrapping _javascript_ function. This would allow us to use puppetdb directly ...















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




 














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

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Support trusted facts in PuppetDB fact storage 










Lindsey Smith PO and Patrick Carlisle understood, right now though I think we need to scope what work we'll need to do to Puppet for us to get at this data, since we are largely a dumb consumer of whatever Puppet gives us. Currently I believe Puppet does not give us this data using the current methodologies anyway.
Once we determine how we can get at this data then we can determine a solution for submitting it with the PDB terminus, and storing it within PuppetDB.
/cc Andy Parker, Henrik Lindberg and Deepak Giridharagopal any thoughts guys?












   

 Add Comment











 













 PuppetDB /  PDB-565



  Support trusted facts in PuppetDB fact storage 







 Since Puppet 3.4, we've added a new top-scope, immutable hash called 'trusted' which is exposed in the DSL and populated with the authenticated certname from the SSL certificate that made the catalog request. In addition, custom attributes can be added to the certificate and will also show up in the trusted hash (see http://docs.puppetlabs.com/puppet/late...















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




 

Jira (PDB-465) Add Trusty (Ubuntu 14.04) Packaging Support

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-465



  Add Trusty (Ubuntu 14.04) Packaging Support 










Change By:

 Kenneth Barber




Sprint:

 20140409 to 20140423












   

 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-586) Store and append to global variables

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Store and append to global variables 










Daniele Sluijters what is wrong with just wrapping exported resources to achieve this?
I would create 2 functions ... 1 to wrap the export and another to wrap the "collection" and merging.



node "web1" {
  variable_export("my_global_array", $::fqdn)
}
node "balancer" {
  $my_global_array = variable_collect("my_global_array")
}



In this case 'variable_collect' would not actually do a traditional collection, it would use the API directly to query for this information and munge the values together in an array.
The 'variable_export' would really just internally be doing an export on some custom resource (that really does nothing). In the DSL this would look something like:



@@variable_export_data { "${fqdn}-${global_id}":
  tag => "variable_export_${global_id}",
  data ="" $::fqdn,
}



If this seems viable, I would actually ship it as a Puppet module (at least initially).












   

 Add Comment











 













 PuppetDB /  PDB-586



  Store and append to global variables 







 One fairly common scenario is to want to auto-reconfigure parts of your system as daemons and machines come online or go offline. This can already partially be resolved with exported resources but not all of it.   The scenario would be something like this: I want all my MySQL XtraDB Cluster nodes to become aware of a new member 

Jira (PUP-2164) require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized

[Robert Buchholz (JIRA)]

Title: Message Title










 

 Robert Buchholz commented on an issue











 






  Re: require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized 










We have the same symptoms after installing a puppet update on el6 today (to puppet-3.5.1-1.el6). rubygems-json was installed before, but ruby-json was not. For some reason, the /usr/lib/ruby/gems/1.8/gems/json-1.5.5 directory was gone from the system though. No idea what caused it, but "yum reinstall rubygems-json" fixed it.












   

 Add Comment











 













 Puppet /  PUP-2164



  require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized 







 We now ship {{rubygems-json}} for EL 6.x as a dependency of Puppet 3.5.0. However, Ruby 1.8.7 does not initialize the Gem search paths by default which leads to the following error:   {noformat}  # yum install -y puppet-3.5.0-1.el6   # ... much yum output ...   # ruby -e ' require "puppet" '  /usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3:in `require':...















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




 














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

Jira (PDB-586) Store and append to global variables

[Daniele Sluijters (JIRA)]

Title: Message Title










 

 Daniele Sluijters commented on an issue











 






  Re: Store and append to global variables 










That's already a lot better than what I came up with. I hadn't considered wrapping a function around it which ended up being incredibly verbose and complex for getting something as simple as a variable.
Wrapping exported resources in turn in functions is workable but imho pretty messy. It gets the job done and to the end user it won't matter much as long as we get the functions to do what people expect.
The reason I brought it up is because I think it fits nicely into PuppetDB with a /variables endpoint that you can query, scoped per environment and what not. I think this kind of data would also be useful to drive other things than just Puppet through PuppetDB's API but having to untangle resources that way from a catalog would make that a lot more difficult.
We could start out with the function method first and see what people come up with. Armature perhaps?












   

 Add Comment











 













 PuppetDB /  PDB-586



  Store and append to global variables 







 One fairly common scenario is to want to auto-reconfigure parts of your system as daemons and machines come online or go offline. This can already partially be resolved with exported resources but not all of it.   The scenario would be something like this: I want all my MySQL XtraDB Cluster nodes to become aware of a new member when it joins the cluster















 This message was sent by Atlassian JIRA (v6.1.4#615

Jira (PUP-1890) Wrong encoding type for file

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen assigned an issue to Charlie Sharpsteen











 






 Puppet /  PUP-1890



  Wrong encoding type for file 










Change By:

 Charlie Sharpsteen




Assignee:

 Hadmut Danisch 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 (PUP-2317) Future parser does not honor dynamic environments with modulepath in Puppet 3.5.1

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow updated an issue











 






 Puppet /  PUP-2317



  Future parser does not honor dynamic environments with modulepath in Puppet 3.5.1 










Change By:

 Joshua Partlow




Component/s:

 Modules




Story Points:

 2












   

 Add Comment











 










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




 














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

Jira (PDB-586) Store and append to global variables

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Store and append to global variables 










> That's already a lot better than what I came up with. I hadn't considered wrapping a function around it which ended up being incredibly verbose and complex for getting something as simple as a variable. > > Wrapping exported resources in turn in functions is workable but imho pretty messy. It gets the job done and to the end user it won't matter much as long as we get the functions to do what people expect.
Yeah, I think the user cares little about the backend implementation.
> The reason I brought it up is because I think it fits nicely into PuppetDB with a /variables endpoint that you can query, scoped per environment and what not. I think this kind of data would also be useful to drive other things than just Puppet through PuppetDB's API but having to untangle resources that way from a catalog would make that a lot more difficult.
Which is a nice idea, but we should prove the concept using something that doesn't require a lot of effort first.
> We could start out with the function method first and see what people come up with. Armature perhaps?
I think starting with the function method first will get the methodology proven. Not sure if we need an armature as such, thats more of a language change thing. Personally I'd avoid changing the language to do this until its proven with just functions and we iron out all the different use cases there. We can post the link to such a module on the community plugin page for PuppetDB if you wanted to write something up.












   

 Add Comment











 













 PuppetDB /  PDB-586



  Store and append to global variables 







 One fairly common scenario is to want to auto-reconfigure parts of your system as daemons and machines come online or go offline. This can already partially be 

Jira (PUP-2319) Puppet 3.6.0-rc1 2014-05-01 Release

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2319



  Puppet 3.6.0-rc1 2014-05-01 Release 










Issue Type:

  Task




Assignee:

 Release Engineering




Created:


 22/Apr/14 9:36 AM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Puppet 3.6.0-rc1 2014-05-01 Release












   

 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 em

Jira (PUP-2320) Ensure tests are passing

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2320



  Ensure tests are passing 










Issue Type:

  Sub-task




Assignee:

 Rob Reynolds




Created:


 22/Apr/14 9:36 AM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Ensure tests are passing












   

 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 ema

Jira (PUP-2321) Is there a bug targeted at the release for every commit?

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2321



  Is there a bug targeted at the release for every commit? 










Issue Type:

  Sub-task




Assignee:

 Rob Reynolds




Created:


 22/Apr/14 9:36 AM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Is there a bug targeted at the release for every commit?












   

 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 unsubscrib

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

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2323



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










Issue Type:

  Sub-task




Assignee:

 Rob Reynolds




Created:


 22/Apr/14 9:36 AM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










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












   

 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 Bu

Jira (PUP-2322) Is there a commit for every bug targeted at the release?

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2322



  Is there a commit for every bug targeted at the release? 










Issue Type:

  Sub-task




Assignee:

 Rob Reynolds




Created:


 22/Apr/14 9:36 AM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Is there a commit for every bug targeted at the release?












   

 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 unsubscrib

Jira (PUP-2325) Update version number

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2325



  Update version number 










Issue Type:

  Sub-task




Assignee:

 Rob Reynolds




Created:


 22/Apr/14 9:36 AM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Update version number












   

 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 

Jira (PUP-2332) Update the downloads page

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2332



  Update the downloads page 










Issue Type:

  Sub-task




Assignee:

 Melissa Stone




Created:


 22/Apr/14 9:37 AM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Update the downloads page












   

 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 

Jira (PUP-2329) Docs pushed

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2329



  Docs pushed 










Issue Type:

  Sub-task




Assignee:

 Nicholas Fagerlund




Created:


 22/Apr/14 9:37 AM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Docs pushed












   

 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+un

Jira (PUP-2333) Send out announcements

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2333



  Send out announcements 










Issue Type:

  Sub-task




Assignee:

 Eric Sorenson




Created:


 22/Apr/14 9:37 AM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Send out announcements












   

 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 

Jira (PUP-2326) Tag the release and create packages

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2326



  Tag the release and create packages 










Issue Type:

  Sub-task




Assignee:

 Melissa Stone




Created:


 22/Apr/14 9:36 AM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Tag the release and create packages












   

 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 emai

Jira (PUP-2334) Close all resolved tickets in Jira

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2334



  Close all resolved tickets in Jira 










Issue Type:

  Sub-task




Assignee:

 Rob Reynolds




Created:


 22/Apr/14 9:37 AM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Close all resolved tickets in Jira












   

 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 

Jira (PUP-2324) Prepare long form release notes and short form release story

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2324



  Prepare long form release notes and short form release story 










Issue Type:

  Sub-task




Assignee:

 Nicholas Fagerlund




Created:


 22/Apr/14 9:36 AM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Prepare long form release notes and short form release story












   

 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.

Jira (PUP-2328) Go/no-go meeting

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2328



  Go/no-go meeting 










Issue Type:

  Sub-task




Assignee:

 Rob Reynolds




Created:


 22/Apr/14 9:36 AM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Go/no-go meeting












   

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

Jira (PUP-2331) Push tag

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2331



  Push tag 










Issue Type:

  Sub-task




Assignee:

 Melissa Stone




Created:


 22/Apr/14 9:37 AM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Push tag












   

 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...@g

Jira (PUP-2330) Packages pushed

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2330



  Packages pushed 










Issue Type:

  Sub-task




Assignee:

 Melissa Stone




Created:


 22/Apr/14 9:37 AM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Packages pushed












   

 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

Jira (PUP-2327) Smoke test packages

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-2327



  Smoke test packages 










Issue Type:

  Sub-task




Assignee:

 Rob Reynolds




Created:


 22/Apr/14 9:36 AM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Smoke test packages












   

 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 pupp

Jira (PUP-2317) Future parser does not honor dynamic environments with modulepath in Puppet 3.5.1

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow updated an issue











 






 Puppet /  PUP-2317



  Future parser does not honor dynamic environments with modulepath in Puppet 3.5.1 










Change By:

 Joshua Partlow




Sprint:

 Week 2014-4-23 to 2014-4-30












   

 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-2093) PMT should use the Forge's /v3 API

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow updated an issue











 






 Puppet /  PUP-2093



  PMT should use the Forge's /v3 API 










Change By:

 Joshua Partlow




Sprint:

 Week 2014-4-23 to 2014-4-30












   

 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-247) PR (617): Changes to netmask.rb for AIX - jcitarello

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: PR (617): Changes to netmask.rb for AIX - jcitarello 










I'm trying to confirm that '/etc/ifconfig' needs to be added to the common paths for AIX, and I'm coming up with a blank. On AIX 5.3 and 7.1 '/etc/ifconfig' is a symlink to '/usr/sbin/ifconfig', and the only references to '/etc/ifconfig' that I can find come from extremely old UNIXes (IRIX, TRU64), and most recently AIX 4. I would like to know more about why this is necessary since supported AIX versions have ifconfig in a standard location. Under what circumstances is it necessary to check '/etc/ifconfig'?












   

 Add Comment











 













 Facter /  FACT-247



  PR (617): Changes to netmask.rb for AIX - jcitarello 







 h2. Changes to netmask.rb for AIX   * Author: <>  * Company:   * Github ID: [jcitarello|https://github.com/jcitarello]  * [Pull Request 617 Discussion|https://github.com/puppetlabs/facter/pull/617]  * [Pull Request 617 File Diff|https://github.com/puppetlabs/facter/pull/617/files]  h2. Pull Request Description   The changes included are to accommodat...















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




 














-- 
You received this message because you are

Jira (PUP-1890) Wrong encoding type for file

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: Wrong encoding type for file 










Thanks a bunch for the logs and example file.
It appears that the second "o" in Momоt___.ttf is actually U+043E "Cyrillic small letter o". This error shows up even when the Puppet agent is running in a UTF-8 locale, so there must be something in the pathname handling that is forcing the string to US-ASCII.












   

 Add Comment











 













 Puppet /  PUP-1890



  Wrong encoding type for file 







 Hi,   I am running a puppet server under Ubuntu 12.04 (Puppet 2.7.11) and a puppet client under Ubuntu 14.04 (Puppet 3.4.2).   I am distributing a directory of ttf fonts from the server to the clients, the rule is     file{"/usr/local/share/fonts/FreeFonts":  ensure => directory,  mode => 0444,  recurse => true,   ...















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




 














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

Jira (PDB-586) Store and append to global variables

[Daniele Sluijters (JIRA)]

Title: Message Title










 

 Daniele Sluijters commented on an issue











 






  Re: Store and append to global variables 










Sure, that seems like a good idea. You mentioned you already had some code to support this? I'm especially curious about creating resources from a function.












   

 Add Comment











 













 PuppetDB /  PDB-586



  Store and append to global variables 







 One fairly common scenario is to want to auto-reconfigure parts of your system as daemons and machines come online or go offline. This can already partially be resolved with exported resources but not all of it.   The scenario would be something like this: I want all my MySQL XtraDB Cluster nodes to become aware of a new member when it joins the cluster















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




 














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

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo assigned an issue to Adrien Thebo











 






 Puppet /  PUP-1932



  systemd reports transient (in-memory) services 










Change By:

 Adrien Thebo




Assignee:

 Adrien Thebo












   

 Add Comment











 










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




 














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

Jira (PDB-593) PR (936): Maint/1.6.x/fedora sqlite3 gem - kbarber

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (936): Maint/1.6.x/fedora sqlite3 gem - kbarber 










Pull request Maint/1.6.x/fedora sqlite3 gem has been closed.












   

 Add Comment











 













 PuppetDB /  PDB-593



  PR (936): Maint/1.6.x/fedora sqlite3 gem - kbarber 







 h2. Maint/1.6.x/fedora sqlite3 gem   * Author: Ken Barber   * Company: Puppet Labs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 936 Discussion|https://github.com/puppetlabs/puppetdb/pull/936]  * [Pull Request 936 File Diff|https://github.com/puppetlabs/puppetdb/pull/936/files]  h2. Pull Request Description -...















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




 














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

Jira (PDB-593) PR (936): Maint/1.6.x/fedora sqlite3 gem - kbarber

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-593



  PR (936): Maint/1.6.x/fedora sqlite3 gem - kbarber 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 22/Apr/14 4:46 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Maint/1.6.x/fedora sqlite3 gem


Author: Ken Barber 


Company: Puppet Labs Inc.


Github ID: kbarber


Pull Request 936 Discussion


Pull Request 936 File Diff


Pull Request Description


(webhooks-id: 98b39a179f2d5113d7c6d6cc858e9984)









   

Jira (PUP-2160) Undocumented hash lookup change with future evaluator in Puppet 3.5.0

[Nicholas Fagerlund (JIRA)]

Title: Message Title










 

 Nicholas Fagerlund updated an issue











 






 Puppet /  PUP-2160



  Undocumented hash lookup change with future evaluator in Puppet 3.5.0 










Change By:

 Nicholas Fagerlund




Summary:

 Undocumented hash lookup change  with future evaluator  in Puppet 3.5.0












   

 Add Comment











 










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




 














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

Jira (PUP-2160) Undocumented hash lookup change with future evaluator in Puppet 3.5.0

[Nicholas Fagerlund (JIRA)]

Title: Message Title










 

 Nicholas Fagerlund updated an issue











 






 Puppet /  PUP-2160



  Undocumented hash lookup change with future evaluator in Puppet 3.5.0 










Change By:

 Nicholas Fagerlund




Labels:

 docs_reviewed future-parser












   

 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-2160) Undocumented hash lookup change with future evaluator in Puppet 3.5.0

[Nicholas Fagerlund (JIRA)]

Title: Message Title










 

 Nicholas Fagerlund commented on an issue











 






  Re: Undocumented hash lookup change with future evaluator in Puppet 3.5.0 










I plan to cut new copies of every single page of the language guide and designate them as future docs, then make changes until they're brought in line with the rewritten language behavior. This is being tracked as DOC-722.
I've made a ticket for this change: DOCUMENT-85. Docs work will be tracked in that ticket, not this one.
Henrik Lindberg, reassigning to you to decide if any engineering effort is needed. If not, you can close as wontfix. Per Cederqvist, thanks for catching this! I'll add you as a watcher to document-85.












   

 Add Comment











 













 Puppet /  PUP-2160



  Undocumented hash lookup change with future evaluator in Puppet 3.5.0 







 Consider this code:   {noformat}  $h = { "k1" => "value" }  $v = $h["k2"]  {noformat}   Puppet 3.5.0 sets $v to undef. Earlier versions set $v to the empty string, I believe. (Possibly that isn't true. Possibly it is instead some comparison changes that bites me.)   What happens when you look up a non-existing key in a hash should be documented on htt...















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




 



   

Jira (PUP-2160) Undocumented hash lookup change with future evaluator in Puppet 3.5.0

[Nicholas Fagerlund (JIRA)]

Title: Message Title










 

 Nicholas Fagerlund updated an issue











 






 Puppet /  PUP-2160



  Undocumented hash lookup change with future evaluator in Puppet 3.5.0 










Change By:

 Nicholas Fagerlund




Assignee:

 Nicholas Fagerlund 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-2342) Cron acceptance tests may leak state

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Cron acceptance tests may leak state 










Merged in b536de1.












   

 Add Comment











 













 Puppet /  PUP-2342



  Cron acceptance tests may leak state 







 Some of the Cron acceptance tests do not properly tear down their state after they are complete. Because of this leaked state, acceptance tests can start demonstrating test order dependent failures. While this isn't currently an issue it is only due to the inode ordering on our current test environments. When working with [~alice] on moving tests to GCE 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-2342) Cron acceptance tests may leak state

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Cron acceptance tests may leak state 










/cc Alice Nodelman












   

 Add Comment











 













 Puppet /  PUP-2342



  Cron acceptance tests may leak state 







 Some of the Cron acceptance tests do not properly tear down their state after they are complete. Because of this leaked state, acceptance tests can start demonstrating test order dependent failures. While this isn't currently an issue it is only due to the inode ordering on our current test environments. When working with [~alice] on moving tests to GCE 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-2317) Future parser does not honor dynamic environments with modulepath in Puppet 3.5.1

[Eric Sorenson (JIRA)]

Title: Message Title










 

 Eric Sorenson updated an issue











 






 Puppet /  PUP-2317



  Future parser does not honor dynamic environments with modulepath in Puppet 3.5.1 










Change By:

 Eric Sorenson




Assignee:

 William Van Hevelingen












   

 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-2317) Future parser does not honor dynamic environments with modulepath in Puppet 3.5.1

[Eric Sorenson (JIRA)]

Title: Message Title










 

 Eric Sorenson commented on an issue











 






  Re: Future parser does not honor dynamic environments with modulepath in Puppet 3.5.1 










can you please paste your puppet.conf into the ticket? i wasn't able to trivially reproduce this.












   

 Add Comment











 













 Puppet /  PUP-2317



  Future parser does not honor dynamic environments with modulepath in Puppet 3.5.1 







 Puppet 3.5.1 with Future parser enabled does not honor modulepath or manifest config with $environment. It works as expected when disabling future parser.















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




 














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

[Felipe Salum (JIRA)]

Title: Message Title










 

 Felipe Salum commented on an issue











 






  Re: Provide a manifest directory where all manifests are automatically parsed. 










Does it work with puppet apply ?
I changed the config option for manifest in puppet.conf to point to /etc/puppet/manifests which I have a lot of *.pp related to each node cluster I support and I'm not sure how to use 'puppet apply site.pp' as before without the include in the site.pp. It doesn't find the node definition for the host running puppet apply that is outside site.pp in a specific node.pp manifest.
Where is the documentation or best practice about the new way to do it ?












   

 Add Comment











 













 Puppet /  PUP-865



  Provide a manifest directory where all manifests are automatically parsed. 







 There is at least one major use case where users need to import a set of manifest files, the following pattern:   {code}  # manifests/site.pp  import nodes/*.pp  {code}   As per the parent ticket, we're looking to deprecate `import`, and the most obvious solution appears to be to offer a configuration option for a directory where all manifest files are ...















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




 

Jira (PUP-2348) Puppet run randomly fails with "Unknown function at on node "

[Francois Conil (JIRA)]

Title: Message Title










 

 Francois Conil created an issue











 






 Puppet /  PUP-2348



  Puppet run randomly fails with "Unknown function  at  on node " 










Issue Type:

  Bug




Affects Versions:


 3.5.1




Assignee:


 Unassigned




Created:


 22/Apr/14 8:33 PM




Environment:


Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux ruby 2.1.1p76 (2014-02-24 revision 45161) [x86_64-linux]




Priority:

  Major




Reporter:

 Francois Conil










After upgrading puppetmaster to 3.5.1 we started experiencing random manifests failures.
A given (manifest, function, node) tuple can work several times and then fail, only to succeed on the next run (with the exact same code base).
Running the agent and the master in debug does not bring any more information on why the function cannot be found. 
The issue appears across multiple modules and custom functions, and cannot be repeated on demand. 
Reverting to puppet 3.4.3 and facter 1.7.5 fixed the issue, reverting to 3.5.0.rc3 (keeping facter at 2.0.1) did not.
The error is always of the form :
"Unknown function  at  on node "

Jira (PUP-1799) New Function API

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: New Function API 










Andy Parker Henrik Lindberg I went ahead and merged this so that it would run with tonight's acceptance. If there are more doc adjustments I figured they can go in as doc or maint. I believe it was ready to go and we just forgot about it because of the env cacheing entertainment.












   

 Add Comment











 













 Puppet /  PUP-1799



  New Function API 














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




 














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

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: New Function API 










merged in 640cf90












   

 Add Comment











 













 Puppet /  PUP-1799



  New Function API 














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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-2317) Future parser does not honor dynamic environments with modulepath in Puppet 3.5.1

[William Van Hevelingen (JIRA)]

Title: Message Title










 

 William Van Hevelingen commented on an issue











 






  Re: Future parser does not honor dynamic environments with modulepath in Puppet 3.5.1 










[main] modulepath=/etc/puppet/environments/$environment/modules/internal:/etc/puppet/environments/$environment/modules/public:/etc/puppet/secure manifest=/etc/puppet/environments/$environment/manifests/site.pp logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter pluginsync=true runinterval=1380 configtimeout=600 splay=true report=true ca_server = puppetca.cat.pdx.edu server=tassadar.cat.pdx.edu parser=future
[master] ca = false storeconfigs = true storeconfigs_backend = puppetdb reports = foreman reportdir = /disk/trump/puppet-reports
[user] environment = production












   

 Add Comment











 













 Puppet /  PUP-2317



  Future parser does not honor dynamic environments with modulepath in Puppet 3.5.1 







 Puppet 3.5.1 with Future parser enabled does not honor modulepath or manifest config with $environment. It works as expected when disabling future parser.















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