Jira (PUP-1764) PR (2387): Respect Yum's lock - seveas

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2387): Respect Yum's lock - seveas 










seveas commented:
The whole point of this patch is to not open any databases at all before acquiring the yum lock. Instantiating the YumBase object does not open any databases, so one does not need to close any databases if doLock fails, this is why I moved this out of the existing try/finally.












   

 Add Comment











 













 Puppet /  PUP-1764



  PR (2387): Respect Yum's lock - seveas 







 h2. Respect Yum's lock   * Author: Dennis Kaarsemaker   * Company: Booking.com  * Github ID: [seveas|https://github.com/seveas]  * [Pull Request 2387 Discussion|https://github.com/puppetlabs/puppet/pull/2387]  * [Pull Request 2387 File Diff|https://github.com/puppetlabs/puppet/pull/2387/files]  h2. Pull Request Description   We...















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




 














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

Jira (PDB-402) Disable AOT compiling of PuppetDB code

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Disable AOT compiling of PuppetDB code 










Merged here: https://github.com/puppetlabs/puppetdb/commit/3c8bd7afc67e2c73bd221c5febaa6ef2bd4de9f8












   

 Add Comment











 













 PuppetDB /  PDB-402



  Disable AOT compiling of PuppetDB code 







 We currently need to use AOT to support "java -jar .. services..." form of execution. We can instead switch to "java -cp ... clojure.main -m services ..." which does not require AOT compiling and removes the need to do any AOT compiling of PuppetDB code. This would have saved us a lot of headaches. The steps needed to do this are below:   - Change scri...















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




 














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

Jira (PDB-123) Throw error message for a modified log4j.properties when we migrate to logback

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Throw error message for a modified log4j.properties when we migrate to logback 










So in the end we've decided to just package a new log4j.properties with no real content and a commented warning about the switch to logback. Package installers will find that the configuration will be overwritten - debian users will have their normal "how do you want to deal with this changing file" prompt and RPM users will get an rpmnew file to analyse. Its not perfect, but its probably good enough for most cases. Users who haven't changed their log4j.properties won't be affected, but users will hopefully be drawn to the file change containing the comment about log4j retirement.












   

 Add Comment











 













 PuppetDB /  PDB-123



  Throw error message for a modified log4j.properties when we migrate to logback 







 This ticket tracks the work to 'deprecate' log4j, which at the moment seems pretty much:   * Put a warning in the log4j.properties we ship (if users have modified this however, most packaging systems will not overwrite their version, which unfortunately, customised log4j.properties are our target market).  * Make sure its in the release notes   Honestly...















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




 




  

Jira (PDB-134) Purging resources that were exported resources sometimes fails

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-134



  Purging resources that were exported resources sometimes fails 










Change By:

 Kenneth Barber









 I'm seeing an issue where sometimes I have an exported resource that is failing to be removed from the node that is collecting them after the node has been cleaned up by running a "puppet node clean " on the puppetmaster. For example, I'm exporting both nagios_host and nagios_service resources from my nodes and collecting them on my nagios server. On the nagios server, I've set up resources of these types to be purged:   {code} resources { ['nagios_service', 'nagios_host']:  purge  => true,  notify => Service['nagios'],}  {code} If I purge a node on the puppetmaster:   {code} puppet node clean node.example.com  {code} On the next puppet run on the nagios server, I might get the following error message:   {code} warning: /Nagios_service[node.example.com SSH]: Whit[Completed_stage[post]],Whit[Admissible_stage[post]],Whit[Admissible_stage[puppetcomplete]],Whit[Completed_stage[puppetcomplete]],Whit[Completed_stage[main]],Whit[Completed_class[Nagios]],Service[nagios] still depend on me -- not purging  {code} This doesn't happen all of the time, nor does it happen for all of the nagios_service resources for this node (other nagios_service resources get cleaned up just fine). I've seen this with both the nagios_host and the nagios_service type of resources. It will continue to occur for the same resource on any subsequent run of puppet on the nagios server. To remedy this, I have to manually remove the resource it is complaining about from the nagios configuration and restart the service (something I would like to avoid).Not sure if it matters or not, but I'm using PuppetDB as the stored configurations backend.












   

 Add Comment











 










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




 

 

Jira (PDB-476) Convert the terminus performance logging one-off support solution to something permanent

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Convert the terminus performance logging one-off support solution to something permanent 










Merged here: https://github.com/puppetlabs/puppetdb/commit/95ed9db45f343a39b7dffeb60721c4921858b96d












   

 Add Comment











 













 PuppetDB /  PDB-476



  Convert the terminus performance logging one-off support solution to something permanent 







 To help diagnose some potential performance issues with the PuppetDB terminus (PE-2889), I instrumented a bunch of different operations done by the PuppetDB terminus here: https://github.com/senior/puppetdb/commit/133a76de04b709515af6dcb4759ad880ecec3d77. We should make that permanent via similar changes in master.   It seems like there is a lot of over...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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

Jira (PUP-1295) Yum provider "purge" target runs irrespective of package installation status

[Jason Corley (JIRA)]

Title: Message Title










 

 Jason Corley commented on an issue











 






  Re: Yum provider "purge" target runs irrespective of package installation status 










I'm seeing this as well with puppet 3.2.4, centos 6.5, and ruby 1.9.3p484












   

 Add Comment











 













 Puppet /  PUP-1295



  Yum provider "purge" target runs irrespective of package installation status 







 It seems the yum provider will try to purge an absent package:[root@test ~]# cat test.pp  package { logwatch: ensure => purged; }   [root@test ~]# /bin/rpm -q logwatch --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}'  package logwatch is not installed   [root@test ~]# puppet -d -v test.pp  debug: P...















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




 














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

Jira (FACT-352) cannot load such file -- win32/dir

[Maurizio De Santis (JIRA)]

Title: Message Title










 

 Maurizio De Santis updated an issue











 






 Facter /  FACT-352



  cannot load such file -- win32/dir 










Change By:

 Maurizio De Santis









 I have facter inside the Gemfile of a Rails app. I get this error: {noformat} cannot load such file -- win32/dirC:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:251:in `require'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:251:in `block in require'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:236:in `load_dependency'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:251:in `require'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/facter-1.7.5/lib/facter/util/config.rb:47:in `uired)>'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:251:in `require'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:251:in `block in require'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:236:in `load_dependency'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:251:in `require'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/facter-1.7.5/lib/facter/util/resolution.rb:7:in `required)>'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:251:in `require'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:251:in `block in require'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:236:in `load_dependency'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:251:in `require'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/facter-1.7.5/lib/facter/util/fact.rb:2:in `ed)>'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:251:in `require'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:251:in `block in require'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:236:in `load_dependency'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb:251:in `require'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/facter-1.7.5/lib/facter.rb:23:in `'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/facter-1.7.5/lib/facter.rb:19:in `'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.5.3/lib/bundler/runtime.rb:76:in `require'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.5.3/lib/bundler/runtime.rb:76:in `block (2 levels) in require'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.5.3/lib/bundler/runtime.rb:72:in `each'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.5.3/lib/bundler/runtime.rb:72:in `block in require'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.5.3/lib/bundler/runtime.rb:61:in `each'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.5.3/lib/bundler/runtime.rb:61:in `require'C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.5.3/lib/bundler.rb:131:in `require'C:/Users/PcMorgan/Sviluppo/desy/config/application.rb:7:in `'C:/Ruby200-x64/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require'C:/Ruby2

Jira (FACT-352) cannot load such file -- win32/dir

[Maurizio De Santis (JIRA)]

Title: Message Title










 

 Maurizio De Santis created an issue











 






 Facter /  FACT-352



  cannot load such file -- win32/dir 










Issue Type:

  Bug




Affects Versions:


 1.7.5




Assignee:

 Eric Sorenson




Created:


 27/Feb/14 7:27 AM




Environment:


Windows 7 64bit, Ruby 2.0.0 x64




Priority:

  Normal




Reporter:

 Maurizio De Santis










I have facter inside the Gemfile of a Rails app. I get this error:
cannot load such file – win32/dir C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb :251:in `require' C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb :251:in `block in require' C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb :236:in `load_dependency' C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb :251:in `require' C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/facter-1.7.5/lib/facter/util/config.rb:47:in ` uired)>' C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb :251:in `require' C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb :251:in `block in require' C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb :236:in `load_dependency' C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb :251:in `require' C:/Ruby200-x6

Jira (PDB-478) PR (873): Unpin beaker now that 1.7.0 is released - kbarber

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-478



  PR (873): Unpin beaker now that 1.7.0 is released - kbarber 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 27/Feb/14 7:31 AM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Unpin beaker now that 1.7.0 is released


