Jira (PDB-519) PR (892): Use the puppet agent configprint to get local certificate informations - aruetten

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (892): Use the puppet agent configprint to get local certificate informations - aruetten 










aruetten commented:
ack












   

 Add Comment











 













 PuppetDB /  PDB-519



  PR (892): Use the puppet agent configprint to get local certificate informations - aruetten 







 h2. Use the puppet agent configprint to get local certificate informations   * Author: Andreas Rütten <>  * Company:   * Github ID: [aruetten|https://github.com/aruetten]  * [Pull Request 892 Discussion|https://github.com/puppetlabs/puppetdb/pull/892]  * [Pull Request 892 File Diff|https://github.com/puppetlabs/puppetdb/pull/892/files]  h2. Pull Request D...















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




 














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

Jira (PDB-573) PR (126): Add strict_variables support when puppetdb is not on puppetmaster - mcanevet

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (126): Add strict_variables support when puppetdb is not on puppetmaster - mcanevet 










raphink commented:
![](http://andyarthur.org/wp-content/uploads/2014/02/YOmDuDV.jpg)












   

 Add Comment











 













 PuppetDB /  PDB-573



  PR (126): Add strict_variables support when puppetdb is not on puppetmaster - mcanevet 







 h2. Add strict_variables support when puppetdb is not on puppetmaster   * Author: Mickaël Canévet   * Company: camptocamp  * Github ID: [mcanevet|https://github.com/mcanevet]  * [Pull Request 126 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/126]  * [Pull Request 126 File Diff|https://github.com/puppetla...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this 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 m

Jira (PDB-567) Export with reports fails with java.io.IOException: This archives contains unclosed entries

[JIRA]

Title: Message Title










 

 Thomas Weißschuh commented on an issue











 






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










Kenneth Barber Several hosts before this one exported fine. It fails always at the same host (I don't know about the hosts after the broken host)
There are several bugs in apache-commons-compress related to the functionality used by puppetdb which are fixed in newer versions.
The dump imported just fine into our puppetdb version (1.6.3 + updated dependency)












   

 Add Comment











 













 PuppetDB /  PDB-567



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







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















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




 














-- 
You received this messa

Jira (PUP-2170) Puppet always recreates Nagios_hosts

[Jonathan Gazeley (JIRA)]

Title: Message Title










 

 Jonathan Gazeley commented on an issue











 






  Re: Puppet always recreates Nagios_hosts 










Yes, I have a block like this



  # Purge old configs
  resources { [
'nagios_host',
'nagios_service',
'nagios_hostextinfo',
'nagios_servicedependency',
'nagios_contact',
'nagios_contactgroup',
'nagios_command',
'nagios_servicegroup',
'nagios_hostgroup',
'nagios_hostdependency'
  ]:
purge  => true,
notify => Service['nagios'],
  }















   

 Add Comment











 













 Puppet /  PUP-2170



  Puppet always recreates Nagios_hosts 







 I've been using puppet with nagios for ages without any problems. Recently I looked into the puppet logs on my nagios server and it seems on every puppet run, puppet throws an error and recreates all the nagios_host objects (see below), even if none of them have been changed. I haven't changed my config so is there a new bug?   Thanks,  Jonathan   [jg44...















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




 






  

Jira (PUP-2170) Puppet always recreates Nagios_hosts

[Felix Frank (JIRA)]

Title: Message Title










 

 Felix Frank updated an issue











 






 Puppet /  PUP-2170



  Puppet always recreates Nagios_hosts 










Change By:

 Felix Frank




Assignee:

 Kylo Ginsberg Felix Frank












   

 Add Comment











 










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




 














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

Jira (PUP-2170) Puppet always recreates Nagios_hosts

[Felix Frank (JIRA)]

Title: Message Title










 

 Felix Frank commented on an issue











 






  Re: Puppet always recreates Nagios_hosts 










All right, awesome, thanks for the info. We may have regressed on the detection of existing nagios configuration entities. I'll try to get to the bottom of this so that we can perhaps fix this in a 3.4.4 release.












   

 Add Comment











 













 Puppet /  PUP-2170



  Puppet always recreates Nagios_hosts 







 I've been using puppet with nagios for ages without any problems. Recently I looked into the puppet logs on my nagios server and it seems on every puppet run, puppet throws an error and recreates all the nagios_host objects (see below), even if none of them have been changed. I haven't changed my config so is there a new bug?   Thanks,  Jonathan   [jg44...















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




 














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

Jira (PUP-2150) yumrepo removable URL properties cannot be set to 'absent' in Puppet 3.5.0.

[Alexey Ladin (JIRA)]

Title: Message Title










 

 Alexey Ladin commented on an issue











 






  Re: yumrepo removable URL properties cannot be set to 'absent' in Puppet 3.5.0. 










A "proxy" parameter may be set to '_none_'. My workaround in yumrepo.rb:



  if value != '_none_' && value != 'absent'
parsed = URI.parse(value)
fail("Must be a valid URL") unless ['file', 'http', 'https', 'ftp'].include?(parsed.scheme)
  end















   

 Add Comment











 













 Puppet /  PUP-2150



  yumrepo removable URL properties cannot be set to 'absent' in Puppet 3.5.0. 







 I am on CentOS 6.5 using open-source Puppet 3.5.0. We were previously using Puppet 3.4.3.   We are using the epel module from the forge, which specifies a value of 'absent' for all of the yumrepos it manages by default. This does not work in Puppet 3.5.0, causing this error:   {noformat}  Error: Parameter proxy failed on Yumrepo[epel-testing]: Must be a...















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




 














-- 
Yo

Jira (PUP-2170) Puppet always recreates Nagios_hosts

[Jonathan Gazeley (JIRA)]

Title: Message Title










 

 Jonathan Gazeley commented on an issue











 






  Re: Puppet always recreates Nagios_hosts 










Thanks for looking into this - I appreciate it. Let me know if you want me to gather more information etc. I can do some testing but we don't currently have a dev puppet environment and I'm reluctant to tinker too much with my production puppetmaster 












   

 Add Comment











 













 Puppet /  PUP-2170



  Puppet always recreates Nagios_hosts 







 I've been using puppet with nagios for ages without any problems. Recently I looked into the puppet logs on my nagios server and it seems on every puppet run, puppet throws an error and recreates all the nagios_host objects (see below), even if none of them have been changed. I haven't changed my config so is there a new bug?   Thanks,  Jonathan   [jg44...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this 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-1267) puppet help only show error message

[JIRA]

Title: Message Title










 

 Jonathan Araña Cruz commented on an issue











 






  Re: puppet help only show error message 










I'm experiencing this with puppet 3.5.0 on Debian 7 (wheezy). Here's a trace:


# puppet help --trace
Error: "--name=": already defined in puppet
/usr/lib/ruby/vendor_ruby/puppet/interface/option.rb:36:in `block in initialize'
/usr/lib/ruby/vendor_ruby/puppet/interface/option.rb:18:in `each'
/usr/lib/ruby/vendor_ruby/puppet/interface/option.rb:18:in `initialize'
/usr/lib/ruby/vendor_ruby/puppet/interface/option_builder.rb:17:in `new'
/usr/lib/ruby/vendor_ruby/puppet/interface/option_builder.rb:17:in `initialize'
/usr/lib/ruby/vendor_ruby/puppet/interface/option_builder.rb:12:in `new'
/usr/lib/ruby/vendor_ruby/puppet/interface/option_builder.rb:12:in `build'
/usr/lib/ruby/vendor_ruby/puppet/interface/action_builder.rb:93:in `option'
/var/lib/puppet/lib/puppet/face/dashboard.rb:102:in `block (2 levels) in '
/usr/lib/ruby/vendor_ruby/puppet/interface/action_builder.rb:146:in `instance_eval'
/usr/lib/ruby/vendor_ruby/puppet/interface/action_builder.rb:146:in `initialize'
/usr/lib/ruby/vendor_ruby/puppet/interface/action_builder.rb:17:in `new'
/usr/lib/ruby/vendor_ruby/puppet/interface/action_builder.rb:17:in `build'
/usr/lib/ruby/vendor_ruby/puppet/interface/action_manager.rb:22:in `action'
/var/lib/puppet/lib/puppet/face/dashboard.rb:100:in `block in '
/usr/lib/ruby/vendor_ruby/puppet/interface.rb:75:in `instance_eval'
/usr/lib/ruby/vendor_ruby/puppet/interface.rb:75:in `define'
/var/lib/puppet/lib/puppet/face/dashboard.rb:4:in `'
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
/usr/lib/ruby/vendor_ruby/puppet/interface/face_collection.rb:100:in `safely_require'
/usr/lib/ruby/vendor_ruby/puppet/interface/face_collection.rb:56:in `load_face'
/usr/lib/ruby/vendor_ruby/puppet/interface/face_collection.rb:17:in `[]'
/usr/lib/ruby/vendor_ruby/puppet/interface.rb:102:in `[]'
/usr/lib/ruby/vendor_ruby/puppet/face/help.rb:142:in `block in all_application_summaries'
/usr/lib/ruby/vendor_ruby/puppet/face/help.rb:137:in `each'
/usr/lib/ruby/vendor_ruby/puppet/face/help.rb:137:in `inject'
/usr/lib/ruby/vendor_ruby/puppet/face/help.rb:137:in `all_application_summaries'
/usr/lib/ruby/vendor_ruby/puppet/face/help/global.erb:6:in `block (3 levels) in '
/usr/lib/ruby/1.9.1/erb.rb:838:in `eval'
/usr/lib/ruby/1.9.1/erb.rb:838:in `result'
/usr/lib/ruby/vendor_ruby/puppet/face/help.rb:64:in `block (3 levels) in '
/usr/lib/ruby/vendor_ruby/puppet/interface/action.rb+eval[wrapper]:242:in `help'
/usr/lib/ruby/vendor_ruby/puppet/application/face_base.rb:229:in `main'
/usr/lib/ruby/vendor_ruby/puppet/application.rb:381:in `run_command'
/usr/lib/ruby/vendor_ruby/puppet/application.rb:372:in `block (3 levels) in run'
/usr/lib/ruby/vendor_ruby/puppet/application.rb:479:in `plugin_hook'
/usr/lib/ruby/vendor_ruby/puppet/application.rb:372:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/puppet/util.rb:479:in `exit_on_fail'
/usr/lib/ruby/vendor_ruby/puppet/application.rb:372:in `block in run'
/usr/lib/ruby/vendor_ruby/puppet/context.rb:51:in `override'
/usr/lib/ruby/vendor_ruby/puppet.rb:224:in `override'
/usr/lib/ruby/vendor_ruby/puppet/application.rb:362:in `run'
/usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:137:in `run'
/usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:91:in `execute'
/usr/bin/puppet:4:in `'
Error: Try 'puppet help help help' for usage

Jira (PUP-1267) puppet help only show error message

[Frederik Wagner (JIRA)]

Title: Message Title










 

 Frederik Wagner commented on an issue











 






  Re: puppet help only show error message 










Could it be that you have the dashboard face from the forge module "puppetlabs/dashboard " installed?
I experienced this kind of error with exactly this face - it redefines parameters already defined. Since some puppet version (don't ask me exactly) the redefinition of puppet standard parameters in faces is not allowed anymore.












   

 Add Comment











 













 Puppet /  PUP-1267



  puppet help only show error message 







 All puppet agents i have updated from 3.3.0 to 3.3.1 show on "puppet help" only the following error message:   Error: "--name=": already defined in puppet  Error: Try 'puppet help help help' for usage   The same error is shown with all "puppet man xyz" commands, but "puppet help xyz" seems to work with all commands.















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




 














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

Jira (PDB-563) puppet nodes status -- SSL problems

[JIRA]

Title: Message Title










 

 Andreas Rütten commented on an issue











 






  Re: puppet nodes status -- SSL problems 










Strange things are happened here...
For what ever reasons it's now working here without a given certname option



# puppet node status puppet-test01.domain.net 
puppet-test01.domain.net
Currently active
Last catalog: 2014-04-09T10:13:05.616Z
Last facts: 2014-04-09T10:13:04.372Z



Although /etc/puppet/puppet.conf is still the same as I wrote in the description.
We had some software updates but I don't think that they changed it:


libyaml


python-magic


libssl


openssl


So all I can say is: Works for me now.












   

 Add Comment











 













 PuppetDB /  PDB-563



  puppet nodes status -- SSL problems 







 We are getting a SSL error while calling  {code}  # puppet node status puppetdb-test02.domain.net  Error: Could not retrieve status for puppetdb-test02.domain.net: SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read finished A  {code}   In the puppetdb 

Jira (PUP-2156) file provider silent behaviour change for "mode"

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: file provider silent behaviour change for "mode" 










I think issuing a deprecation warning for 3.x when the mode is not a string and only accepting a string in puppet 4 is a good approach. It removes all of the ambiguity of what number to use to get the desired permissions.












   

 Add Comment











 













 Puppet /  PUP-2156



  file provider silent behaviour change for "mode" 







 The type reference for file in Puppet 0.25.5 said:   {noformat}  file { '/some/dir':    mode => 644,    recurse => true,  }  {noformat}   Ref: http://docs.puppetlabs.com/references/0.25.5/type.html#file   I believe that there are many Puppet manifests out there that still writes file mode as 3-digit numbers and expect them to be interpreted as octal.  ...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this 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-1295) Yum provider "purge" target runs irrespective of package installation status

[Mike Reznik (JIRA)]

Title: Message Title










 

 Mike Reznik commented on an issue











 






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










Still seeing this issue, Puppet 3.3.2, CentOS 6.3, Ruby 1.8.7












   

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

Jira (PUP-2150) yumrepo removable URL properties cannot be set to 'absent' in Puppet 3.5.0.

[Steven Merrill (JIRA)]

Title: Message Title










 

 Steven Merrill commented on an issue











 






  Re: yumrepo removable URL properties cannot be set to 'absent' in Puppet 3.5.0. 










Alexey Ladin, where are you seeing that none is a valid value? The official documentation (http://docs.puppetlabs.com/references/latest/type.html#yumrepo-attribute-proxy) doesn't mention "none" but it does mention "absent" as being valid.












   

 Add Comment











 













 Puppet /  PUP-2150



  yumrepo removable URL properties cannot be set to 'absent' in Puppet 3.5.0. 







 I am on CentOS 6.5 using open-source Puppet 3.5.0. We were previously using Puppet 3.4.3.   We are using the epel module from the forge, which specifies a value of 'absent' for all of the yumrepos it manages by default. This does not work in Puppet 3.5.0, causing this error:   {noformat}  Error: Parameter proxy failed on Yumrepo[epel-testing]: Must be a...















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




 














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

Jira (PUP-2188) Debian client looking for init script even when it shouldn't be there.

[redmine.exporter (JIRA)]

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-2188



  Debian client looking for init script even when it shouldn't be there. 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 09/Apr/14 5:34 AM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










I was working on our internal time module. I'm attaching a very generic version of it.
Basically when the class is set 'ensure => absent' it ensures that the package is gone and the service is stopped and disabled. My service requires the package, so in theory it shouldn't run the service resource if the package is absent. But every run on a debian system it throws the following error:
Error: /Stage[main]/Basictime/Service[ntp]: Could not evaluate: Could not find init script for 'ntp'
Also attaching full output.
Testing with 2.7.18 from debian's squeeze testing, 2.7.19 and 3.0.1 from apt.puppetlabs.
This part works fine on CentOS (I have a different issue on that side)












   

 Add Comment
 

Jira (PUP-2188) Debian client looking for init script even when it shouldn't be there.

[JIRA]

Title: Message Title










 

 Aloïs T updated an issue











 






 Puppet /  PUP-2188



  Debian client looking for init script even when it shouldn't be there. 










Change By:

 Aloïs T




Component/s:

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

Jira (PUP-2172) Add exceptions to http_proxy_{port,host}

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker updated an issue











 






 Puppet /  PUP-2172



  Add exceptions to http_proxy_{port,host} 










Change By:

 Andy Parker




Affects Version/s:

 3.5.0




Affects Version/s:

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

Jira (PUP-2172) Add exceptions to http_proxy_{port,host}

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Add exceptions to http_proxy_{port,host} 










I think adding a configurable list of excludes makes sense. There are a couple things to keep in mind:


The proxy exclusion needs to be reevaluated whenever a redirect is followed (I think this should trivially happen from the existing code)


As Josh points out, we aren't consistent everywhere. We should do a check of the code and make sure everything is consistently making HTTP requests


Right now some parts respect the http_proxy (or HTTP_PROXY) environment variable, but not everything. We need to combine those code paths so that everything respects the same proxy settings in the same way.














   

 Add Comment











 













 Puppet /  PUP-2172



  Add exceptions to http_proxy_{port,host} 







 We had a PE site which had set the http_proxy_\{port,host\} settings for PMT usage, which had the unintended consequence that all puppet master http connections went through the proxy, including those to the dashboard for node lookups. When something (not yet identified) changed in the network/proxy configuration, these lookups failed causing all agent ru...

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

[Tom Riley (JIRA)]

Title: Message Title










 

 Tom Riley commented on an issue











 






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










The Gem used (win32-taskscheduler) doesn't support minutes/hours. This would have to be addressed or an alternative gem found before work can commence. Feature Request raised against Gem https://github.com/djberg96/win32-taskscheduler/issues/6.












   

 Add Comment











 













 Puppet /  PUP-1291



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







 As stated in the Puppet documentation (http://docs.puppetlabs.com/windows/writing.html#scheduledtaskscheduledtask), the "scheduled_task" resource type does not support repetition modes such as "every X minutes".   It is a pity, because such tasks are very commonly used in Windows servers (and maybe less on Windows clients), making "scheduled_task" not s...















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




 














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

Jira (PUP-2184) Removing ACEs should have optional elements with identity

[Rob Reynolds (JIRA)]

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-2184



  Removing ACEs should have optional elements with identity 










Change By:

 Rob Reynolds




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

Jira (PUP-2184) Removing ACEs should have optional elements with identity

[Rob Reynolds (JIRA)]

Title: Message Title










 

 Rob Reynolds updated an issue











 






 Puppet /  PUP-2184



  Removing ACEs should have optional elements with identity 










Change By:

 Rob Reynolds




Fix Version/s:

 M












   

 Add Comment











 










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




 














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

Jira (PDB-573) PR (126): Add strict_variables support when puppetdb is not on puppetmaster - mcanevet

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (126): Add strict_variables support when puppetdb is not on puppetmaster - mcanevet 










mcanevet commented:
@kbarber I added `env: PUPPET_GEM_VERSION="~> 3.5.0.rc3" STRICT_VARIABLES="yes"`as allowed failure because the issue comes from `puppetlabs-postgresql`. Can you merge this ?












   

 Add Comment











 













 PuppetDB /  PDB-573



  PR (126): Add strict_variables support when puppetdb is not on puppetmaster - mcanevet 







 h2. Add strict_variables support when puppetdb is not on puppetmaster   * Author: Mickaël Canévet   * Company: camptocamp  * Github ID: [mcanevet|https://github.com/mcanevet]  * [Pull Request 126 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/126]  * [Pull Request 126 File Diff|https://github.com/puppetla...















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




 














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

Jira (PUP-1386) puppet agents complain about master not-being UTF-8

[Louis Mayorga (JIRA)]

Title: Message Title










 

 Louis Mayorga commented on an issue











 






  Re: puppet agents complain about master not-being UTF-8 










Where should I make the same change in PE 3.1.3?












   

 Add Comment











 













 Puppet /  PUP-1386



  puppet agents complain about master not-being UTF-8 







 I had this error after updating to 3.2.1 when I tried to fetch catalog from agents   Error: Could not retrieve catalog from remote server: Error 400 on SERVER: invalid byte sequence in US-ASCII   My config is Debian based, with packages installed from puppetlab repo. PuppetMaster is served through puppetmaster-passenger.  I managed to get it working bac...















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




 














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

Jira (PUP-2150) yumrepo removable URL properties cannot be set to 'absent' in Puppet 3.5.0.

[Alexey Ladin (JIRA)]

Title: Message Title










 

 Alexey Ladin commented on an issue











 






  Re: yumrepo removable URL properties cannot be set to 'absent' in Puppet 3.5.0. 










Steven Merrill, yes you are right. However, according to "man 5 yum.conf":

proxy url to the proxy server for this repository. Set to ’_none_’ to disable the global proxy setting for this repository. If this is unset it inherits it from the global setting

It is should be a not "absent" value ("absent" value just hide proxy option). If we have proxy setting in yum.conf and want to disable it in some repos, we should set proxy=_none_. It works fine in previous puppet 3.5. But not work anymore since 3.5 version.












   

 Add Comment











 













 Puppet /  PUP-2150



  yumrepo removable URL properties cannot be set to 'absent' in Puppet 3.5.0. 







 I am on CentOS 6.5 using open-source Puppet 3.5.0. We were previously using Puppet 3.4.3.   We are using the epel module from the forge, which specifies a value of 'absent' for all of the yumrepos it manages by default. This does not work in Puppet 3.5.0, causing this error:   {noformat}  Error: Parameter proxy failed on Yumrepo[epel-testing]: Must be a...















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




 

  

Jira (PUP-2158) Directory Environments breaks many classic Config File Environments

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Directory Environments breaks many classic Config File Environments 










Merged PR 2519 into stable in 152a94












   

 Add Comment











 













 Puppet /  PUP-2158



  Directory Environments breaks many classic Config File Environments 







 If you use the script in the classic blog post http://puppetlabs.com/blog/git-workflow-and-puppet-environments you have Config File Environments located at /etc/puppet/environments. Unfortunately, Puppet 3.5.0 will treat them as Directory Environments. If you have a modulepath such as this:   {noformat}    modulepath=/etc/puppet/environments/$environme...















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




 














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

Jira (PDB-567) Export with reports fails with java.io.IOException: This archives contains unclosed entries

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber commented on an issue











 






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










Thomas Weißschuh my critical question though, is does the dump format now contain directories where files should live due to the forward slash? Can you show me the output of tar -tzf of the dump file created so I can see this for myself?












   

 Add Comment











 













 PuppetDB /  PDB-567



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







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















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




 














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

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

[Tom Riley (JIRA)]

Title: Message Title










 

 Tom Riley commented on an issue











 






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










According to the Gem creator it can support minutes/hour intervals using :minutes_interval.












   

 Add Comment











 













 Puppet /  PUP-1291



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







 As stated in the Puppet documentation (http://docs.puppetlabs.com/windows/writing.html#scheduledtaskscheduledtask), the "scheduled_task" resource type does not support repetition modes such as "every X minutes".   It is a pity, because such tasks are very commonly used in Windows servers (and maybe less on Windows clients), making "scheduled_task" not s...















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




 














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

Jira (PUP-2156) file provider silent behaviour change for "mode"

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: file provider silent behaviour change for "mode" 










+1 on requiring that mode is a string in puppet 4, and deprecating when it's not in 3.x.
As to whether that string needs to start with a '0', I'm lukewarm on that, simply because I think people know it's octal and don't commonly provide the 0 when running chmod on the command-line, so I worry it would just be one of those naggy things. No strong feelings on that part though, I'm happy to be out-voted 












   

 Add Comment











 













 Puppet /  PUP-2156



  file provider silent behaviour change for "mode" 







 The type reference for file in Puppet 0.25.5 said:   {noformat}  file { '/some/dir':    mode => 644,    recurse => true,  }  {noformat}   Ref: http://docs.puppetlabs.com/references/0.25.5/type.html#file   I believe that there are many Puppet manifests out there that still writes file mode as 3-digit numbers and expect them to be interpreted as octal.  ...















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




 














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

Jira (PUP-2189) The CRL can get corrupted if two workers revoke certs at same time

[JIRA]

Title: Message Title










 

 Erik Dalén created an issue











 






 Puppet /  PUP-2189



  The CRL can get corrupted if two workers revoke certs at same time 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 09/Apr/14 7:33 AM




Priority:

  Normal




Reporter:

 Erik Dalén










The CRL file (and many other SSL related files) are missing locking, so concurrent access can lead to corruptions.












   

 Add Comment











 










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




 














-- 
You rece

Jira (PUP-2189) The CRL can get corrupted if two workers revoke certs at same time

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: The CRL can get corrupted if two workers revoke certs at same time 










The specific case here is if multiple CRL requests are made to the master (via the HTTP API). Because the writes are unprotected the CRL file ends up corrupted sometimes.












   

 Add Comment











 













 Puppet /  PUP-2189



  The CRL can get corrupted if two workers revoke certs at same time 







 The CRL file (and many other SSL related files) are missing locking, so concurrent access can lead to corruptions.















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




 














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

Jira (PUP-2189) The CRL can get corrupted if two workers revoke certs at same time

[JIRA]

Title: Message Title










 

 Erik Dalén commented on an issue











 






  Re: The CRL can get corrupted if two workers revoke certs at same time 










Also running "puppet cert revoke" from command line in parallell can cause it. Or one from command line or one from HTTP API etc.












   

 Add Comment











 













 Puppet /  PUP-2189



  The CRL can get corrupted if two workers revoke certs at same time 







 The CRL file (and many other SSL related files) are missing locking, so concurrent access can lead to corruptions.















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




 














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

Jira (PDB-554) EC2 instances are being left behind and not cleaned up

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 PuppetDB /  PDB-554



  EC2 instances are being left behind and not cleaned up 










Change By:

 Kenn Hussey




Sprint:

 20140326 to 20140409 , 20140409 to 20140423












   

 Add Comment











 










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




 














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

Jira (PDB-455) Update terminus querying to include environments

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 PuppetDB /  PDB-455



  Update terminus querying to include environments 










Change By:

 Kenn Hussey




Sprint:

 20140326 to 20140409 , 20140409 to 20140423












   

 Add Comment











 










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




 














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

Jira (PDB-518) export resources fails to export array parameters

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 PuppetDB /  PDB-518



  export resources fails to export array parameters 










Change By:

 Kenn Hussey




Sprint:

 20140312 to 20140326, 20140326 to 20140409 , 20140409 to 20140423












   

 Add Comment











 










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




 














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

Jira (PDB-454) Update existing query end-points to support environments

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 PuppetDB /  PDB-454



  Update existing query end-points to support environments 










Change By:

 Kenn Hussey




Sprint:

 20140326 to 20140409 , 20140409 to 20140423












   

 Add Comment











 










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




 














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

Jira (PDB-566) PR (125): Ensure db and db users created before validation - rickerc

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 PuppetDB /  PDB-566



  PR (125): Ensure db and db users created before validation - rickerc 










Change By:

 Kenn Hussey




Sprint:

 20140326 to 20140409 , 20140409 to 20140423












   

 Add Comment











 










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




 














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

Jira (PDB-567) Export with reports fails with java.io.IOException: This archives contains unclosed entries

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 PuppetDB /  PDB-567



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










Change By:

 Kenn Hussey




Sprint:

 20140326 to 20140409 , 20140409 to 20140423












   

 Add Comment











 










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




 














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

Jira (PDB-573) PR (126): Add strict_variables support when puppetdb is not on puppetmaster - mcanevet

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 PuppetDB /  PDB-573



  PR (126): Add strict_variables support when puppetdb is not on puppetmaster - mcanevet 










Change By:

 Kenn Hussey




Sprint:

 20140326 to 20140409 , 20140409 to 20140423












   

 Add Comment











 










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




 














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

Jira (PDB-533) PR (900): Add subqueries to events query endpoint - dalen

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 PuppetDB /  PDB-533



  PR (900): Add subqueries to events query endpoint - dalen 










Change By:

 Kenn Hussey




Sprint:

 20140326 to 20140409 , 20140409 to 20140423












   

 Add Comment











 










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




 














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

Jira (PUP-1927) Yum Package Provider Ignores Source Parameter

[Marcus Delap (JIRA)]

Title: Message Title










 

 Marcus Delap updated an issue











 






 Puppet /  PUP-1927



  Yum Package Provider Ignores Source Parameter 










Change By:

 Marcus Delap




Labels:

 wf001












   

 Add Comment











 










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




 














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

Jira (PUP-1450) [Windows] Copying file resources from non-NTFS volumes causes Invalid DACL errors

[Marcus Delap (JIRA)]

Title: Message Title










 

 Marcus Delap updated an issue











 






 Puppet /  PUP-1450



  [Windows] Copying file resources from non-NTFS volumes causes Invalid DACL errors 










Change By:

 Marcus Delap




Labels:

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

Jira (HI-46) Hiera should support alternate environments

[Marcus Delap (JIRA)]

Title: Message Title










 

 Marcus Delap updated an issue











 






 Hiera /  HI-46



  Hiera should support alternate environments 










Change By:

 Marcus Delap




Labels:

 customer redmine  wf001












   

 Add Comment











 










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




 














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

Jira (PUP-731) Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments

[Marcus Delap (JIRA)]

Title: Message Title










 

 Marcus Delap updated an issue











 






 Puppet /  PUP-731



  Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments 










Change By:

 Marcus Delap




Labels:

 customer redmine  wf001












   

 Add Comment











 










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




 














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

Jira (PDB-24) Support for Puppet Environments

[Marcus Delap (JIRA)]

Title: Message Title










 

 Marcus Delap updated an issue











 






 PuppetDB /  PDB-24



  Support for Puppet Environments 










Change By:

 Marcus Delap




Labels:

 PE_3.3 puppetdb  wf001












   

 Add Comment











 










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




 














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

Jira (PDB-574) /v4/catalogs/ returns a 500, should return a 404

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 PuppetDB /  PDB-574



  /v4/catalogs/ returns a 500, should return a 404 










Change By:

 Kenn Hussey




Story Points:

 1












   

 Add Comment











 










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




 














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

Jira (PDB-557) Add subqueries for /v4/environments end-point

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 PuppetDB /  PDB-557



  Add subqueries for /v4/environments end-point 










Change By:

 Kenn Hussey




Sprint:

 20140409 to 20140423












   

 Add Comment











 










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




 














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

Jira (PDB-456) New REST endpoints scoped by environment

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 PuppetDB /  PDB-456



  New REST endpoints scoped by environment 










Change By:

 Kenn Hussey




Sprint:

 20140409 to 20140423












   

 Add Comment











 










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




 














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

Jira (PDB-555) Add last_environment support to /v4/nodes for showing the last environment seen for each object type

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 PuppetDB /  PDB-555



  Add last_environment support to /v4/nodes for showing the last environment seen for each object type 










Change By:

 Kenn Hussey




Sprint:

 20140409 to 20140423












   

 Add Comment











 










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




 














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

Jira (PDB-559) Ensure community tooling is ready for environment awareness

[Kenn Hussey (JIRA)]

Title: Message Title










 

 Kenn Hussey updated an issue











 






 PuppetDB /  PDB-559



  Ensure community tooling is ready for environment awareness 










Change By:

 Kenn Hussey




Sprint:

 20140409 to 20140423












   

 Add Comment











 










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




 














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

Jira (PUP-2190) Accessing resource metaparameters fails in future evaluator

[JIRA]

Title: Message Title










 

 Erik Dalén created an issue











 






 Puppet /  PUP-2190



  Accessing resource metaparameters fails in future evaluator 










Issue Type:

  Bug




Affects Versions:


 3.5.0




Assignee:

 Henrik Lindberg




Created:


 09/Apr/14 9:05 AM




Priority:

  Normal




Reporter:

 Erik Dalén










Accessing regular parameters works fine, and when accessing unknown ones you get a decent error message. But when trying to access metaparameters you get a bad internal error



notify{foo:}
notify{Notify[foo][tag]:}



Gives:


Error: Evaluation Error: Error while evaluating a '[]' _expression_, undefined method `value' for nil:NilClass at line 1:33 on node 10.48.20.37.office.spotify.net
Error: Evaluation Error: Error while evaluating a '[]' _expression_, undefined method `value' for nil:NilClass at line 1:33 on node 10.48.20.37.office.spotify.net















   
  

Jira (PDB-457) Environments: Update import/export/anonymization to handle new wire formats

[Ryan Senior (JIRA)]

Title: Message Title










 

 Ryan Senior assigned an issue to Ryan Senior











 






 PuppetDB /  PDB-457



  Environments: Update import/export/anonymization to handle new wire formats 










Change By:

 Ryan Senior




Assignee:

 Ryan Senior












   

 Add Comment











 










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




 














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

Jira (HI-232) hiera should conflict/provide/replace ruby-hiera (from ubuntu)

[Matthaus Owens (JIRA)]

Title: Message Title










 

 Matthaus Owens updated an issue











 






 Hiera /  HI-232



  hiera should conflict/provide/replace ruby-hiera (from ubuntu) 










Change By:

 Matthaus Owens




Fix Version/s:

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

Jira (PDB-573) PR (126): Add strict_variables support when puppetdb is not on puppetmaster - mcanevet

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (126): Add strict_variables support when puppetdb is not on puppetmaster - mcanevet 










kbarber commented:
@mcanevet I'd rather not allow this to go in without fixing the upstream confirmed, otherwise no one will find the time to fix it correctly . Also - I'd rather this be a mandatory pass/fail if we can.
I've had @apenney merge in your change to postgresql, but I'm still seeing an error related to postgres when I re-run your tests. Can you take another look please? https://travis-ci.org/puppetlabs/puppetlabs-puppetdb/jobs/22608476












   

 Add Comment











 













 PuppetDB /  PDB-573



  PR (126): Add strict_variables support when puppetdb is not on puppetmaster - mcanevet 







 h2. Add strict_variables support when puppetdb is not on puppetmaster   * Author: Mickaël Canévet   * Company: camptocamp  * Github ID: [mcanevet|https://github.com/mcanevet]  * [Pull Request 126 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/126]  * [Pull Request 126 File Diff|https://github.com/puppetla...















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




 





   

Jira (PUP-2190) Accessing resource metaparameters fails in future evaluator

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-2190



  Accessing resource metaparameters fails in future evaluator 










Change By:

 Henrik Lindberg




Component/s:

 DSL












   

 Add Comment











 










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




 














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

Jira (PUP-2190) Accessing resource metaparameters fails in future evaluator

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-2190



  Accessing resource metaparameters fails in future evaluator 










Change By:

 Henrik Lindberg




Labels:

 future-parser












   

 Add Comment











 










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




 














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

Jira (PUP-2080) Support functions written in pp

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Support functions written in pp 










This was merged as part of Function API. It is on master at a04d9a740bdc3ef5134665f1ad6c1154a74adb32












   

 Add Comment











 













 Puppet /  PUP-2080



  Support functions written in pp 







 Add the ability to write functions in the puppet language.  Functions should be stored under ./functions relative to the root of a module.   Function names should support fully qualified names.















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




 














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

Jira (PUP-2026) Add a LambdaType to the type system

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Add a LambdaType to the type system 










Decided against using the name "Lambda" since the same type applies to Function - implemented it using the name Callable.
The Callable type is parameterized as a Tuple type, and supports an additional Callable at the end after size constraints to denote that the callable accepts a block. Thus a full Callable type for a function like foo(String $x, Integer $y) that accepts a block with a Scalar argument looks like this:



Callable[String, Integer, Callable[Scalar]]



That is, a Callable placed last means it is supported using the "pass lambda to function" syntax in the language.












   

 Add Comment











 













 Puppet /  PUP-2026



  Add a LambdaType to the type system 







 The type system lacks a type to describe a Puppet Lambda. This is needed when the type system is used to describe function type signatures.   Suggest that this type is called Lambda in the puppet language, and it is parameterized the same way a TupleType is parameterized (to allow it to describe required, optional, and variable number of arguments.















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

Jira (PUP-2027) Add support for Lambda in Function Call API

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-2027



  Add support for Lambda in Function Call API 










Change By:

 Henrik Lindberg




Sprint:

 Week 2014-4-09 to 2014-4-16












   

 Add Comment











 










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




 














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

Jira (PUP-2026) Add a LambdaType to the type system

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-2026



  Add a LambdaType to the type system 










Change By:

 Henrik Lindberg




Sprint:

 Week 2014-4-09 to 2014-4-16












   

 Add Comment











 










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




 














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

Jira (PUP-2191) Python php provider does not support minimum or maximum requirement specifiers

[Daniel Beckham (JIRA)]

Title: Message Title










 

 Daniel Beckham created an issue











 






 Puppet /  PUP-2191



  Python php provider does not support minimum or maximum requirement specifiers 










Issue Type:

  Bug




Affects Versions:


 3.5.0 RC, 3.4.3, 3.5.0




Assignee:

 Kylo Ginsberg




Components:


 Types and Providers




Created:


 09/Apr/14 11:17 AM




Priority:

  Normal




Reporter:

 Daniel Beckham










The Python php package provider does not support pip requirements specifiers other than a specific version. 
The issue seems to be missing quotes around the package and version in the command line args. See: line 85 in pip.rb
Examples of pip requirements specifiers:



pip install 'foo==1.0'
pip install 'foo>=1.0.0'
pip install 'foo>=1.0.0,<1.5.0'



PIP Install Example Docs Valid Specifiers in EBNF

Jira (FACT-455) Using Facter 2.0.1 with Puppet 3.4.2 gives me an error

[stack72 (JIRA)]

Title: Message Title










 

 stack72 created an issue











 






 Facter /  FACT-455



  Using Facter 2.0.1 with Puppet 3.4.2 gives me an error 










Issue Type:

  Bug




Assignee:

 Eric Sorenson




Created:


 09/Apr/14 3:19 PM




Priority:

  Normal




Reporter:

 stack72










I have just provisioned a new server with Puppet 3.4.2 and Facter 2.0.1
When running puppet agent -t, I get the following error
root@pp-logindexer-01:~# puppet agent -t Info: Retrieving pluginfacts Info: Retrieving plugin Error: Could not retrieve local facts: undefined method `puppetversion' for Facter:Module Error: Failed to apply catalog: Could not retrieve local facts: undefined method `puppetversion' for Facter:Module












   

 Add Comment











 










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


  

Jira (PUP-1987) ACLs - Deny ACL does not set inheritance properly

[Kurt Wall (JIRA)]

Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-1987



  ACLs - Deny ACL does not set inheritance properly 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall












   

 Add Comment











 










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




 














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

Jira (FACT-455) Using Facter 2.0.1 with Puppet 3.4.2 gives me an error

[Eric Sorenson (JIRA)]

Title: Message Title










 

 Eric Sorenson commented on an issue











 






  Re: Using Facter 2.0.1 with Puppet 3.4.2 gives me an error 










Hi Paul, this error is usually due to having conflicting versions of facter on the system; by chance is there one installed via system package (rpm) and one via gem, or some other combination? Something like find / -type d -name facter should (eventually) find them all...












   

 Add Comment











 













 Facter /  FACT-455



  Using Facter 2.0.1 with Puppet 3.4.2 gives me an error 







 I have just provisioned a new server with Puppet 3.4.2 and Facter 2.0.1   When running puppet agent -t, I get the following error   root@pp-logindexer-01:~# puppet agent -t  Info: Retrieving pluginfacts  Info: Retrieving plugin  Error: Could not retrieve local facts: undefined method `puppetversion' for Facter:Module  Error: Failed to apply catalog: Cou...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this 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@googlegr

Jira (FACT-455) Using Facter 2.0.1 with Puppet 3.4.2 gives me an error

[Eric Sorenson (JIRA)]

Title: Message Title










 

 Eric Sorenson updated an issue











 






 Facter /  FACT-455



  Using Facter 2.0.1 with Puppet 3.4.2 gives me an error 










Change By:

 Eric Sorenson




Assignee:

 Eric Sorenson stack72












   

 Add Comment











 










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




 














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

Jira (PUP-2096) support alternate http client classes in http_pool

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow assigned an issue to Joshua Partlow











 






 Puppet /  PUP-2096



  support alternate http client classes in http_pool 










Change By:

 Joshua Partlow




Assignee:

 Andy Parker Joshua Partlow












   

 Add Comment











 










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




 














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

Jira (PUP-2096) support alternate http client classes in http_pool

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: support alternate http client classes in http_pool 










Merged to master in a3757ef. Should go out in 3.6.0.












   

 Add Comment











 













 Puppet /  PUP-2096



  support alternate http client classes in http_pool 







 In order to support termini and other code that makes HTTPS requests when running in the JVM, we need to be able to provide alternate implementations of the HTTP client that is provided by http_pool.   This ticket is just a placeholder to represent the platform work necessary for PE-3076.















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




 














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

Jira (PUP-2209) FreeBSD Service definition not working with missing rc.conf definition

[Dolf Schimmel (JIRA)]

Title: Message Title










 

 Dolf Schimmel created an issue











 






 Puppet /  PUP-2209



  FreeBSD Service definition not working with missing rc.conf definition 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 09/Apr/14 4:18 PM




Environment:


Uname:

 FreeBSD hostname.example.org 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 {/quote}
Server runs version 3.4.3 Client runs version: 3.4.2




Labels:


 freebsd




Priority:

  Normal




Reporter:

 Dolf Schimmel










TL;DR When no service definition exists on FreeBSD in /etc/rc.conf.d will result in this error: 

Error: /Stage[main]/Dovecot/Service[dovecot]: Could not evaluate: undefined method `gsub' for nil:NilClass
 --
Consider the following code:


service { 'dovecot':
  ensure => running,
  name   => dovecot,
  enable => true,
}


The error happens

Jira (PUP-2209) FreeBSD Service definition not working with missing rc.conf definition

[Dolf Schimmel (JIRA)]

Title: Message Title










 

 Dolf Schimmel updated an issue











 






 Puppet /  PUP-2209



  FreeBSD Service definition not working with missing rc.conf definition 










Change By:

 Dolf Schimmel









 TL;DR When no service definition exists on FreeBSD in /etc/rc.conf.d will result in this error: {quote}Error: /Stage[main]/Dovecot/Service[dovecot]: Could not evaluate: undefined method `gsub' for nil:NilClass{quote}--Consider the following code:{code}service { 'dovecot':  ensure => running,  name   => dovecot,  enable => true,}{code}The error happens whenever the `enable` parameter/directive (what's the convention here?) is given. The outcome being the same, whether the value is either `false` or `true`.This resulted in the following error:{quote}Error: /Stage[main]/Dovecot/Service[dovecot]: Could not evaluate: undefined method `gsub' for nil:NilClass/usr/local/lib/ruby/site_ruby/1.9/puppet/provider/service/freebsd.rb:26:in `rcvar'/usr/local/lib/ruby/site_ruby/1.9/puppet/provider/service/freebsd.rb:52:in `rcvar_value'/usr/local/lib/ruby/site_ruby/1.9/puppet/provider/service/freebsd.rb:113:in `enabled?'/usr/local/lib/ruby/site_ruby/1.9/puppet/type/service.rb:56:in `retrieve'/usr/local/lib/ruby/site_ruby/1.9/puppet/type.rb:1045:in `block in retrieve'/usr/local/lib/ruby/site_ruby/1.9/puppet/type.rb:1040:in `each'/usr/local/lib/ruby/site_ruby/1.9/puppet/type.rb:1040:in `retrieve'/usr/local/lib/ruby/site_ruby/1.9/puppet/type.rb:1063:in `retrieve_resource'/usr/local/lib/ruby/site_ruby/1.9/puppet/transaction/resource_harness.rb:223:in `from_resource'/usr/local/lib/ruby/site_ruby/1.9/puppet/transaction/resource_harness.rb:17:in `evaluate'/usr/local/lib/ruby/site_ruby/1.9/puppet/transaction.rb:174:in `apply'/usr/local/lib/ruby/site_ruby/1.9/puppet/transaction.rb:187:in `eval_resource'/usr/local/lib/ruby/site_ruby/1.9/puppet/transaction.rb:117:in `call'/usr/local/lib/ruby/site_ruby/1.9/puppet/transaction.rb:117:in `block (2 levels) in evaluate'/usr/local/lib/ruby/site_ruby/1.9/puppet/util.rb:327:in `block in thinmark'/usr/local/lib/ruby/1.9/benchmark.rb:295:in `realtime'/usr/local/lib/ruby/site_ruby/1.9/puppet/util.rb:326:in `thinmark'/usr/local/lib/ruby/site_ruby/1.9/puppet/transaction.rb:117:in `block in evaluate'/usr/local/lib/ruby/site_ruby/1.9/puppet/graph/relationship_graph.rb:118:in `traverse'/usr/local/lib/ruby/site_ruby/1.9/puppet/transaction.rb:108:in `evaluate'/usr/local/lib/ruby/site_ruby/1.9/puppet/resource/catalog.rb:164:in `block in apply'/usr/local/lib/ruby/site_ruby/1.9/puppet/util/log.rb:149:in `with_destination'/usr/local/lib/ruby/site_ruby/1.9/puppet/transaction/report.rb:108:in `as_logging_destination'/usr/local/lib/ruby/site_ruby/1.9/puppet/resource/catalog.rb:163:in `apply'/usr/local/lib/ruby/site_ruby/1.9/puppet/configurer.rb:125:in `block in apply_catalog'/usr/local/lib/ruby/site_ruby/1.9/puppet/util.rb:161:in `block in benchmark'/usr/local/lib/ruby/1.9/benchmark.rb:295:in `realtime'/usr/local/lib/ruby/site_ruby/1.9/puppet/util.rb:160:in `benchmark'/usr/local/lib/ruby/site_ruby/1.9/puppet/configurer.rb:124:in `apply_catalog'/usr/local/lib/ruby/site_ruby/1.9/puppet/configurer.rb:192:in `run'/usr/local/lib/ruby/site_ruby/1.9/puppet/agent.rb:44:in `block (4 levels) in run'/usr/local/lib/ruby/site_ruby/1.9/puppet/agent/locker.rb:20:in `lock'/usr/local/lib/ruby/site_ruby/1.9/puppet/agent.rb:44:in `block (3 levels) in run'/usr

Jira (PUP-2158) Directory Environments breaks many classic Config File Environments

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Directory Environments breaks many classic Config File Environments 










Merged an additional commit 1c55916 












   

 Add Comment











 













 Puppet /  PUP-2158



  Directory Environments breaks many classic Config File Environments 







 If you use the script in the classic blog post http://puppetlabs.com/blog/git-workflow-and-puppet-environments you have Config File Environments located at /etc/puppet/environments. Unfortunately, Puppet 3.5.0 will treat them as Directory Environments. If you have a modulepath such as this:   {noformat}    modulepath=/etc/puppet/environments/$environme...















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




 














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

Jira (PDB-576) PR (915): (maint) have beaker tests use the host.hostname instead of host.name - anodelman

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-576



  PR (915): (maint) have beaker tests use the host.hostname instead of host.name - anodelman 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 09/Apr/14 4:30 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










(maint) have beaker tests use the host.hostname instead of host.name


Author: alice nodelman 


Company: Puppet Labs


Github ID: anodelman


Pull Request 915 Discussion


Pull Request 915 File Diff


Pull Request Description



when you want the current hostname use host.hostname, for some provisioners host.name is the name provided by the user but the current hostname is generated on the fly and thus different.

Jira (PDB-576) PR (915): (maint) have beaker tests use the host.hostname instead of host.name - anodelman

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (915): (maint) have beaker tests use the host.hostname instead of host.name - anodelman 










anodelman commented:
This will depend on puppetlabs/beaker#205 landing and being rolled into a gem - we may want to pin to a beaker version to ensure that this works once the update rolls out.












   

 Add Comment











 













 PuppetDB /  PDB-576



  PR (915): (maint) have beaker tests use the host.hostname instead of host.name - anodelman 







 h2. (maint) have beaker tests use the host.hostname instead of host.name   * Author: alice nodelman   * Company: Puppet Labs  * Github ID: [anodelman|https://github.com/anodelman]  * [Pull Request 915 Discussion|https://github.com/puppetlabs/puppetdb/pull/915]  * [Pull Request 915 File Diff|https://github.com/puppetlabs/puppetdb/pull...















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




 














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

Jira (PDB-576) PR (915): (maint) have beaker tests use the host.hostname instead of host.name - anodelman

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (915): (maint) have beaker tests use the host.hostname instead of host.name - anodelman 










pljenkinsro commented:
Can one of the admins verify this patch?












   

 Add Comment











 













 PuppetDB /  PDB-576



  PR (915): (maint) have beaker tests use the host.hostname instead of host.name - anodelman 







 h2. (maint) have beaker tests use the host.hostname instead of host.name   * Author: alice nodelman   * Company: Puppet Labs  * Github ID: [anodelman|https://github.com/anodelman]  * [Pull Request 915 Discussion|https://github.com/puppetlabs/puppetdb/pull/915]  * [Pull Request 915 File Diff|https://github.com/puppetlabs/puppetdb/pull...















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




 














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

Jira (PDB-576) PR (915): (maint) have beaker tests use the host.hostname instead of host.name - anodelman

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (915): (maint) have beaker tests use the host.hostname instead of host.name - anodelman 










pljenkinsro commented:
Can one of the admins verify this patch?












   

 Add Comment











 













 PuppetDB /  PDB-576



  PR (915): (maint) have beaker tests use the host.hostname instead of host.name - anodelman 







 h2. (maint) have beaker tests use the host.hostname instead of host.name   * Author: alice nodelman   * Company: Puppet Labs  * Github ID: [anodelman|https://github.com/anodelman]  * [Pull Request 915 Discussion|https://github.com/puppetlabs/puppetdb/pull/915]  * [Pull Request 915 File Diff|https://github.com/puppetlabs/puppetdb/pull...















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




 














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

Jira (FACT-455) Using Facter 2.0.1 with Puppet 3.4.2 gives me an error

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Using Facter 2.0.1 with Puppet 3.4.2 gives me an error 










I'm guessing this is due to facter no longer using method_missing to resolve facts...












   

 Add Comment











 













 Facter /  FACT-455



  Using Facter 2.0.1 with Puppet 3.4.2 gives me an error 







 I have just provisioned a new server with Puppet 3.4.2 and Facter 2.0.1   When running puppet agent -t, I get the following error   root@pp-logindexer-01:~# puppet agent -t  Info: Retrieving pluginfacts  Info: Retrieving plugin  Error: Could not retrieve local facts: undefined method `puppetversion' for Facter:Module  Error: Failed to apply catalog: Cou...















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




 














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

Jira (PDB-576) PR (915): (maint) have beaker tests use the host.hostname instead of host.name - anodelman

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (915): (maint) have beaker tests use the host.hostname instead of host.name - anodelman 










anodelman commented:
This will work with current blimpy/ec2 work - since the host.hostname will default to name when vmhostname is not set.












   

 Add Comment











 













 PuppetDB /  PDB-576



  PR (915): (maint) have beaker tests use the host.hostname instead of host.name - anodelman 







 h2. (maint) have beaker tests use the host.hostname instead of host.name   * Author: alice nodelman   * Company: Puppet Labs  * Github ID: [anodelman|https://github.com/anodelman]  * [Pull Request 915 Discussion|https://github.com/puppetlabs/puppetdb/pull/915]  * [Pull Request 915 File Diff|https://github.com/puppetlabs/puppetdb/pull...















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




 














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

Jira (PDB-573) PR (126): Add strict_variables support when puppetdb is not on puppetmaster - mcanevet

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (126): Add strict_variables support when puppetdb is not on puppetmaster - mcanevet 










mcanevet commented:
@kbarber fixed












   

 Add Comment











 













 PuppetDB /  PDB-573



  PR (126): Add strict_variables support when puppetdb is not on puppetmaster - mcanevet 







 h2. Add strict_variables support when puppetdb is not on puppetmaster   * Author: Mickaël Canévet   * Company: camptocamp  * Github ID: [mcanevet|https://github.com/mcanevet]  * [Pull Request 126 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/126]  * [Pull Request 126 File Diff|https://github.com/puppetla...















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




 














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

Jira (PUP-2073) Multiple values for diff_args causes diff execution failure

[Matt Shean (JIRA)]

Title: Message Title










 

 Matt Shean commented on an issue











 






  Re: Multiple values for diff_args causes diff execution failure 










Unfortunately I wasn't able to join the triage today. Is this planned for a merge or should I attend next week's triage?












   

 Add Comment











 













 Puppet /  PUP-2073



  Multiple values for diff_args causes diff execution failure 







 Inserting multiple switches for diff_args in puppet.conf causes diff execution to fail. I experienced this in both Windows and Linux.   Example:  diff_args = -u --strip-trailing-cr   This commit will fix the problem:  https://github.com/mshean/puppet/commit/7972585779f3a12cfe62449df3c5e9d3b96c6136 















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




 














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