Author: Ken Barber 


Company: Puppetlabs Inc.


Github ID: kbarber


Pull Request 873 Discussion


Pull Request 873 File Diff


Pull Request Description

We had a pinned version of beaker. This patch unpins it now that the code that we need has been released.
Signed-off-by: Ken Barber 

(webhooks-id: f62c02e73282e2f86d966d577f6dda39)

 

Jira (PDB-478) PR (873): Unpin beaker now that 1.7.0 is released - kbarber

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-478



  PR (873): Unpin beaker now that 1.7.0 is released - kbarber 










Change By:

 Kenneth Barber




Sprint:

 20140226 to 20140305












   

 Add Comment











 










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




 














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

Jira (PDB-478) PR (873): Unpin beaker now that 1.7.0 is released - kbarber

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-478



  PR (873): Unpin beaker now that 1.7.0 is released - kbarber 










Change By:

 Kenneth Barber




Story Points:

 0












   

 Add Comment











 










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




 














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

Jira (FACT-353) some facts do not work with locales set

[redmine.exporter (JIRA)]

Title: Message Title










 

 redmine.exporter created an issue











 






 Facter /  FACT-353



  some facts do not work with locales set 










Issue Type:

  Bug




Assignee:

 Eric Sorenson




Created:


 27/Feb/14 7:39 AM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










facter does not clean locale environment variables prior to executing commands and sometimes falls over the localized output. I'm not sure whether this is relevant for facter being executed by puppet, but it makes debugging a lot harder. For example with the macaddress fact
 root@mail:~# facter | grep mac Could not retrieve macaddress: undefined method `split' for nil:NilClass Could not retrieve macaddress: undefined method `split' for nil:NilClass root@mail:~# LANG=C LC_ALL=C facter | grep mac macaddress => 52:54:00:94:f3:1c macaddress_eth0 => 52:54:00:94:f3:1c 
The reason is that macaddress.rb is looking for ether or HWaddr
 setcode do ether = [] output = Facter::Util::Resolution.exec("/sbin/ifconfig -a") output.each_line do |s| ether.push($1) if s =~ /(?:ether|HWaddr) (\w {1,2}:\w{1,2}
:\w {1,2}:\w{1,2}
:\w {1,2}:\w{1,2}
)/ end Facter::Util::Macaddress.standardize(ether[0]) 
which is not contained in the localized output
 root@mail:~# ifconfig -a eth0 Link encap:Ethernet Hardware Adresse 52:54:00:94:f3:1c  inet Adresse:80.244.243.68 Bcast:80.244.243.71 Maske:255.255.255.248 inet6-Adresse: 2001:4d88:1005::25:1:2/64 Gültigkeitsbereich:Global inet6-Adresse: fe80::5054:ff:fe94:f31c/64 Gültigkeitsbereich:Verb

Jira (HI-221) Cannot concatenate arrays when interpolating

[Sylvain Baubeau (JIRA)]

Title: Message Title










 

 Sylvain Baubeau created an issue











 






 Hiera /  HI-221



  Cannot concatenate arrays when interpolating 










Issue Type:

  Bug




Affects Versions:


 1.3.2




Assignee:


 Unassigned




Attachments:


 common.yaml, hiera.yaml, override.yaml




Created:


 27/Feb/14 8:18 AM




Priority:

  Normal




Reporter:

 Sylvain Baubeau










If I have a YAML data file with the following content : — myarray:


1


2


3 myrefarray: "% {hiera('myarray')}
"


And an other one with :
— myrefarray:


4


5
  

Jira (PDB-478) PR (873): Unpin beaker now that 1.7.0 is released - kbarber

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (873): Unpin beaker now that 1.7.0 is released - kbarber 










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












   

 Add Comment











 













 PuppetDB /  PDB-478



  PR (873): Unpin beaker now that 1.7.0 is released - kbarber 







 h2. Unpin beaker now that 1.7.0 is released   * Author: Ken Barber   * Company: Puppetlabs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 873 Discussion|https://github.com/puppetlabs/puppetdb/pull/873]  * [Pull Request 873 File Diff|https://github.com/puppetlabs/puppetdb/pull/873/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.g

Jira (PUP-1784) Unable to remove Cron environment

[Reinier Schoof (JIRA)]

Title: Message Title










 

 Reinier Schoof created an issue











 






 Puppet /  PUP-1784



  Unable to remove Cron environment 










Issue Type:

  Bug




Affects Versions:


 3.4.2




Assignee:

 Kylo Ginsberg




Components:


 Types and Providers




Created:


 27/Feb/14 8:29 AM




Environment:


Debian 7 FreeBSD 9.2




Labels:


 cron environment environmen




Priority:

  Normal




Reporter:

 Reinier Schoof










When I set an environment parameter for a Cron resource, it can't be removed afterwards. Defining an empty environment parameter is not allowed.
For example:
cron  { 'test': command => '/bin/echo', }
creates:


Puppet Name

Jira (PUP-1639) Some modules fail to install into target_dir

[Eric Veiras Galisson (JIRA)]

Title: Message Title










 

 Eric Veiras Galisson commented on an issue











 






  Re: Some modules fail to install into target_dir 










Andrew Parker : I'm not using NFS to store my modules directory.












   

 Add Comment











 













 Puppet /  PUP-1639



  Some modules fail to install into target_dir 







 puppet module install puppetlabs/apache -i puppet/forge-modules   Notice: Preparing to install into /home/www/puppet/forge-modules ...  Notice: Created target directory /home/www/puppet/forge-modules  Notice: Downloading from https://forge.puppetlabs.com ...  Notice: Installing -- do not interrupt ...  Error: No such file or directory - /home/www/puppet/...















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




 














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

Jira (PUP-1785) Services without any init script on Freebsd result in error

[Dolf Schimmel (JIRA)]

Title: Message Title










 

 Dolf Schimmel updated an issue











 






 Puppet /  PUP-1785



  Services without any init script on Freebsd result in error 










Change By:

 Dolf Schimmel




Environment:

 FreeBSD  tank3.transip.nl  9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: Thu Sep 26 22:50:31 UTC 2013 r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64 puppet --version: 3.4.2ruby --version: ruby 1.9.3p484 (2013-11-22 revision 43786) [amd64-freebsd9]












   

 Add Comment











 










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




 














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

Jira (PUP-1785) Services without any init script on Freebsd result in error

[Dolf Schimmel (JIRA)]

Title: Message Title










 

 Dolf Schimmel created an issue











 






 Puppet /  PUP-1785



  Services without any init script on Freebsd result in error 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 27/Feb/14 8:38 AM




Environment:


FreeBSD tank3.transip.nl 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: Thu Sep 26 22:50:31 UTC 2013 r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 puppet --version: 3.4.2 ruby --version: ruby 1.9.3p484 (2013-11-22 revision 43786) [amd64-freebsd9]




Priority:

  Normal




Reporter:

 Dolf Schimmel










I'm trying to stop a service in case it's still running. The package the service belongs to may have already been removed, so we cannot rely on the init script.
This is my manifest:

 service { 'zabbix-agent': audit => all, status => "test `${::ps} | grep zabbix-agent | wc -l` == 0", stop => "kill `${::ps} | grep zabbix-agent | awk '

Unknown macro: {print $2}

'`", start => '/bin/false', hasstatus => false, hasrestart => false, }

When running `puppet agent` with --debug flag, the following relevant output is shown:

Debug: Executing 'test `ps auxwww | grep zabbix-agent | wc -l` == 0' Debug: Service[zabbix-agent](provider=freebsd): Could not find zabbix-agent in /etc/rc.d Debug: Service[zabbix-agent](provider=freebsd): Could not find zabbix-age

Jira (PUP-1785) Services without any init script on Freebsd result in error

[Dolf Schimmel (JIRA)]

Title: Message Title










 

 Dolf Schimmel updated an issue











 






 Puppet /  PUP-1785



  Services without any init script on Freebsd result in error 










Change By:

 Dolf Schimmel









 I'm trying to stop a service in case it's still running. The package the service belongs to may have already been removed, so we cannot rely on the init script.This is my manifest:{ quote code }  service { 'zabbix-agent':audit  => all,status => "test `${::ps} | grep zabbix-agent | wc -l` == 0",stop   => "kill `${::ps} | grep zabbix-agent | awk '{print $2}'`",start  => '/bin/false',hasstatus  => false,hasrestart => false,  }{ quote code }When running `puppet agent` with --debug flag, the following relevant output is shown:{quote}Debug: Executing 'test `ps auxwww | grep zabbix-agent | wc -l` == 0'Debug: Service[zabbix-agent](provider=freebsd): Could not find zabbix-agent in /etc/rc.dDebug: Service[zabbix-agent](provider=freebsd): Could not find zabbix-agent in /usr/local/etc/rc.dDebug: Service[zabbix-agent](provider=freebsd): Could not find zabbix-agent.sh in /etc/rc.dDebug: Service[zabbix-agent](provider=freebsd): Could not find zabbix-agent.sh in /usr/local/etc/rc.dError: /Stage[main]/Profile::Removelegacylater/Service[zabbix-agent]: Could not evaluate: Could not find init script for 'zabbix-agent'{quote}Expected behavior: I would expect Puppet to simply use my supplied stop or start commands to manage this resource.Actual behavior: Puppet Looks for an init script and bails out the moment it cannot find any.What's furthermore interesting is that even with `noop => true` this error is observed.












   

 Add Comment











 










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




 














-- 
You receive

Jira (PUP-1106) Require and Subscribe on the same refreshonly exec doesnt work

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-1106



  Require and Subscribe on the same refreshonly exec doesnt work 










Change By:

 Andrew Parker




Component/s:

 DSL




Component/s:

 Catalog Application












   

 Add Comment











 










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




 














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

Jira (PUP-1414) In Passenger, statements in a module outside class survive past node and affect other nodes

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-1414



  In Passenger, statements in a module outside class survive past node and affect other nodes 










I think this is occurring because of the coding being loaded into known_resource_types and being available to run, which then happens regardless of whether the file that it came from should have been evaluated.
We should fix this in the new evaluator in some manner.












   

 Add Comment











 










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




 














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

Jira (PUP-1422) Inconsistent scope behaviour to_hash vs. lookupvar

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-1422



  Inconsistent scope behaviour to_hash vs. lookupvar 










Change By:

 Andrew Parker









 Which behavior is correct?Example:  {noformat} # puppet apply --modulepath ~/tmp/scopetest init.ppNotice: Scope(Class[Smurvice]): classscope to_hash  : testNotice: Scope(Class[Smurvice]): classscope lookupvar:Notice: Scope(Class[Smurvice]): classscope pupppet  :Notice: Scope(Class[Smurvice]): nodescope to_hash   : testNotice: Scope(Class[Smurvice]): nodescope lookupvar : testNotice: Scope(Class[Smurvice]): nodescope puppet: testNotice: Compiled catalog for eriks-mac-mini.local in environment production in 0.06 secondsNotice: Finished catalog run in 0.08 seconds {noformat}  {noformat} init.pp:node default {init.pp:  $nodescope="test"init.pp:  class { smurfer: }init.pp:}smurfer/manifests/init.pp:class smurfer {smurfer/manifests/init.pp:  $classscope = "test"smurfer/manifests/init.pp:  class { 'smurvice': }smurfer/manifests/init.pp:}smurvice/manifests/init.pp:class smurvice {smurvice/manifests/init.pp:  $classscope_to_hash = inline_template('<%= scope.to_hash["classscope"] %>')smurvice/manifests/init.pp:  $classscope_lookupvar = inline_template('<%= scope.lookupvar("classscope") %>')smurvice/manifests/init.pp:  $classscope_puppet = $classscopesmurvice/manifests/init.pp:  notice("classscope to_hash  : ${classscope_to_hash}")smurvice/manifests/init.pp:  notice("classscope lookupvar: ${classscope_lookupvar}")smurvice/manifests/init.pp:  notice("classscope pupppet  : ${classscope_puppet}")smurvice/manifests/init.pp:  $nodescope_to_hash = inline_template('<%= scope.to_hash["nodescope"] %>')smurvice/manifests/init.pp:  $nodescope_lookupvar = inline_template('<%= scope.lookupvar("nodescope") %>')smurvice/manifests/init.pp:  $nodescope_puppet = $nodescopesmurvice/manifests/init.pp:  notice("nodescope to_hash   : ${nodescope_to_hash}")smurvice/manifests/init.pp:  notice("nodescope lookupvar : ${nodescope_lookupvar}")smurvice/manifests/init.pp:  notice("nodescope puppet: ${nodescope_puppet}")smurvice/manifests/init.pp:} {noformat}












   

 Add Comment











 










 

Jira (PUP-1283) Update win32-service gem

[Michelle Johansen (JIRA)]

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1283



  Update win32-service gem 










Change By:

 Michelle Johansen




Component/s:

 PE












   

 Add Comment











 










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




 














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

Jira (PUP-1283) Update win32-service gem

[Michelle Johansen (JIRA)]

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1283



  Update win32-service gem 










Change By:

 Michelle Johansen




Fix Version/s:

 3.6.0












   

 Add Comment











 










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




 














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

Jira (PUP-1546) Improve validation error message for hash/resource (future parser)

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: Improve validation error message for hash/resource (future parser) 










Henrik Lindberg, I think the suggested fixes for PUP-979 will affect this. Maybe even end up making the error message better?












   

 Add Comment











 













 Puppet /  PUP-1546



  Improve validation error message for hash/resource (future parser) 







 Given input such as:  {code}  clasf bar {  }  {code}  An error is raised with the text: "All resource specifications require names...". This is correct since the program is interpreted as a call to "clasf" followed by a resource of type "bar".   This is however hard to understand - the user thinks this is a class (but there is a typo).  A simple fix is...















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




 














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

Jira (PUP-1283) Update win32-service gem

[Michelle Johansen (JIRA)]

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1283



  Update win32-service gem 










Change By:

 Michelle Johansen




Component/s:

 PE












   

 Add Comment











 










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




 














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

Jira (PUP-1283) Update win32-service gem

[Michelle Johansen (JIRA)]

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1283



  Update win32-service gem 










Change By:

 Michelle Johansen




Fix Version/s:

 3.6.0












   

 Add Comment











 










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




 














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

Jira (HI-221) Cannot concatenate arrays when interpolating

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo updated an issue











 






 Hiera /  HI-221



  Cannot concatenate arrays when interpolating 










Change By:

 Adrien Thebo









 If I have a YAML data file with the following content : {code} ---myarray: - 1 - 2 - 3myrefarray: "%{hiera('myarray')}" {code}   And an other one with : {code} ---myrefarray:  - 4  - 5  - 6 {code}   The command "hiera -d -c hiera.yaml myrefarray --array" returns :["[1, 2, 3]", 4, 5, 6]I would expect Hiera to return :[1, 2, 3, 4, 5, 6]Is this behaviour expected ? 












   

 Add Comment











 










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




 














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

Jira (PUP-1397) hyphen in class name messes with qualified variables

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: hyphen in class name messes with qualified variables 










We won't be allowing hyphens in names, but they will be allowed in bare words. PUP-1576 is the work to add that support back into the future parser.












   

 Add Comment











 













 Puppet /  PUP-1397



  hyphen in class name messes with qualified variables 







 $module::class-name::variable   This tricks puppet. I suppose it thinks the "-" is a minus...















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




 














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

Jira (PUP-493) Add Issue based error handling to evaluator

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-493



  Add Issue based error handling to evaluator 










Change By:

 Andrew Parker




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/groups/opt_out.

Jira (HI-221) Cannot concatenate arrays when interpolating

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Cannot concatenate arrays when interpolating 










Does the behavior described in https://tickets.puppetlabs.com/browse/HI-183 sound like this same issue to you?












   

 Add Comment











 













 Hiera /  HI-221



  Cannot concatenate arrays when interpolating 







 If I have a YAML data file with the following content :   {code}  ---  myarray:   - 1   - 2   - 3  myrefarray: "%{hiera('myarray')}"  {code}   And an other one with :   {code}  ---  myrefarray:    - 4    - 5    - 6  {code}   The command "hiera -d -c hiera.yaml myrefarray --array" returns :  ["[1, 2, 3]", 4, 5, 6]   I would expect Hiera to return :  [...















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




 














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

Jira (PUP-513) Validate type references at runtime.

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-513



  Validate type references at runtime. 










Change By:

 Andrew Parker




Story Points:

 3












   

 Add Comment











 










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




 














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

Jira (PUP-592) :rvalue functions require argument handling

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-592



  :rvalue functions require argument handling 










Change By:

 Andrew Parker




Story Points:

 1












   

 Add Comment











 










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




 














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

Jira (PDB-479) PR (123): Fix is_pe declaration so it works without is_pe - kbarber

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-479



  PR (123): Fix is_pe declaration so it works without is_pe - kbarber 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 27/Feb/14 9:05 AM




Labels:


 github module




Priority:

  Normal




Reporter:

 gepetto-bot










Fix is_pe declaration so it works without is_pe


Author: Ken Barber 


Company: Puppetlabs Inc.


Github ID: kbarber


Pull Request 123 Discussion


Pull Request 123 File Diff


Pull Request Description

Signed-off-by: Ken Barber 

(webhooks-id: bdc282f0b43fc8bd676e77e34c546d83)

Jira (PUP-509) Specify the Puppet Language query mechanism

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-509



  Specify the Puppet Language query mechanism 










Change By:

 Andrew Parker




Story Points:

 3












   

 Add Comment











 










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




 














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

Jira (PUP-1220) dynamic variable lookup works in templates

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-1220



  dynamic variable lookup works in templates 










Change By:

 Andrew Parker




Story Points:

 1












   

 Add Comment











 










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




 














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

Jira (PUP-1780) Issue warning when undefined variables are accessed

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-1780



  Issue warning when undefined variables are accessed 










Change By:

 Andrew Parker




Story Points:

 1












   

 Add Comment











 










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




 














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

Jira (PDB-401) PR (826): Port to trapperkeeper 0.3.0 - cprice404

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (826): Port to trapperkeeper 0.3.0 - cprice404 










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












   

 Add Comment











 













 PuppetDB /  PDB-401



  PR (826): Port to trapperkeeper 0.3.0 - cprice404 







 h2. Port to trapperkeeper 0.3.0   * Author: Chris Price <>  * Company:   * Github ID: [cprice404|https://github.com/cprice404]  * [Pull Request 826 Discussion|https://github.com/puppetlabs/puppetdb/pull/826]  * [Pull Request 826 File Diff|https://github.com/puppetlabs/puppetdb/pull/826/files]  h2. Pull Request Description   This commit updates PuppetD...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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/puppe

Jira (PUP-1781) PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo 










adrienthebo commented:
The 1.8.7 job is failing with a weird error that looks spurious, I'm rerunning the job.












   

 Add Comment











 













 Puppet /  PUP-1781



  PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo 







 h2. Issue/master/pup 876 redhat 6 upstart   * Author: Adrien Thebo git...@somethingsinistral.net>  * Company: Puppet Labs  * Github ID: [adrienthebo|https://github.com/adrienthebo]  * [Pull Request 2392 Discussion|https://github.com/puppetlabs/puppet/pull/2392]  * [Pull Request 2392 File Diff|https://github.com/puppetlabs/puppet/pull/2392/files]  h2















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




 














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

Jira (PDB-401) PR (826): Port to trapperkeeper 0.3.0 - cprice404

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (826): Port to trapperkeeper 0.3.0 - cprice404 










Pull request Port to trapperkeeper 0.3.0 has been closed.












   

 Add Comment











 













 PuppetDB /  PDB-401



  PR (826): Port to trapperkeeper 0.3.0 - cprice404 







 h2. Port to trapperkeeper 0.3.0   * Author: Chris Price <>  * Company:   * Github ID: [cprice404|https://github.com/cprice404]  * [Pull Request 826 Discussion|https://github.com/puppetlabs/puppetdb/pull/826]  * [Pull Request 826 File Diff|https://github.com/puppetlabs/puppetdb/pull/826/files]  h2. Pull Request Description   This commit updates PuppetD...















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




 














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

Jira (PUP-1543) agent as nonroot: incorrect messaging when attempting to create unauthorized crons

[Michelle Johansen (JIRA)]

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1543



  agent as nonroot: incorrect messaging when attempting to create unauthorized crons 










Change By:

 Michelle Johansen




Component/s:

 PE












   

 Add Comment











 










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




 














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

Jira (FACT-352) cannot load such file -- win32/dir

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Facter /  FACT-352



  cannot load such file -- win32/dir 










Change By:

 Joshua Cooper




Assignee:

 Eric Sorenson Maurizio De Santis












   

 Add Comment











 










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




 














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

Jira (PUP-1543) agent as nonroot: incorrect messaging when attempting to create unauthorized crons

[Michelle Johansen (JIRA)]

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1543



  agent as nonroot: incorrect messaging when attempting to create unauthorized crons 










Change By:

 Michelle Johansen




Fix Version/s:

 3.6.0












   

 Add Comment











 










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




 














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

Jira (PUP-1786) Error with noop run when file has require and source that doesn't exist

[Steven Willis (JIRA)]

Title: Message Title










 

 Steven Willis moved an issue











 






 Puppet /  PUP-1786



  Error with noop run when file has require and source that doesn't exist 










Change By:

 Steven Willis




Component/s:

 puppet




Workflow:

 Forge Platform  Workflow




Key:

 MODULES PUP - 469 1786




Project:

 Forge Modules Puppet












   

 Add Comment











 










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




 














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

Jira (PUP-1786) Error with noop run when file has require and source that doesn't exist

[Steven Willis (JIRA)]

Title: Message Title










 

 Steven Willis commented on an issue











 






  Re: Error with noop run when file has require and source that doesn't exist 










I also just discovered the ability to move. I think I beat you to it.












   

 Add Comment











 













 Puppet /  PUP-1786



  Error with noop run when file has require and source that doesn't exist 







 The following manifest fails when run with --noop, but succeeds when run normally:   {noformat:title=t.pp}  file { '/tmp/foo-bar':    content => "Hello\n",  }   file { '/tmp/bar-foo':    source => "file:///tmp/foo-bar",    require => File['/tmp/foo-bar'],  }  {noformat}   {noformat}  $ rm -rf /tmp/foo-bar /tmp/bar-foo; puppet apply t.pp  Notice: Compi...















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




 














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

Jira (PUP-1786) Error with noop run when file has require and source that doesn't exist

[Ryan Coleman (JIRA)]

Title: Message Title










 

 Ryan Coleman commented on an issue











 






  Re: Error with noop run when file has require and source that doesn't exist 










Heh, you beat me to it. Cheers. 












   

 Add Comment











 













 Puppet /  PUP-1786



  Error with noop run when file has require and source that doesn't exist 







 The following manifest fails when run with --noop, but succeeds when run normally:   {noformat:title=t.pp}  file { '/tmp/foo-bar':    content => "Hello\n",  }   file { '/tmp/bar-foo':    source => "file:///tmp/foo-bar",    require => File['/tmp/foo-bar'],  }  {noformat}   {noformat}  $ rm -rf /tmp/foo-bar /tmp/bar-foo; puppet apply t.pp  Notice: Compi...















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




 














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

Jira (PUP-1786) Error with noop run when file has require and source that doesn't exist

[Ryan Coleman (JIRA)]

Title: Message Title










 

 Ryan Coleman updated an issue











 






 Puppet /  PUP-1786



  Error with noop run when file has require and source that doesn't exist 










Change By:

 Ryan Coleman




Assignee:

 Ryan Coleman












   

 Add Comment











 










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




 














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

Jira (FACT-352) cannot load such file -- win32/dir

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: cannot load such file -- win32/dir 










Facter on windows depends on several windows gems. In the 1.7 series, you need to install facter's dependencies manually. The complete list is:



  ffi: '1.9.0'
  sys-admin: '1.5.6'
  win32-api: '1.4.8'
  win32-dir: '~> 0.4.3'
  windows-api: '~> 0.4.2'
  windows-pr: '~> 1.2.2'
  win32console: '~> 1.3.2'



If you do gem list, I suspect that win32-dir will be missing.
When facter 2.x comes out, gem install facter on windows will automatically pull in the platform specific dependencies. See 

FACT-186
.












   

 Add Comment











 













 Facter /  FACT-352



  cannot load such file -- win32/dir 







 I have facter inside the Gemfile of a Rails app. I get this error:   {noformat}  cannot load such file -- win32/dir  C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb  :251:in `require'  C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/activesupport-3.2.17/lib/active_support/dependencies.rb  :251:in `block in require'...















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

Jira (PUP-592) :rvalue functions require argument handling

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: :rvalue functions require argument handling 










We are working on a new Function API - this is w.i.p and the example above would look something like this:



Puppet::Functions.create(:mastername) do
  def mastername
 Socket.gethostname.chomp
  end
end















   

 Add Comment











 













 Puppet /  PUP-592



  :rvalue functions require argument handling 







 What I mean by this is that the function has to handle the args parameter, even it doesn't do anything with it. This is not true for :statement functions.   This function blows up   {code}  # mastername.rb  require 'socket'   Puppet::Parser::Functions.newfunction(:mastername, :type => :rvalue ) do    Socket.gethostname.chomp  end  {code}   Output:   ...















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




 














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

Jira (PUP-1584) Puppet module tool should work with new directory environments

[Tony Vu (JIRA)]

Title: Message Title










 

 Tony Vu commented on an issue











 






  Re: Puppet module tool should work with new directory environments 










To clarify my expectation a bit; I would expect the --force option to look at all the directories that are a part of the environment direnv, not just the top level. For the directory environment direnv, the modulepath would have multiple locations:
modulepath = /etc/puppet/environments/direnv/modules:/etc/puppet/modules:/usr/share/puppet/modules
So maybe the issue more specifically is something like "--force doesn't look in all module path directories". 
At any rate, this behavior is consistent with a similar situation with the default directory locations, /etc/puppet/modules and /usr/share/puppet/modules, so the issue I am describing existed before this environment directory change and doesn't hold up this ticket from exiting functional review.
I'll bring this issue up with the forge team.












   

 Add Comment











 













 Puppet /  PUP-1584



  Puppet module tool should work with new directory environments 







 Given two environments, a legacy environment 'legacyenv' defined in puppet.conf and a 'direnv' directory in the established $environmentdir, `puppet module install --environment ` will respect the legacy environment but not the directory environment. This probably needs to be fixed for all the module functions, but I haven't tested everything yet.















 This message was sent by Atlassian JIRA (v6.1.

Jira (PUP-1584) Puppet module tool should work with new directory environments

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Puppet module tool should work with new directory environments 










I see what you are saying; the modulepath is not the target-dir and I think it's only looking in the target-dir (which ends up being the first element of modulepath). So that might be a clarification of the docs, or a change to the --force option.












   

 Add Comment











 













 Puppet /  PUP-1584



  Puppet module tool should work with new directory environments 







 Given two environments, a legacy environment 'legacyenv' defined in puppet.conf and a 'direnv' directory in the established $environmentdir, `puppet module install --environment ` will respect the legacy environment but not the directory environment. This probably needs to be fixed for all the module functions, but I haven't tested everything yet.















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




 














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

Jira (PUP-1781) PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo 










adrienthebo commented:
On the 1.8.7 specs:
``` rake aborted! Command failed with status (): [rspec spec...] /home/travis/build/puppetlabs/puppet/Rakefile:67 Tasks: TOP => spec (See full trace by running task with --trace) The command "bundle exec rake spec" exited with 1. Done. Your build exited with 1. ``` wtf?












   

 Add Comment











 













 Puppet /  PUP-1781



  PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo 







 h2. Issue/master/pup 876 redhat 6 upstart   * Author: Adrien Thebo git...@somethingsinistral.net>  * Company: Puppet Labs  * Github ID: [adrienthebo|https://github.com/adrienthebo]  * [Pull Request 2392 Discussion|https://github.com/puppetlabs/puppet/pull/2392]  * [Pull Request 2392 File Diff|https://github.com/puppetlabs/puppet/pull/2392/files]  h2















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




 




   

Jira (FACT-351) undefined method 'ipaddress' for Facter:Module

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo updated an issue











 






 Facter /  FACT-351



  undefined method 'ipaddress' for Facter:Module 










Change By:

 Adrien Thebo




Sprint:

 Week 2014-2-26 to 2014-3-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/groups/opt_out.

Jira (FACT-351) undefined method 'ipaddress' for Facter:Module

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: undefined method 'ipaddress' for Facter:Module 










Joshua Cooper I tried reproducing this on the Mac Mini that I have access to and I couldn't reproduce this, what version of Facter were you running? In addition I have https://github.com/adrienthebo/facter/tree/feature/facter-2/log-exceptions available, could you try that copy with `facter --trace` and see if you get a stacktrace back?












   

 Add Comment











 













 Facter /  FACT-351



  undefined method 'ipaddress' for Facter:Module 







 On facter-2, Darwin:   {code}  bundle exec facter  Could not retrieve fact='netmask', resolution='': undefined method `ipaddress' for Facter:Module  ...  {code}   I think this is due to some facts still using {{setcode}} without a block, but I may be confusing this with a different issue.















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




 














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

Jira (FACT-239) Expose different resolution types in DSL

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Expose different resolution types in DSL 










Adrien Thebo can you go through these review comments and make recommendations on fix vs document?












   

 Add Comment











 













 Facter /  FACT-239



  Expose different resolution types in DSL 







 Adding multiple resolution types to Facter means that the DSL will have to take this into account. The DSL needs to take the following into account:   Resolutions need to be able to declare their type upon creation. This should just be a simple matter of taking :type => :something when the resolution is initially created.   Resolutions may also need to...















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




 














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

Jira (FACT-351) undefined method 'ipaddress' for Facter:Module

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo updated an issue











 






 Facter /  FACT-351



  undefined method 'ipaddress' for Facter:Module 










Change By:

 Adrien Thebo




Fix Version/s:

 2.0












   

 Add Comment











 










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




 














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

Jira (PUP-577) Efforts not currently approved for a release

[Michelle Johansen (JIRA)]

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-577



  Efforts not currently approved for a release 










Change By:

 Michelle Johansen




Epic Name:

 PE 3. 3 X  requests












   

 Add Comment











 










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




 














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

Jira (PUP-1783) Create folder on Windows couldn't have permission properly.

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1783



  Create folder on Windows couldn't have permission properly. 










Change By:

 Joshua Cooper




Labels:

 windows












   

 Add Comment











 










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




 














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

Jira (PUP-1781) PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo 










peterhuene commented:
I saw this same thing on another PR, although that one passed on the first re-run and I didn't give it a second thought. We should keep an eye out for more.












   

 Add Comment











 













 Puppet /  PUP-1781



  PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo 







 h2. Issue/master/pup 876 redhat 6 upstart   * Author: Adrien Thebo git...@somethingsinistral.net>  * Company: Puppet Labs  * Github ID: [adrienthebo|https://github.com/adrienthebo]  * [Pull Request 2392 Discussion|https://github.com/puppetlabs/puppet/pull/2392]  * [Pull Request 2392 File Diff|https://github.com/puppetlabs/puppet/pull/2392/files]  h2















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




 














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

Jira (PUP-1781) PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo 










kylog commented:
And now it passed  travis gremlins.












   

 Add Comment











 













 Puppet /  PUP-1781



  PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo 







 h2. Issue/master/pup 876 redhat 6 upstart   * Author: Adrien Thebo git...@somethingsinistral.net>  * Company: Puppet Labs  * Github ID: [adrienthebo|https://github.com/adrienthebo]  * [Pull Request 2392 Discussion|https://github.com/puppetlabs/puppet/pull/2392]  * [Pull Request 2392 File Diff|https://github.com/puppetlabs/puppet/pull/2392/files]  h2















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




 














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

Jira (FACT-239) Expose different resolution types in DSL

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo assigned an issue to Adrien Thebo











 






 Facter /  FACT-239



  Expose different resolution types in DSL 










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/groups/opt_out.

Jira (PUP-1787) Data Types throughout the Puppet Language

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker created an issue











 






 Puppet /  PUP-1787



  Data Types throughout the Puppet Language 










Issue Type:

  Epic




Assignee:

 Andrew Parker




Components:


 DSL




Created:


 27/Feb/14 10:48 AM




Fix Versions:


 4.x




Priority:

  Normal




Reporter:

 Andrew Parker












   

 Add Comment











 










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




 

Jira (PUP-1788) The service type should be able to use a script's default runlevels

[Steven Willis (JIRA)]

Title: Message Title










 

 Steven Willis created an issue











 






 Puppet /  PUP-1788



  The service type should be able to use a script's default runlevels 










Issue Type:

  Improvement




Affects Versions:


 3.2.2




Assignee:


 Unassigned




Created:


 27/Feb/14 10:58 AM




Labels:


 service redhat init enable runlevel chkconfig




Priority:

  Normal




Reporter:

 Steven Willis










Right now, with the redhat provider (and possibly others) using enable => true on service runs chkconfig servicename on which sets the service to be on in runlevels 2-5, if not currently enabled. It doesn't check the header of the init script to find out what runlevels it should be on for.
Even though the comments in the code suggest that this is what's happening:


lib/puppet/provider/service/redhat.rb


36:  # Don't support them specifying runlevels; always use the runlevels
37:  # in the init scripts.
38:  def enable
39:  chkconfig(@resource[:name], :on)



In fact it's a little worse than that since chkconfig servicename exits w

Jira (PUP-744) Pool HTTPS connections

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-744



  Pool HTTPS connections 










Change By:

 Kylo Ginsberg




Story Points:

 2 8












   

 Add Comment











 










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




 














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

Jira (PUP-1676) Puppet config print respects legacy but not directory environments

[Tony Vu (JIRA)]

Title: Message Title










 

 Tony Vu commented on an issue











 






  Re: Puppet config print respects legacy but not directory environments 










This has been tested using the scenario described in the description of this issue. The environment directory is the first directory listed when running puppet agent --configprint --environment direnv.












   

 Add Comment











 













 Puppet /  PUP-1676



  Puppet config print respects legacy but not directory environments 







 Puppet config print and --configprint respect only legacy environments if specified.   For example:   {code}  jpartlow@percival:~/work/puppet$ cat ~/.puppet/puppet.conf  [legacy]  modulepath=/home/jpartlow/work/tmp/envs/legacy   jpartlow@percival:~/work/puppet$ tree ~/.puppet/environments/  /home/jpartlow/.puppet/environments/  └── direnv  └── mod...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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/

Jira (PUP-1789) A new catalog model and builder

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker created an issue











 






 Puppet /  PUP-1789



  A new catalog model and builder 










Issue Type:

  Epic




Assignee:

 Andrew Parker




Components:


 DSL




Created:


 27/Feb/14 11:18 AM




Fix Versions:


 4.0.0, 3.6.0




Priority:

  Normal




Reporter:

 Andrew Parker










Replace the Puppet::Parser::Compiler and related pieces with a new system for constructing catalogs. Model, Types, Validation, Resources, Parameters, Parameter Values, etc. The agent won't be directly exposed to the new catalog model. The catalog will be transformed into the existing catalog format for other users (puppetdb, rspec-puppet, the agent).
This work will be experimental in 3.6 and the actual catalog system in 4.












   

 Add Comment

Jira (FACT-239) Expose different resolution types in DSL

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Expose different resolution types in DSL 










I've added documentation for named resolutions and how they work at https://github.com/puppetlabs/pre-docs/blob/master/facter/facter-2.0.1/named-resolutions.md .
In short, here's the expected behavior for named resolutions:



Facter.add(:myfact) do
  setcode { "foo" }
end

Facter.add(:myfact) do
  setcode { "bar" }
end



This declares two anonymous resolutions, which can happily coexist. There's not a lot we can do to change this behavior since it's the only way to currently declare facts.



Facter.define_fact(:myfact) do
  define_resolution(:myres) do
setcode { "foo" }
  end
end



This declares a named simple resolution, which is all fine and dandy. However, following that with this:



Facter.define_fact(:myfact) do
  define_resolution(:myres) do
setcode { "bar" }
  end
end



Will emit a warning (https://github.com/puppetlabs/facter/blob/facter-2/lib/facter/util/resolution.rb#L70-L74) because reopening a simple resolution is pretty nonsensical.
Doing this:



Facter.define_fact(:myfact) do
  define_resolution(:myres, :type => :aggregate) do
# Will never be reached
  end
end



Will raise an error since :myres has already been defined and is a simple resolution, and it's not meaningful to reopen a resolution with a different type.












   

 Add Comment











 













   

Jira (PDB-479) PR (123): Fix is_pe declaration so it works without is_pe - kbarber

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-479



  PR (123): Fix is_pe declaration so it works without is_pe - kbarber 










Change By:

 Kenneth Barber




Component/s:

 Module




Story Points:

 1




Issue Type:

 Task Bug












   

 Add Comment











 










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




 














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

Jira (FACT-239) Expose different resolution types in DSL

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Expose different resolution types in DSL 










And now for more API stuff:



$ cat lib/facter/reopened_aggregate.rb
Facter.add("reopened_aggregate", :type => :aggregate) do
  setcode do
'one'
  end
end

Facter.add("reopened_aggregate", :type => :aggregate) do
  setcode do
'two'
  end
end
$ be facter reopened_aggregate
Unable to add resolve nil for fact reopened_aggregate: undefined method `setcode' for #
Unable to add resolve nil for fact reopened_aggregate: undefined method `setcode' for #



We could explicitly raise a NotImplementedError for setcode to explain what's going on here, do you expect this to be prevalent enough to add that in?



$ cat lib/facter/reopened_aggregate.rb
Facter.add("reopened_aggregate", :type => :aggregate) do
  chunk(:one) do
'one'
  end
  chunk(:two) do
'two'
  end
end
$ be facter reopened_aggregate
Could not retrieve fact='reopened_aggregate', resolution='': No aggregate block specified and could not deep merge all chunks, either specify an aggregate block or ensure that all chunks return deep mergable structures. (Original error: Cannot merge "one":String and "two":String)



I was hoping that the error message indicated that but it doesn't read very clearly, how would you like to see that worded?












   

 Add Comment











 













 Facter /  FACT-239



  Expose different resolution types in DSL 







 Adding multiple resolution types to Facter means that the DSL will have to take t

Jira (PUP-1583) Puppet agent doesn't start on server power on

[Steven Willis (JIRA)]

Title: Message Title










 

 Steven Willis commented on an issue











 






  Re: Puppet agent doesn't start on server power on 










This is probably due to your locale settings. Try running:


LC_ALL=C service puppet start



I bet LANG or one of the LC_* variables is set to xx_YY.UTF-8 (where xx is your language and YY is your country) in your environment, allowing non-ascii characters to be parsed in your puppet config. However, on boot, these variables are either unset, or set to C. So on parse, it only allows ascii characters.
We use puppet enterprise, and the init script checks for (and then sources) the file: /etc/sysconfig/pe-puppet, on your system it might be /etc/default/puppet or something like that. Figure out what environment variables need to be set to parse your conf file correctly, and export them into the environment in that file.












   

 Add Comment











 













 Puppet /  PUP-1583



  Puppet agent doesn't start on server power on 







 Puppet packages from official Puppet repo for Debian has a bug: if there is non-ASCII comments (!) in puppet.conf, such as   {noformat}  # Что-то там  {noformat}   then puppet agent willn't start on server power on with this error:   {quote}  Could not parse /etc/puppet/puppet.conf: invalid byte sequence in US-ASCII  {quote}   Manually service launche...















   

Jira (PUP-477) Implement Strict Numbers

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: Implement Strict Numbers 










We will implement a "strict mode" in puppet 4.x that disallows implicit coercions. At the same time we will introduce a warning mode that warns about coercions. The user will then have the option of deciding how strict the language should be. After that we can decide if the next iteration of the language semantics should be strict by default or not.












   

 Add Comment











 













 Puppet /  PUP-477



  Implement Strict Numbers 







 3x has hybrid string / number auto type conversion.  The experimental 4x evaluator also has this, but with currently fixed paradoxes in this handling. It continues to be a problem balancing between "being helpful" and "being correct and free of paradox".   It would be much cleaner to never automatically convert between numbers and strings (except possibl...















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




 














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

Jira (FACT-239) Expose different resolution types in DSL

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Expose different resolution types in DSL 










For the last example I think there was an issue with the hash object not having a key/value pair:



└> cat lib/facter/mismatch.rb 
Facter.add("mismatch", :type => :aggregate) do
  chunk(:one) do
['one']
  end
  chunk(:two) do
{'two' => 'three'}
  end
end
└> bexec facter mismatch 
Could not retrieve fact='mismatch', resolution='': No aggregate block specified and could not deep merge all chunks, either specify an aggregate block or ensure that all chunks return deep mergable structures. (Original error: Cannot merge ["one"]:Array and {"two"=>"three"}:Hash)
















   

 Add Comment











 













 Facter /  FACT-239



  Expose different resolution types in DSL 







 Adding multiple resolution types to Facter means that the DSL will have to take this into account. The DSL needs to take the following into account:   Resolutions need to be able to declare their type upon creation. This should just be a simple matter of taking :type => :something when the resolution is initially created.   Resolutions may also need to...















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




 
   

Jira (FACT-239) Expose different resolution types in DSL

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Expose different resolution types in DSL 










So lastly I realize that the behavior of this is a little complex depending on if a resolution is named or anonymous, if it's simple or aggregate, and if we're reopening a resolution. I tried to make this a bit more simple and clear but I couldn't figure out much on how to have named resolutions and aggregate resolutions. Does anyone have suggestions on how this could be simplified?












   

 Add Comment











 













 Facter /  FACT-239



  Expose different resolution types in DSL 







 Adding multiple resolution types to Facter means that the DSL will have to take this into account. The DSL needs to take the following into account:   Resolutions need to be able to declare their type upon creation. This should just be a simple matter of taking :type => :something when the resolution is initially created.   Resolutions may also need to...















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




 














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

Jira (PDB-478) PR (873): Unpin beaker now that 1.7.0 is released - kbarber

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (873): Unpin beaker now that 1.7.0 is released - kbarber 










Pull request Unpin beaker now that 1.7.0 is released has been closed.












   

 Add Comment











 













 PuppetDB /  PDB-478



  PR (873): Unpin beaker now that 1.7.0 is released - kbarber 







 h2. Unpin beaker now that 1.7.0 is released   * Author: Ken Barber   * Company: Puppetlabs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 873 Discussion|https://github.com/puppetlabs/puppetdb/pull/873]  * [Pull Request 873 File Diff|https://github.com/puppetlabs/puppetdb/pull/873/files]  h2. Pull Request Description -...















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




 














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

Jira (PUP-1787) Data Types throughout the Puppet Language

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-1787



  Data Types throughout the Puppet Language 










Change By:

 Andrew Parker




Epic Name:

 Typed  and Strict  Puppet












   

 Add Comment











 










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




 














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

Jira (PUP-1790) Debugging, testing, quality metrics tools for the puppet language

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker created an issue











 






 Puppet /  PUP-1790



  Debugging, testing, quality metrics tools for the puppet language 










Issue Type:

  Epic




Assignee:


 Unassigned




Created:


 27/Feb/14 11:32 AM




Priority:

  Normal




Reporter:

 Andrew Parker












   

 Add Comment











 










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




 














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

Jira (PUP-1787) Data Types throughout the Puppet Language

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-1787



  Data Types throughout the Puppet Language 










Change By:

 Andrew Parker




Epic Name:

 Typed and Strict Maintainable  Puppet  Lang












   

 Add Comment











 










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




 














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

Jira (PUP-521) allow classes to be treated differently by documentation and classification tools

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-521



  allow classes to be treated differently by documentation and classification tools 










Change By:

 Andrew Parker




Fix Version/s:

 4.x












   

 Add Comment











 










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




 














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

Jira (PUP-1787) Data Types throughout the Puppet Language

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-1787



  Data Types throughout the Puppet Language 










Change By:

 Andrew Parker




Epic Name:

 Maintainable Puppet  Lang  Modules












   

 Add Comment











 










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




 














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

Jira (PUP-908) Refactor grammar validations to validation

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-908



  Refactor grammar validations to validation 










Change By:

 Andrew Parker




Fix Version/s:

 4.0.0




Fix Version/s:

 3.6.0












   

 Add Comment











 










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




 














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

Jira (PUP-30) Support Puppet Templates

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: Support Puppet Templates 










The functions will be epp(name, hash) and inline_epp(string, hash). The epp template doesn't have access to anything in the local scope. The template is evaluated in a new scope that is a child of the node scope and the local scope only contains bindings given in the hash.
In order to provide an easier migration path we will also create another function called visible_vars that returns a hash of all of the variables currently visible in the calling scope.
If an EPP specifies parameters, then any extra parameters that are given in the hash will result in an error.












   

 Add Comment











 













 Puppet /  PUP-30



  Support Puppet Templates 







 Add support for Puppet Templates. This is implemented and is based on the work in Puppet Heredoc. One feature (syntax checking) is not implemented, and is just like the support for Heredoc waiting for functionality to handle "plugins" (which is basically the same mechanism as "data in modules")  https://github.com/puppetlabs/puppet/pull/1660















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




 

Jira (PUP-30) Support Puppet Templates

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker assigned an issue to Henrik Lindberg











 






 Puppet /  PUP-30



  Support Puppet Templates 










Change By:

 Andrew Parker




Assignee:

 Andrew 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/groups/opt_out.

Jira (PUP-1784) Unable to remove Cron environment

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1784



  Unable to remove Cron environment 










Change By:

 Charlie Sharpsteen









 When I set an environment parameter for a Cron resource, it can't be removed afterwards. Defining an empty environment parameter is not allowed.For example: {code} cron { 'test':  command => '/bin/echo',} {code}   creates: {code} # Puppet Name: test* * * * * /bin/echo {code}   When I set an environment, it appears in the crontab: {cpde} Cron['test'] { environment => 'FOO=BAR' }# Puppet Name: testFOO=BAR* * * * * /bin/echo {code}   When I remove the environment parameter, the crontab is not affected at all, and setting an empty or undef environment either is not allowed or doesn't change the crontab.How do I remove the environment? 












   

 Add Comment











 










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




 














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

Jira (PUP-1784) Unable to remove Cron environment

[Reinier Schoof (JIRA)]

Title: Message Title










 

 Reinier Schoof updated an issue











 






 Puppet /  PUP-1784



  Unable to remove Cron environment 










Change By:

 Reinier Schoof









 When I set an environment parameter for a Cron resource, it can't be removed afterwards. Defining an empty environment parameter is not allowed.For example:{code}cron { 'test':  command => '/bin/echo',}{code}creates:{code}# Puppet Name: test* * * * * /bin/echo{code}When I set an environment, it appears in the crontab:{ cpde code }Cron['test'] { environment => 'FOO=BAR' }# Puppet Name: testFOO=BAR* * * * * /bin/echo{code}When I remove the environment parameter, the crontab is not affected at all, and setting an empty or undef environment either is not allowed or doesn't change the crontab.How do I remove the environment? 












   

 Add Comment











 










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




 














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

Jira (PUP-1784) Unable to remove Cron environment

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1784



  Unable to remove Cron environment 










Change By:

 Charlie Sharpsteen









 When I set an environment parameter for a Cron resource, it can't be removed afterwards. Defining an empty environment parameter is not allowed.For example:{code}cron { 'test':  command => '/bin/echo',}{code}creates:{code}# Puppet Name: test* * * * * /bin/echo{code}When I set an environment, it appears in the crontab:{ code cpde }Cron['test'] { environment => 'FOO=BAR' }# Puppet Name: testFOO=BAR* * * * * /bin/echo{code}When I remove the environment parameter, the crontab is not affected at all, and setting an empty or undef environment either is not allowed or doesn't change the crontab.How do I remove the environment? 












   

 Add Comment











 










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




 














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

Jira (PUP-1784) Unable to remove Cron environment

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1784



  Unable to remove Cron environment 










Change By:

 Charlie Sharpsteen









 When I set an environment parameter for a Cron resource, it can't be removed afterwards. Defining an empty environment parameter is not allowed.For example:{code}cron { 'test':  command => '/bin/echo',}{code}creates:{code}# Puppet Name: test* * * * * /bin/echo{code}When I set an environment, it appears in the crontab:{ cpde code }Cron['test'] { environment => 'FOO=BAR' }# Puppet Name: testFOO=BAR* * * * * /bin/echo{code}When I remove the environment parameter, the crontab is not affected at all, and setting an empty or undef environment either is not allowed or doesn't change the crontab.How do I remove the environment? 












   

 Add Comment











 










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




 














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

Jira (PUP-516) Improve 'node expression' match and inherit

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: Improve 'node _expression_' match and inherit 










Because of the number of issues presented by node inheritance I think we need to just remove it in puppet 4. This means that 3.6 should start issuing deprecation warnings whenever it encounters inheritance.
Since this is such a major change we need to make sure that there isn't something we are missing and have a discussion on puppet-dev.












   

 Add Comment











 













 Puppet /  PUP-516



  Improve 'node _expression_' match and inherit 







 A node _expression_ allows a Name or a Regexp, but also allows inheritence with Regexp. This is probelematic (as dicsussed in Redmine #7423.   Suggest that:  * node matching and node identity are two separate things  * node matching should not be handled as a special case of name, and instead be parsed as a '.'-separated list of bareword name segments, or ...















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




 














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

Jira (PUP-1665) PR - Puppet cert list behavior is suboptimal

[Peter Huene (JIRA)]

Title: Message Title










 

 Peter Huene commented on an issue











 






  Re: PR - Puppet cert list behavior is suboptimal 










For functional review:
This fix has no behavioral changes to 'puppet cert list' other than improving performance when there are a large number of signed certificates and doing 'puppet cert list' without any additional arguments.
We should test that 'puppet cert list', still works without arguments, with '-

all' or '
-signed', or when hosts are specified (both signed and unsigned).












   

 Add Comment











 













 Puppet /  PUP-1665



  PR - Puppet cert list behavior is suboptimal 







 In our production environment we have >8 certificates. Issuing {{puppet cert list}} on a large volume of signed certificates "hangs" even though viewing certs does not require traversing the signed repo.   {{puppet cert list}} should only scan all the signed certs when necessary (signed or all options).















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




 














-- 
You received 

Jira (PUP-516) Improve 'node expression' match and inherit

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: Improve 'node _expression_' match and inherit 










Once we get rid of node inheritance there isn't any need for nodes to have names since there isn't any need to refer to them. This removes all of the ambiguities and problems around nodes clashing with classes and other items.












   

 Add Comment











 













 Puppet /  PUP-516



  Improve 'node _expression_' match and inherit 







 A node _expression_ allows a Name or a Regexp, but also allows inheritence with Regexp. This is probelematic (as dicsussed in Redmine #7423.   Suggest that:  * node matching and node identity are two separate things  * node matching should not be handled as a special case of name, and instead be parsed as a '.'-separated list of bareword name segments, or ...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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/p

Jira (PUP-521) allow classes to be treated differently by documentation and classification tools

[Luke Kanies (JIRA)]

Title: Message Title










 

 Luke Kanies commented on an issue











 






  Re: allow classes to be treated differently by documentation and classification tools 










I was expecting to just add the keyword to the class declaration. E.g.:
private class foobar  { ... }
Rather than:
class foobar  { ... }
private foobar












   

 Add Comment











 













 Puppet /  PUP-521



  allow classes to be treated differently by documentation and classification tools 







 Modern module writing patterns call for classes to be broken down to components that either provide user-facing interfaces or manage discrete pieces of functionality for the larger module.   On an individual module level, this might lead to one or two classes that an author intends for others to use while the remaining four or five are just back-end cla...















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




 














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

Jira (PUP-521) allow classes to be treated differently by documentation and classification tools

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: allow classes to be treated differently by documentation and classification tools 










yes, that is how it will work in the language, i.e.



private class foobar { }















   

 Add Comment











 













 Puppet /  PUP-521



  allow classes to be treated differently by documentation and classification tools 







 Modern module writing patterns call for classes to be broken down to components that either provide user-facing interfaces or manage discrete pieces of functionality for the larger module.   On an individual module level, this might lead to one or two classes that an author intends for others to use while the remaining four or five are just back-end cla...















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




 














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

Jira (PUP-542) Provide access to all facts in a single structure

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Provide access to all facts in a single structure 










This works well when stringify_facts is enabled.
Given the following manifest:



$facts_type = inline_template("<%= scope['facts'].class %>")
$processor_fact_type = inline_template("<%= scope['facts']['processors'].class %>")

notice("facts data type is ${facts_type}")

notice("(looking inside facts hash) ipaddress is ${facts['ipaddress']}")

notice("(structured data in facts hash) processors type is ${processor_fact_type}")

notice("processors is ${facts['processors']}")

each($facts['processors']) |$value| {
  notice("next processor is ${value}")
}






└> bexec puppet apply --immutable_node_data --stringify_facts --parser future facts.pp --trace  
Notice: Scope(Class[main]): facts data type is Hash
Notice: Scope(Class[main]): (looking inside facts hash) ipaddress is 10.16.18.164
Notice: Scope(Class[main]): (structured data in facts hash) processors type is String
Notice: Scope(Class[main]): processors is ["Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz", "Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz", "Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz", "Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz"]
# Puppet then iterates over each character in the "processors" string, omitted here for brevity.



When fact stringifying is disabled we get this:



└> bexec puppet apply --immutable_node_data --no-stringify_facts --parser future facts.pp
Failed to load ZFS module stack.
Load the module manually by running 'insmod /zfs.ko' as root.
Failed to load ZFS module stack.
Load the module manually by running 'insmod /zfs.ko' as root.
Could not retrieve fact='zpool_version', resolution='': undefined method `captures' for nil:NilClass
Failed to load ZFS module stack.
Load the module manually by running 'insmod /zfs.ko' as root.
Failed to load ZFS module stack.
Load the module manually by running 'insmod /zfs.ko' as root.
Error: Unsupported data type: 'Array on node grey.somethingsinistral.net
Error: Unsupported data type: 'Array on node grey.somethingsinistral.net



It appears that the code at (https://github.com/puppetlabs/puppet/blob/3.4.3/lib/puppet/parser/scope.rb#L513-L525) doesn't take into account Numeric, Boolean, and Array values.
I added this patch to make my basic case work:



diff --git i/lib/puppet/parser/scope.rb w/lib/puppet/parser/scope.rb
index 8d557e4..8546dae 100644
--- i/lib/puppet/parser/scope.rb
+++ w/lib/puppet/parser/scope.rb
@@ -599,15 +599,18 @@ class Puppet::Parser::Scope
   #
   def deep_freeze(object)
 case object
+when Array
+  object.each {|v| deep_freeze(v) }
+  object.freeze
 when Hash
   object.each {|k, v| deep_freeze(k); deep_freeze(v) }
   object.freeze
-when NilClass
+when NilClass, Numeric, TrueClass, FalseClass
   # do nothing
 when String
   object.freeze
 else
-  raise 

Jira (PUP-1694) Provide packages for Rhel7

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Provide packages for Rhel7 










Melissa Stone just scrubbing jira and saw this. I assume this can be marked as resolved (or dup?).












   

 Add Comment











 













 Puppet /  PUP-1694



  Provide packages for Rhel7 







 We should provide packages for rhel7 for puppet, providing they pass a smoke test.















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




 














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

Jira (PUP-1523) Add support for 'held' ensure value to Yum provider by using yum-versionlock.

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1523



  Add support for 'held' ensure value to Yum provider by using yum-versionlock.  










Change By:

 Kylo Ginsberg




Fix Version/s:

 3.5.0












   

 Add Comment











 










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




 














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

Jira (HI-222) PR (182): Allow options to be passed to deep_merge - devin-c

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot created an issue











 






 Hiera /  HI-222



  PR (182): Allow options to be passed to deep_merge - devin-c 










Issue Type:

  Task




Assignee:

 Adrien Thebo




Components:


 Community




Created:


 27/Feb/14 1:36 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Allow options to be passed to deep_merge


Author: Devin Christensen <>


Company:


Github ID: devin-c


Pull Request 182 Discussion


Pull Request 182 File Diff


Pull Request Description

This enables the end user to customize the configuration of deep_merge 

Jira (FACT-349) Facter doesn't surface exception backtraces

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Facter doesn't surface exception backtraces 










Functional review should probably entail running `facter --trace` and see if any traces are logged. If nothing breaks, break a random fact and see if it produces a useful stacktrace.












   

 Add Comment











 













 Facter /  FACT-349



  Facter doesn't surface exception backtraces 







 When an error is raised/caught inside of Facter, the majority of rescue locations cannot display backtraces. This makes it challenging to debug the origin of crashes and failures inside of Facter. With the upcoming Facter 2.0 release we expect some breakage in custom facts and the like, and it would be very helpful for users to see these traces while hand...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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://group

Jira (PUP-1694) Provide packages for Rhel7

[Melissa Stone (JIRA)]

Title: Message Title










 

 Melissa Stone commented on an issue











 






  Re: Provide packages for Rhel7 










Umm, we technically haven't done this yet since we haven't shipped 3.5.0... but what ticket does/would it duplicate?












   

 Add Comment











 













 Puppet /  PUP-1694



  Provide packages for Rhel7 







 We should provide packages for rhel7 for puppet, providing they pass a smoke test.















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




 














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

Jira (PUP-542) Provide access to all facts in a single structure

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Provide access to all facts in a single structure 










Pull request for the above patch at https://github.com/puppetlabs/puppet/pull/2394












   

 Add Comment











 













 Puppet /  PUP-542



  Provide access to all facts in a single structure 







 The facts that are reported by the agent should be accessible via a top-scope {{$facts}} hash. The keys are the fact names and the values are the fact values.   If this variable is shadowed in a scope the evaluator should emit a warning.















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




 














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

Jira (PUP-1791) PR (2394): (maint) Allow arrays, bools, and numerics to be frozen - adrienthebo

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot created an issue











 






 Puppet /  PUP-1791



  PR (2394): (maint) Allow arrays, bools, and numerics to be frozen - adrienthebo 










Issue Type:

  Task




Assignee:

 Eric Sorenson




Components:


 Community




Created:


 27/Feb/14 1:46 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










(maint) Allow arrays, bools, and numerics to be frozen


Author: Adrien Thebo 


Company: Puppet Labs


Github ID: adrienthebo


Pull Request 2394 Discussion


Pull Request 2394 File Diff


Pull Request Description


  

Jira (PUP-509) Specify the Puppet Language query mechanism

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-509



  Specify the Puppet Language query mechanism 










Change By:

 Andrew Parker




Fix Version/s:

 3.6.0




Fix Version/s:

 4.x












   

 Add Comment











 










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




 














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