Jira (PUP-1607) symbolic_modes.rb acceptance test is really slow

[Ethan Brown (JIRA)]

Title: Message Title










 

 Ethan Brown commented on an issue











 






  Re: symbolic_modes.rb acceptance test is really slow 










I might be misunderstanding the intent of the test, but it seems to me that instead of performing and verifying each apply independently, that the test could be batched up into 2 different apply operations.


Create uniquely named temp files with the requested permissions by applying a single manifest / verify them


Try to change the perms on the same set of files / verify them


This would require a complete overhaul of the test as I understand it












   

 Add Comment











 













 Puppet /  PUP-1607



  symbolic_modes.rb acceptance test is really slow 







 [~ethan] added performance data to Jenkins which pointed out that the symbolic_modes.rb test is really slow. It would be nice to speed this test up so that acceptance runs are quicker.















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




 

Jira (PUP-1607) symbolic_modes.rb acceptance test is really slow

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: symbolic_modes.rb acceptance test is really slow 










I looked at one run and there were 360 `puppet apply` operations. Each one can take 2+ seconds and I believe the sheer volume of starting up puppet that many times is the big contributor to the slowness.
The 360 comes from something like this:


for each agent (2)


there are 22 `assert_creates` tests and 26 `assert_modifies` test (x48)


each test checks for file mode and dir mode (x2)


almost (see note) each mode test runs puppet apply twice (x2)


Note: some of the tests don't actually run the first apply (see the test for details re `expected_mode`).
2 * 48 * 2 * 2 = 384, but there are actually only 360 tests because of the tests that skip when the `expected_mode` already matches.
The lowest-hanging fruit here is that there's probably only marginal gain from running this test on both agents (generally the agents are running the same distro, just x86_64 vs x86, and sometime its identical).
Also a possibility is to make the test code somewhat longer by having slightly more complex manifests combining the steps of the single manifest template that is reused repeatedly through the test.
It also may be worth scrubbing the 48 tests for whether all conditions are still interesting (I didn't really look).












   

 Add Comment











 













 Puppet /  PUP-1607



  symbolic_modes.rb acceptance test is really slow 
  

Jira (PUP-1607) symbolic_modes.rb acceptance test is really slow

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1607



  symbolic_modes.rb acceptance test is really slow 










Issue Type:

  Bug




Assignee:

 Eric Sorenson




Created:


 06/Feb/14 10:04 PM




Priority:

  Normal




Reporter:

 Kylo Ginsberg










Ethan Brown added performance data to Jenkins which pointed out that the symbolic_modes.rb test is really slow. It would be nice to speed this test up so that acceptance runs are quicker.












   

 Add Comment











 










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




 









 

Jira (PUP-1604) PR (2333): (doc) Split up README_DEVELOPER - zaphod42

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2333): (doc) Split up README_DEVELOPER - zaphod42 










kylog commented:
Huge improvement @zaphod42 !












   

 Add Comment











 













 Puppet /  PUP-1604



  PR (2333): (doc) Split up README_DEVELOPER - zaphod42 







 h2. (doc) Split up README_DEVELOPER   * Author: Andrew Parker <>  * Company: Puppet Labs  * Github ID: [zaphod42|https://github.com/zaphod42]  * [Pull Request 2333 Discussion|https://github.com/puppetlabs/puppet/pull/2333]  * [Pull Request 2333 File Diff|https://github.com/puppetlabs/puppet/pull/2333/files]  h2. Pull Request Description   The README_D...















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




 














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

Jira (PUP-1606) Virtual classes are always realized

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1606



  Virtual classes are always realized 










Change By:

 Kylo Ginsberg









 Declaring a virtual class should not instantiate it without being realized.  This worked in puppet 2.6.1 but is broken in 2.6.7.  I also tried it in 2.7.9 and it still seems to be broken.  The code below is a very simple example.  vclass and the notify should not happen because it is not realized.  {code} class vclass {notify {"vclass":message => "I've been realized"}}class iclass {@class {"vclass": }}class {"iclass":}  {code} Puppet 2.7.9 output:  {code} puppet apply --debug iclass.ppdebug: importing '/root/iclass.pp' in environment productiondebug: Creating default schedulesdebug: Failed to load library 'selinux' for feature 'selinux'debug: Failed to load library 'shadow' for feature 'libshadow'debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not existdebug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not existdebug: Failed to load library 'ldap' for feature 'ldap'debug: Puppet::Type::User::ProviderLdap: feature ldap is missingdebug: Puppet::Type::User::ProviderPw: file pw does not existdebug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl]debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring File[/etc/puppet/ssl]debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring File[/var/lib/puppet/state]debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/lib/puppet]debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring File[/var/lib/puppet/state]debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet]debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring File[/etc/puppet/ssl]debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/lib/puppet/state]debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/puppet]debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet]debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring File[/var/lib/puppet/state]debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/puppet]debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]debug: Finishing transaction 23948234472800debug: Loaded state in 0.00 secondsdebug: Loaded state in 0.00 secondsinfo: Applying configuration version '1327691293'debug: /Schedule[daily]: Skipping device resources because running on a hostdebug: /Schedule[monthly]: Skipping device resources because running on a hostnotice: I've been realizednotice: /Notify[vclass]/message: defined 'message' as 'I've been realized'debug: /Schedule[hourly]: Skipping device resources because running on a hostdebug: /Schedule[never]: Skipping device resources because running on a hostdebug: /Schedule[weekly]: Skipping device resources because running on a hostdebug: /Schedule[puppet]: Skipping device resources because running on a hostdebug: Finishing transactio

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

[Ethan Brown (JIRA)]

Title: Message Title










 

 Ethan Brown commented on an issue











 






  Re: No EC2 facts shown on newly-built Amazon Linux host 










There is a lot of prior discussion on this issue at http://projects.puppetlabs.com/issues/7559












   

 Add Comment











 













 Facter /  FACT-185



  No EC2 facts shown on newly-built Amazon Linux host 







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















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




 














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

[Ryan Senior (JIRA)]

Title: Message Title










 

 Ryan Senior updated an issue











 






 PuppetDB /  PDB-432



  PR (840): Remove v1 API - senior 










Change By:

 Ryan Senior




Affects Version/s:

 2.0.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-1606) Virtual classes are always realized

[redmine.exporter (JIRA)]

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1606



  Virtual classes are always realized 










Issue Type:

  Bug




Assignee:

 Eric Sorenson




Created:


 06/Feb/14 6:38 PM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










Declaring a virtual class should not instantiate it without being realized. This worked in puppet 2.6.1 but is broken in 2.6.7. I also tried it in 2.7.9 and it still seems to be broken. The code below is a very simple example. vclass and the notify should not happen because it is not realized.
 class vclass { notify  {"vclass": message => "I've been realized" }
}
class iclass { @class  {"vclass": }
}
class  {"iclass":}

Puppet 2.7.9 output:  puppet apply --debug iclass.pp debug: importing '/root/iclass.pp' in environment production debug: Creating default schedules debug: Failed to load library 'selinux' for feature 'selinux' debug: Failed to load library 'shadow' for feature 'libshadow' debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug: Failed to load library 'ldap' for feature 'ldap' debug: Puppet::Type::User::ProviderLdap: feature ldap is missing debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring File[/etc/puppet/ssl] debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring 

Jira (PUP-1029) filter function should accept two parameters

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg assigned an issue to Unassigned











 






 Puppet /  PUP-1029



  filter function should accept two parameters 










Change By:

 Henrik Lindberg




Assignee:

 Henrik Lindberg












   

 Add Comment











 










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




 














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

Jira (PDB-432) PR (840): Remove v1 API - senior

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-432



  PR (840): Remove v1 API - senior 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 06/Feb/14 5:22 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Remove v1 API


Author: Ryan Senior 


Company:


Github ID: senior


Pull Request 840 Discussion


Pull Request 840 File Diff


Pull Request Description

This commit removes the v1 API and builds on the HTTP api refactor. This commit contains:


Remove all v1 namespaces and the namespaces calling them


  

Jira (PUP-1604) PR (2333): (doc) Split up README_DEVELOPER - zaphod42

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2333): (doc) Split up README_DEVELOPER - zaphod42 










hlindberg commented:
Better than before. 












   

 Add Comment











 













 Puppet /  PUP-1604



  PR (2333): (doc) Split up README_DEVELOPER - zaphod42 







 h2. (doc) Split up README_DEVELOPER   * Author: Andrew Parker <>  * Company: Puppet Labs  * Github ID: [zaphod42|https://github.com/zaphod42]  * [Pull Request 2333 Discussion|https://github.com/puppetlabs/puppet/pull/2333]  * [Pull Request 2333 File Diff|https://github.com/puppetlabs/puppet/pull/2333/files]  h2. Pull Request Description   The README_D...















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




 














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

Jira (PUP-1604) PR (2333): (doc) Split up README_DEVELOPER - zaphod42

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2333): (doc) Split up README_DEVELOPER - zaphod42 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 Puppet /  PUP-1604



  PR (2333): (doc) Split up README_DEVELOPER - zaphod42 







 h2. (doc) Split up README_DEVELOPER   * Author: Andrew Parker <>  * Company: Puppet Labs  * Github ID: [zaphod42|https://github.com/zaphod42]  * [Pull Request 2333 Discussion|https://github.com/puppetlabs/puppet/pull/2333]  * [Pull Request 2333 File Diff|https://github.com/puppetlabs/puppet/pull/2333/files]  h2. Pull Request Description   The README_D...















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




 














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

Jira (PUP-1574) Using new directory environments with puppet apply prevents evaluation of the manifest requested on the commandline.

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker assigned an issue to Unassigned











 






 Puppet /  PUP-1574



  Using new directory environments with puppet apply prevents evaluation of the manifest requested on the commandline. 










Change By:

 Andrew Parker




Assignee:

 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-1574) Using new directory environments with puppet apply prevents evaluation of the manifest requested on the commandline.

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: Using new directory environments with puppet apply prevents evaluation of the manifest requested on the commandline. 










Merged into master in https://github.com/puppetlabs/puppet/commit/b6a9dc130cf17724779f9e1bd3ed1a85eb3a13fb












   

 Add Comment











 













 Puppet /  PUP-1574



  Using new directory environments with puppet apply prevents evaluation of the manifest requested on the commandline. 







 Assuming you are working with master past the inclusion of PUP-1118 (3c4669d) and you have directory environments available:   {code}  jpartlow@percival:~/work/puppet$ tree ~/.puppet/environments/  /home/jpartlow/.puppet/environments/  └── myenv   1 directory, 0 files  {code}   Then given a manifest ./local.pp   {code}  jpartlow@percival:~/work/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.

Jira (PUP-1574) Using new directory environments with puppet apply prevents evaluation of the manifest requested on the commandline.

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker assigned an issue to Andrew Parker











 






 Puppet /  PUP-1574



  Using new directory environments with puppet apply prevents evaluation of the manifest requested on the commandline. 










Change By:

 Andrew Parker




Assignee:

 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-649) PR (2024): (#3220) crontab: allow purging unmanaged resources - ffrank

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker assigned an issue to Felix Frank











 






 Puppet /  PUP-649



  PR (2024): (#3220) crontab: allow purging unmanaged resources - ffrank 










Change By:

 Andrew Parker




Assignee:

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

Jira (PUP-728) PR (2060): (#3299) add the file attributes owner, group and mode to nagios types - ffrank

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker assigned an issue to Felix Frank











 






 Puppet /  PUP-728



  PR (2060): (#3299) add the file attributes owner, group and mode to nagios types - ffrank 










Change By:

 Andrew Parker




Assignee:

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

Jira (PDB-423) Update dujour to notify users to use 1.6.2

[Ryan Senior (JIRA)]

Title: Message Title










 

 Ryan Senior updated an issue











 






 PuppetDB /  PDB-423



  Update dujour to notify users to use 1.6.2 










Change By:

 Ryan Senior









 Dujour needs an update for the latest 1.6. 1 2 .












   

 Add Comment











 










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




 














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

Jira (PUP-1597) "contain" cannot contain "contain"

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: "contain" cannot contain "contain" 










I tried this out and it looks like there isn't a problem with containing something that is containing something. I can reproduce what appears to be the same problem by simply calling contains with a fully qualified class name:



class a { }
contain(::a)





> be puppet apply t.pp
Error: undefined method `tag' for nil:NilClass on node aparker.corp.puppetlabs.net
Error: undefined method `tag' for nil:NilClass on node aparker.corp.puppetlabs.net















   

 Add Comment











 













 Puppet /  PUP-1597



  "contain" cannot contain "contain" 







 nested contains don't appear to work. I'm hitting this issue when trying to {{contain}} puppetlabs/mysql::client, but the issue can be reproduced quite simply:   {code}  #  class mybug::client (    $package_ensure = 'present',    $package_name = 'mysql',  ){    package { 'mybug_client':  ensure => $mybug::client::package_ensure,  name => $m...















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


 

Jira (PUP-1585) cron resources with target specified generate duplicate entries

[Felix Frank (JIRA)]

Title: Message Title










 

 Felix Frank commented on an issue











 






  Re: cron resources with target specified generate duplicate entries 










A more educated guess now is that this is a regression caused by https://projects.puppetlabs.com/issues/19876 - ironically.
It's pretty hurtful that the cron type exposes both the target and user properties. On provider level, there's code in place to make them interchangeable, but that's missing on the type level. Note that using user instead of target yields the expected result.
Fortunately, it should be a simple fix. Big thanks for reporting this.












   

 Add Comment











 













 Puppet /  PUP-1585



  cron resources with target specified generate duplicate entries 







 The following resource results in duplicate cron entry added with each puppet run:  {noformat} cron { 'bacula_vacuumdb':    ensure => present,    minute => '00',    hour => '12',    command => 'vacuumdb --analyze -U postgres bacula',    target => 'postgres',  }{noformat}   Example of Cron:  {noformat}~# crontab -l ...















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




 














-- 
You re

Jira (PUP-1597) "contain" cannot contain "contain"

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker updated an issue











 






 Puppet /  PUP-1597



  "contain" cannot contain "contain" 










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-753) Create a reasonable "benchmark" manifest

[Ethan Brown (JIRA)]

Title: Message Title










 

 Ethan Brown commented on an issue











 






  Re: Create a reasonable "benchmark" manifest 










I have enabled JUnit based performance graphs in Jenkins for all of the 'Puppet FOSS' jobs in Jenkins (both master and stable):
https://jenkins.puppetlabs.com/view/Puppet%20FOSS/
Things to keep in mind


We should validate that the information is useful / graphs are trending properly on or about 2/12/14.


We should measure that enabling these graphs hasn't impacted storage or job run times in a significant way


If useful, we might also want to enable these graphs on Facter, Hiera and modules?


Running our new profiler code for an overall benchmark will be performed on some sort of physical hardware that isn't subject to external performance anomalies














   

 Add Comment











 













 Puppet /  PUP-753



  Create a reasonable "benchmark" manifest 







 Concrete baseline for performance measurement

Jira (PUP-649) PR (2024): (#3220) crontab: allow purging unmanaged resources - ffrank

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2024): (#3220) crontab: allow purging unmanaged resources - ffrank 










zaphod42 commented:
@Sharpie @ffrank Oh! I just read the comments on the `additional_resources_generator` change in this PR. It looks like it was explained why it is needed here, sorry that I didn't catch it before.
Since the change is really just to handle things that are really malformed catalogs, I think we should keep that change out. I'd much rather have it fail quickly on something malformed than keep going and possibly get into a worse situation.
So I think we should clean up the tests that are generating incorrect catalogs. If we add something to the `additional_resource_generator` code, then it should be to more clearly call out the problem.












   

 Add Comment











 













 Puppet /  PUP-649



  PR (2024): (#3220) crontab: allow purging unmanaged resources - ffrank 







 h2. (#3220) crontab: allow purging unmanaged resources   * Author: <>  * Company:   * Github ID: [ffrank|https://github.com/ffrank]  * [Pull Request 2024 Discussion|https://github.com/puppetlabs/puppet/pull/2024]  * [Pull Request 2024 File Diff|https://github.com/puppetlabs/puppet/pull/2024/files]  h2. Pull Request Description   This pull was request...















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




 

Jira (PDB-421) Update downloads page

[Melissa Stone (JIRA)]

Title: Message Title










 

 Melissa Stone assigned an issue to Melissa Stone











 






 PuppetDB /  PDB-421



  Update downloads page 










Change By:

 Melissa Stone




Assignee:

 Melissa Stone












   

 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-246) One item array are casted to String when stored in puppetdb

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-246



  One item array are casted to String when stored in puppetdb 










Change By:

 Kenneth Barber




Affects Version/s:

 2.x




Affects Version/s:

 1.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 (PDB-336) Investigage - PuppetDB won't start: OutOfMemoryError: Java heap space

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-336



  Investigage - PuppetDB won't start: OutOfMemoryError: Java heap space 










Change By:

 Kenneth Barber




Fix Version/s:

 2.x




Fix Version/s:

 1.6.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-753) Create a reasonable "benchmark" manifest

[Andrew Parker (JIRA)]

Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: Create a reasonable "benchmark" manifest 










After some discussion we've decided to pull this back and make sure that the benchmarks are running in our jenkins infrastructure and we can graph the benchmark times.












   

 Add Comment











 













 Puppet /  PUP-753



  Create a reasonable "benchmark" manifest 







 Concrete baseline for performance measurement















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this 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-640) Report format 4 docs should be updated for optional fields

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: Report format 4 docs should be updated for optional fields 










Ruth Linehan can you sanity check here? I was treating this as a documentation-only issue and assumed that the report schema was only used by puppet spec tests. And thus this is only on puppet/master and wasn't merged to pe-puppet/3.2.x.












   

 Add Comment











 













 Puppet /  PUP-640



  Report format 4 docs should be updated for optional fields 







 In PE 3.1.0/Puppet 3.3.1 the report format changed to include a new kind of event, which is not associated with a property, for some failures that previously did not have an event. This has caused a change in the report format because these events do not always have previous_value, property, desired_value, name, and historical_value. Some of these get tra...















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




 














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

Jira (PUP-1605) `puppet resource ssh_authorized_key ` should work

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: `puppet resource ssh_authorized_key ` should work 










ParsedFile providers, such as Ssh_authorized_key, return resource instances to puppet resource by loading a list of files referred to as the "default target". The provider implementation of Ssh_authorized_key happens to specify '' as a default target. This means no resources are available for puppet resource to load.












   

 Add Comment











 













 Puppet /  PUP-1605



  `puppet resource ssh_authorized_key ` should work 







 One of my clients remarked that he was working through the Learning Puppet track and ran into a stack trace.   Learning Puppet teaches the `puppet resource` command, the later has an exercise for the `ssh_authorized_key` resource (on ). Running `puppet resource ssh_authorized_key hunner` throws a stack ...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
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-1585) cron resources with target specified generate duplicate entries

[Felix Frank (JIRA)]

Title: Message Title










 

 Felix Frank commented on an issue











 






  Re: cron resources with target specified generate duplicate entries 










Forsooth, you're right. I spoke too soon.
This is likely some regression then. Will look into it.












   

 Add Comment











 













 Puppet /  PUP-1585



  cron resources with target specified generate duplicate entries 







 The following resource results in duplicate cron entry added with each puppet run:  {noformat} cron { 'bacula_vacuumdb':    ensure => present,    minute => '00',    hour => '12',    command => 'vacuumdb --analyze -U postgres bacula',    target => 'postgres',  }{noformat}   Example of Cron:  {noformat}~# crontab -l ...















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




 














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

Jira (PUP-1605) `puppet resource ssh_authorized_key ` should work

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1605



  `puppet resource ssh_authorized_key ` should work 










Change By:

 Charlie Sharpsteen




Issue Type:

 Bug Improvement












   

 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-1605) `puppet resource ssh_authorized_key ` should work

[redmine.exporter (JIRA)]

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1605



  `puppet resource ssh_authorized_key ` should work 










Issue Type:

  Bug




Assignee:

 Eric Sorenson




Created:


 06/Feb/14 3:22 PM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










One of my clients remarked that he was working through the Learning Puppet track and ran into a stack trace.
Learning Puppet teaches the `puppet resource` command, the later has an exercise for the `ssh_authorized_key` resource (on ). Running `puppet resource ssh_authorized_key hunner` throws a stack trace because `lib/puppet/type/ssh_authorized_key:104`, `@parameters[:target]` is `nil`.
 cz% envpuppet puppet resource ssh_authorized_key hunner  /Users/hunner/Documents/work/git/puppet/lib/puppet/type/ssh_authorized_key.rb:104:in `validate': undefined method `[]' for nil:NilClass (NoMethodError) from /Users/hunner/Documents/work/git/puppet/lib/puppet/type.rb:1807:in `initialize' from /Users/hunner/Documents/work/git/puppet/lib/puppet/indirector/resource/ral.rb:5:in `new' from /Users/hunner/Documents/work/git/puppet/lib/puppet/indirector/resource/ral.rb:5:in `find' from /Users/hunner/Documents/work/git/puppet/lib/puppet/indirector/indirection.rb:196:in `find' from /Users/hunner/Documents/work/git/puppet/lib/puppet/application/resource.rb:222:in `find_or_save_resources' from /Users/hunner/Documents/work/git/puppet/lib/puppet/application/resource.rb:144:in `main' from /Users/hunner/Documents/work/git/puppet/lib/puppet/application.rb:317:in `run_command' from /Users/hunner/Documents/work/git/puppet/lib/puppet/application.rb:309:in `run' from /Users/hunner/Documents/work/git/puppet/lib/puppet/application.rb:416:

Jira (PUP-1555) PR (2314): (maint) Add optional_parameter_count method to Closure - dalen

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2314): (maint) Add optional_parameter_count method to Closure - dalen 










Pull request (maint) Add optional_parameter_count method to Closure has been closed.












   

 Add Comment











 













 Puppet /  PUP-1555



  PR (2314): (maint) Add optional_parameter_count method to Closure - dalen 







 h2. (maint) Add optional_parameter_count method to Closure   * Author: Erik Dalén   * Company: Spotify  * Github ID: [dalen|https://github.com/dalen]  * [Pull Request 2314 Discussion|https://github.com/puppetlabs/puppet/pull/2314]  * [Pull Request 2314 File Diff|https://github.com/puppetlabs/puppet/pull/2314/files]  h2. Pull R...















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




 














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

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1605



  `puppet resource ssh_authorized_key ` should work 










Change By:

 Charlie Sharpsteen









 One of my clients remarked that he was working through the Learning Puppet track and ran into a stack trace.Learning Puppet teaches the `puppet resource` command, the later has an exercise for the `ssh_authorized_key` resource (on ). Running `puppet resource ssh_authorized_key hunner` throws a stack trace because `lib/puppet/type/ssh_authorized_key:104`, `@parameters[:target]` is `nil`.  {code} cz% envpuppet puppet resource ssh_authorized_key hunner   /Users/hunner/Documents/work/git/puppet/lib/puppet/type/ssh_authorized_key.rb:104:in `validate': undefined method `[]' for nil:NilClass (NoMethodError) from /Users/hunner/Documents/work/git/puppet/lib/puppet/type.rb:1807:in `initialize' from /Users/hunner/Documents/work/git/puppet/lib/puppet/indirector/resource/ral.rb:5:in `new' from /Users/hunner/Documents/work/git/puppet/lib/puppet/indirector/resource/ral.rb:5:in `find' from /Users/hunner/Documents/work/git/puppet/lib/puppet/indirector/indirection.rb:196:in `find' from /Users/hunner/Documents/work/git/puppet/lib/puppet/application/resource.rb:222:in `find_or_save_resources' from /Users/hunner/Documents/work/git/puppet/lib/puppet/application/resource.rb:144:in `main' from /Users/hunner/Documents/work/git/puppet/lib/puppet/application.rb:317:in `run_command' from /Users/hunner/Documents/work/git/puppet/lib/puppet/application.rb:309:in `run' from /Users/hunner/Documents/work/git/puppet/lib/puppet/application.rb:416:in `hook' from /Users/hunner/Documents/work/git/puppet/lib/puppet/application.rb:309:in `run' from /Users/hunner/Documents/work/git/puppet/lib/puppet/application.rb:407:in `exit_on_fail' from /Users/hunner/Documents/work/git/puppet/lib/puppet/application.rb:309:in `run' from /Users/hunner/Documents/work/git/puppet/lib/puppet/util/command_line.rb:69:in `execute' from /Users/hunner/Documents/work/git/puppet/bin/puppet:4cz% envpuppet puppet resource ssh_authorized_key hunner target=ssh-rsanotice: /Ssh_authorized_key[hunner]/ensure: createderr: /Ssh_authorized_key[hunner]: Could not evaluate: Cannot write SSH authorized keys without userssh_authorized_key { 'hunner':  ensure => 'present',  target => 'ssh-rsa',}  {code} I have two ssh-rsa keys in `~/.ssh/authorized_keys2`












   

 Add Comment

Jira (PUP-1604) PR (2333): (doc) Split up README_DEVELOPER - zaphod42

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot created an issue











 






 Puppet /  PUP-1604



  PR (2333): (doc) Split up README_DEVELOPER - zaphod42 










Issue Type:

  Task




Assignee:

 Eric Sorenson




Components:


 Community




Created:


 06/Feb/14 3:14 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










(doc) Split up README_DEVELOPER


Author: Andrew Parker <>


Company: Puppet Labs


Github ID: zaphod42


Pull Request 2333 Discussion


Pull Request 2333 File Diff


Pull Request Description

The README_DEVELOPER document was getting too large and unwieldy. There 

Jira (HI-153) PR (174): Apply the RHEL7 work and merge it into stable - mckern

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (174): Apply the RHEL7 work and merge it into stable - mckern 










Pull request Apply the RHEL7 work and merge it into stable has been closed.












   

 Add Comment











 













 Hiera /  HI-153



  PR (174): Apply the RHEL7 work and merge it into stable - mckern 







 h2. Apply the RHEL7 work and merge it into stable   * Author: Ryan McKern   * Company: Puppet Labs  * Github ID: [mckern|https://github.com/mckern]  * [Pull Request 174 Discussion|https://github.com/puppetlabs/hiera/pull/174]  * [Pull Request 174 File Diff|https://github.com/puppetlabs/hiera/pull/174/files]  h2. Pull Request Descripti...















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




 














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

[Melissa Stone (JIRA)]

Title: Message Title










 

 Melissa Stone updated an issue











 






 Facter /  FACT-290



  Merge tag into the right branch 










Change By:

 Melissa Stone









 the new tag should get merged into the 3.3.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 (FACT-290) Merge tag into the right branch

[Melissa Stone (JIRA)]

Title: Message Title










 

 Melissa Stone updated an issue











 






 Facter /  FACT-290



  Merge tag into the right branch 










Change By:

 Melissa Stone









 the new tag should get merged into the 3.3.x  branch












   

 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-408) Fix Fedora 20 packaging issues

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-408



  Fix Fedora 20 packaging issues 










Change By:

 Kenneth Barber




Fix Version/s:

 1.6.x




Fix Version/s:

 1.6.2












   

 Add Comment











 










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




 














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

Jira (PUP-1585) cron resources with target specified generate duplicate entries

[Doug Forster (JIRA)]

Title: Message Title










 

 Doug Forster commented on an issue











 






  Re: cron resources with target specified generate duplicate entries 










If it is related to the "00" why does it work when target is set to root or left blank? It only duplicates entries when target is changed from my experience. 












   

 Add Comment











 













 Puppet /  PUP-1585



  cron resources with target specified generate duplicate entries 







 The following resource results in duplicate cron entry added with each puppet run:  {noformat} cron { 'bacula_vacuumdb':    ensure => present,    minute => '00',    hour => '12',    command => 'vacuumdb --analyze -U postgres bacula',    target => 'postgres',  }{noformat}   Example of Cron:  {noformat}~# crontab -l ...















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




 














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

Jira (FACT-196) PR (594): (fact-155) Fix operatingsystemrelease on Solaris 11 - stschulte

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (594): (fact-155) Fix operatingsystemrelease on Solaris 11 - stschulte 










ghoneycutt commented:
+1 Seems like facter is failing due to an unrelated issue with ruby 1.8.7 that appears to have been fixed in 1de2d8d7a












   

 Add Comment











 













 Facter /  FACT-196



  PR (594): (fact-155) Fix operatingsystemrelease on Solaris 11 - stschulte 







 h2. (fact-155) Fix operatingsystemrelease on Solaris 11   * Author: Stefan Schulte <>  * Company:   * Github ID: [stschulte|https://github.com/stschulte]  * [Pull Request 594 Discussion|https://github.com/puppetlabs/facter/pull/594]  * [Pull Request 594 File Diff|https://github.com/puppetlabs/facter/pull/594/files]  h2. Pull Request Description   sinc...















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




 














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

Jira (PDB-419) Merge new 1.6.2 tag into 3.3.x branch of pe- fork

[Melissa Stone (JIRA)]

Title: Message Title










 

 Melissa Stone updated an issue











 






 PuppetDB /  PDB-419



  Merge new 1.6.2 tag into 3.3.x branch of pe- fork 










Change By:

 Melissa Stone




Summary:

 Merge new 1.6. 1 2  tag into  3.3.x branch of  pe- fork












   

 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-196) PR (594): (fact-155) Fix operatingsystemrelease on Solaris 11 - stschulte

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (594): (fact-155) Fix operatingsystemrelease on Solaris 11 - stschulte 










stschulte commented:
it would be nice to get some feedback here 












   

 Add Comment











 













 Facter /  FACT-196



  PR (594): (fact-155) Fix operatingsystemrelease on Solaris 11 - stschulte 







 h2. (fact-155) Fix operatingsystemrelease on Solaris 11   * Author: Stefan Schulte <>  * Company:   * Github ID: [stschulte|https://github.com/stschulte]  * [Pull Request 594 Discussion|https://github.com/puppetlabs/facter/pull/594]  * [Pull Request 594 File Diff|https://github.com/puppetlabs/facter/pull/594/files]  h2. Pull Request Description   sinc...















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




 














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

Jira (PDB-424) PR (832): Don't use global schema validation - cprice404

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (832): Don't use global schema validation - cprice404 










Pull request Don't use global schema validation has been closed.












   

 Add Comment











 













 PuppetDB /  PDB-424



  PR (832): Don't use global schema validation - cprice404 







 h2. Don't use global schema validation   * Author: Chris Price <>  * Company:   * Github ID: [cprice404|https://github.com/cprice404]  * [Pull Request 832 Discussion|https://github.com/puppetlabs/puppetdb/pull/832]  * [Pull Request 832 File Diff|https://github.com/puppetlabs/puppetdb/pull/832/files]  h2. Pull Request Description   Prior to this commit...















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




 














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

Jira (PUP-1592) Puppet excessively stats the filesystem when looking for defined types

[JIRA]

Title: Message Title










 

 Erik Dalén commented on an issue











 






  Re: Puppet excessively stats the filesystem when looking for defined types  










I've also seen this behaviour (measured it to ~15 stat calls per compile for one of our defined types..).
I agree that it would be better to look for defined types first as they have much fewer places they can be loaded from. For types with :: in the name we can probably even skip looking for ruby types entirely.












   

 Add Comment











 













 Puppet /  PUP-1592



  Puppet excessively stats the filesystem when looking for defined types  







 [~masterzen] and I realized that when puppet tries to resolve a defined type, it always tries to first find the defined type within all the plugin directories as it tries to first load it as a resource type and then as a defined type.   We should be able to avoid a lot of stats on the filesystem by simply changing the lookup order.   [~masterzen] has so...















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




 














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

Jira (PUP-1574) Using new directory environments with puppet apply prevents evaluation of the manifest requested on the commandline.

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow commented on an issue











 






  Re: Using new directory environments with puppet apply prevents evaluation of the manifest requested on the commandline. 










This also affects puppet parser validate.












   

 Add Comment











 













 Puppet /  PUP-1574



  Using new directory environments with puppet apply prevents evaluation of the manifest requested on the commandline. 







 Assuming you are working with master past the inclusion of PUP-1118 (3c4669d) and you have directory environments available:   {code}  jpartlow@percival:~/work/puppet$ tree ~/.puppet/environments/  /home/jpartlow/.puppet/environments/  └── myenv   1 directory, 0 files  {code}   Then given a manifest ./local.pp   {code}  jpartlow@percival:~/work/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://gr

Jira (PUP-677) user type accepts numeric usernames, but ssh_authorized_key does not

[Carthik Sharma (JIRA)]

Title: Message Title










 

 Carthik Sharma commented on an issue











 






  Re: user type accepts numeric usernames, but ssh_authorized_key does not 










The POSIX standard (IEEE Std 1003.1, 2004 Edition) only states that usernames cannot start with the hyphen character. It's a little bookish and not pragmatic, I know, but it's there as a standard:
http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap03.html#tag_03_426 and http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap03.html#tag_03_276












   

 Add Comment











 













 Puppet /  PUP-677



  user type accepts numeric usernames, but ssh_authorized_key does not 







 A purely numeric username is a bit ridiculous, but it actually came up in a training class. A student assigned himself the username of '1970' and things blew up. Testing indicates that this resource type or provider cannot handle a numeric username.   {code}  [root@monkey ~]# puppet resource user 1970 ensure=present managehome=true  Notice: /User[1970]/e...















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




 














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

Jira (PUP-1430) PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen 










dalen commented:
I've added the commits from @joshcooper now that made sense to merge with this (all but 738745d9fe713d888f5a7c7cbcd627ddfde08051).












   

 Add Comment











 













 Puppet /  PUP-1430



  PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen 







 h2. Make SSL file permissions a bit more relaxed for public files   * Author: Erik Dalén   * Company: Spotify  * Github ID: [dalen|https://github.com/dalen]  * [Pull Request 2257 Discussion|https://github.com/puppetlabs/puppet/pull/2257]  * [Pull Request 2257 File Diff|https://github.com/puppetlabs/puppet/pull/2257/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

Jira (PUP-677) user type accepts numeric usernames, but ssh_authorized_key does not

[Stefan Schulte (JIRA)]

Title: Message Title










 

 Stefan Schulte commented on an issue











 






  Re: user type accepts numeric usernames, but ssh_authorized_key does not 










I agree that the user type should do stricter validation. But there is also the possibility that you create the user manually - and obviously some useradd implementations allow you to create a users that the man page states are invalid - and you now stumble across the ssh_authorized_key type that cannot handle the ssh keys of your manually created user.
So while we cannot ensure that you don't have users that are purely numeric, I think we should not try to handle these cases. Again: I have nothing against stricter validations for the user type but I don't now if the "user should be non numeric" applies for all platforms (windows?)












   

 Add Comment











 













 Puppet /  PUP-677



  user type accepts numeric usernames, but ssh_authorized_key does not 







 A purely numeric username is a bit ridiculous, but it actually came up in a training class. A student assigned himself the username of '1970' and things blew up. Testing indicates that this resource type or provider cannot handle a numeric username.   {code}  [root@monkey ~]# puppet resource user 1970 ensure=present managehome=true  Notice: /User[1970]/e...















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




 

  

Jira (PUP-677) ssh_authorized_key can't handle numeric usernames

[Ben Ford (JIRA)]

Title: Message Title










 

 Ben Ford commented on an issue











 






  Re: ssh_authorized_key can't handle numeric usernames 










If this is the case, then the bug is with the user type then. As you correctly state, numeric usernames are not legal.












   

 Add Comment











 













 Puppet /  PUP-677



  ssh_authorized_key can't handle numeric usernames 







 A purely numeric username is a bit ridiculous, but it actually came up in a training class. A student assigned himself the username of '1970' and things blew up. Testing indicates that this resource type or provider cannot handle a numeric username.   {code}  [root@monkey ~]# puppet resource user 1970 ensure=present managehome=true  Notice: /User[1970]/e...















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




 














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

[Ben Ford (JIRA)]

Title: Message Title










 

 Ben Ford updated an issue











 






 Puppet /  PUP-677



  user type accepts numeric usernames, but ssh_authorized_key does not 










Change By:

 Ben Ford




Summary:

 ssh_authorized_key can't handle user type accepts  numeric usernames , but ssh_authorized_key does not












   

 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-677) ssh_authorized_key can't handle numeric usernames

[Stefan Schulte (JIRA)]

Title: Message Title










 

 Stefan Schulte commented on an issue











 






  Re: ssh_authorized_key can't handle numeric usernames 










The manpage states

Usernames must start with a lower case letter or an underscore, followed by lower case letters, digits, underscores, or dashes. They can end with a dollar sign. In regular _expression_ terms: [a-z_][a-z0-9_-]*[$]?

So I don't think that numeric usernames is something puppet should be able to handle. Puppet will just assume it is a UID. Let's say you define


user { "foo":
  uid => 100,
  gid => 100,
}



Now let's suppose if there is a group foo with gid 100 and also a group with the name 100? What should puppet do then?












   

 Add Comment











 













 Puppet /  PUP-677



  ssh_authorized_key can't handle numeric usernames 







 A purely numeric username is a bit ridiculous, but it actually came up in a training class. A student assigned himself the username of '1970' and things blew up. Testing indicates that this resource type or provider cannot handle a numeric username.   {code}  [root@monkey ~]# puppet resource user 1970 ensure=present managehome=true  Notice: /User[1970]/e...















 This message was sent by At

Jira (PUP-1603) puppet apply failure if puppet is upgraded

[Jason Corley (JIRA)]

Title: Message Title










 

 Jason Corley created an issue











 






 Puppet /  PUP-1603



  puppet apply failure if puppet is upgraded 










Issue Type:

  Bug




Assignee:

 Eric Sorenson




Created:


 06/Feb/14 12:33 PM




Priority:

  Normal




Reporter:

 Jason Corley










I am testing an update from puppet 3.2.4 to 3.4.2 and I am receiving a failure that I have found in a few different places on the internet but that has no bug and no reproducer (for reference, I believe these are related links: https://groups.google.com/forum/#!topic/puppet-users/318TmfkO9Js and https://github.com/purpleidea/puppet-puppet/commit/8b7dae5ca3666a2188f3a0670edd87bbc33c64eb). I've made the following reproducer test case:


bring up a vagrant centos 6.5 nocm image. My Vagrantfile looks like so:


# -*- mode: ruby -*-
# vi: set ft=ruby :

# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  config.vm.box = "centos-65-x64-virtualbox-nocm"
  config.vm.box_url = "http://puppet-vagrant-boxes.puppetlabs.com/centos-65-x64-virtualbox-nocm.box"
  config.vm.provider :virtualbox do |vb|
vb.customize ["modifyvm", :id, "--memory", "1024"]
  end
end





log in to the system via vagrant ssh


become root via sudo su -


install pu

Jira (PUP-1602) value validation of parameter managehome is broken

[Stefan Schulte (JIRA)]

Title: Message Title










 

 Stefan Schulte created an issue











 






 Puppet /  PUP-1602



  value validation of parameter managehome is broken 










Issue Type:

  Bug




Affects Versions:


 2.7.24




Assignee:

 Stefan Schulte




Components:


 Types and Providers




Created:


 06/Feb/14 12:26 PM




Priority:

  Normal




Reporter:

 Stefan Schulte










The user type defines a managehome parameter that can be either true of false. Unfortunately no validation happens so you can specify


user { 'foo':
  ensure => present,
  managehome => 'yes', # will not create directory
}
user { 'bar':
  ensure => present,
  managehome => 'foo', # will not create directory
}



both validate to false apparently.
While the type resource already specifies a value list that sets up a proper validate method


newvalues(:true, :false)



the type does also define a custom validate method that will overwrite the checks that would normally take place:
  

Jira (PUP-1599) PR (2330): (maint) Fix syntax error in example code - dalen

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2330): (maint) Fix syntax error in example code - dalen 










Pull request (maint) Fix syntax error in example code has been closed.












   

 Add Comment











 













 Puppet /  PUP-1599



  PR (2330): (maint) Fix syntax error in example code - dalen 







 h2. (maint) Fix syntax error in example code   * Author: Erik Dalén   * Company: Spotify  * Github ID: [dalen|https://github.com/dalen]  * [Pull Request 2330 Discussion|https://github.com/puppetlabs/puppet/pull/2330]  * [Pull Request 2330 File Diff|https://github.com/puppetlabs/puppet/pull/2330/files]  h2. Pull Request Descrip...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this 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-1599) PR (2330): (maint) Fix syntax error in example code - dalen

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2330): (maint) Fix syntax error in example code - dalen 










joshcooper commented:
@nfagerlund gives :thumbsup: 












   

 Add Comment











 













 Puppet /  PUP-1599



  PR (2330): (maint) Fix syntax error in example code - dalen 







 h2. (maint) Fix syntax error in example code   * Author: Erik Dalén   * Company: Spotify  * Github ID: [dalen|https://github.com/dalen]  * [Pull Request 2330 Discussion|https://github.com/puppetlabs/puppet/pull/2330]  * [Pull Request 2330 File Diff|https://github.com/puppetlabs/puppet/pull/2330/files]  h2. Pull Request Descrip...















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




 














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

[Brice Figureau (JIRA)]

Title: Message Title










 

 Brice Figureau commented on an issue











 






  Re: Puppet excessively stats the filesystem when looking for defined types  










Here is a thorough explanation of the bug.
During the puppet agent run, after the catalog has been converted to RAL based resources, the transaction gets applied. This catalog still contains resources of defined types, for which their ultimate RAL type is a P::Type::Component.
During the transaction application, each resource is in turn evaluated by the virtue of P::T::ResourceHarness#evaluate. This operation involves creating a local ResourceApplicationContext, but also transforming the resource to a Hash, by calling P::Resource#to_hash. This last method, calls P::Resource#parse_title to build compound titles if the resource type supports it. For this we need to know what the underlying type of the resource is, by calling P::Resource#resource_type which is implemented like this:



def resource_type
  @rstype ||= case type
  when "Class"; known_resource_types.hostclass(title == :main ? "" : title)
  when "Node"; known_resource_types.node(title)
  else
Puppet::Type.type(type) || known_resource_types.definition(type)
  end
end



In the case of defined type, their underlying type is not Class, nor Node so we end up in the else. That's where things start to get interesting. Puppet will now try to find the defined type class as a built-in type (which it is not). To do that, we'll end up in P::MetaType::Manager#type. This methods then delegates to the type autoloader (P::Util::Autoload)
The autoloader will call load_file which in turn will call get_file:



# Get the correct file to load for a given path
# returns nil if no file is found
def get_file(name, env=nil)
  name = name + '.rb' unless name =~ /\.rb$/
  path = search_directories(env).find { |dir| Puppet::FileSystem::File.exist?(File.join(dir, name)) }
  path and File.join(path, name)
end



If you look carefully our poor type (let's call it "Test::Definition") will form a path where ".rb" is appended, this path will then be appended to every search directories (which is all gem dirs, all modules dir, lib dirs and finally the whole ruby load path). This can be a large number of directories on a big installation. Then each path in turn will be tested for existence which on Unix translates to calling stat(2).
But that's not all, once the autoloader concludes that the file doesn't exist (BTW we could theoretically inject ruby code into the Puppet agent by this way), it will return back to resource_type.
Resource_type will then ask the known_resource_types if it's a known definition. But since we're running in the agent where the compilation didn't happen, the known_resource_type is completely empty (it's not the case in the puppet apply case, because the environment hasn't been reset between the compilation phase and the application phase).
This means resource_type will return nil. So nil will be memoized in @rstype, which means the next time resource_type will be called, we'll also do the whole directory scanning for an inexistent ruby file. My experimentation show t

Jira (PUP-1524) Duplicate events since 3.4.0

[Kurt Wall (JIRA)]

Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-1524



  Duplicate events since 3.4.0 










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

Jira (PUP-1551) Change from "environmentdir" to "environmentpath"

[Kurt Wall (JIRA)]

Title: Message Title










 

 Kurt Wall commented on an issue











 






  Re: Change from "environmentdir" to "environmentpath" 










I can at least verify that environmentpath works and evironmentdir does not in puppet-3.4.2.765:



# puppet.conf
environmentpath=$vardir/enironments

# puppet config print environmentdir
nil
# puppet config print environmentpath
/var/lib/puppet/environments















   

 Add Comment











 













 Puppet /  PUP-1551



  Change from "environmentdir" to "environmentpath" 







 There is likely a need for having multiple directories to hold environments. This can be done by changing from a single {{environmentdir}} to having a list of paths as an {{environmentpath}}.















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




 














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

Jira (FACT-81) Pull Request (499): (#21530) Rename the .to_plist method in cfpropertylist to .to_cfplist

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Pull Request (499): (#21530) Rename the .to_plist method in cfpropertylist to .to_cfplist 










Kylo Ginsberg what do you we need in the way of functional review for this?












   

 Add Comment











 













 Facter /  FACT-81



  Pull Request (499): (#21530) Rename the .to_plist method in cfpropertylist to .to_cfplist 







 h2. (#21530) Rename the .to_plist method in cfpropertylist to .to_cfplist   * Author: Clay Caviness   * Company:   * Github ID: [ccaviness|https://github.com/ccaviness]  * [Pull Request 499 Discussion|https://github.com/puppetlabs/facter/pull/499]  * [Pull Request 499 File Diff|https://github.com/puppetlabs/facter/pull/499/files]  h2. Pul...















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




 














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

Jira (PUP-1551) Change from "environmentdir" to "environmentpath"

[Kurt Wall (JIRA)]

Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-1551



  Change from "environmentdir" to "environmentpath" 










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/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:
:red_circle: Test failed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/210/












   

 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

Jira (PDB-352) PR (814): Apply the RHEL7 work and merge it into 1.6.x - mckern

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (814): Apply the RHEL7 work and merge it into 1.6.x - mckern 










mckern commented:
Closing to retarget












   

 Add Comment











 













 PuppetDB /  PDB-352



  PR (814): Apply the RHEL7 work and merge it into 1.6.x - mckern 







 h2. Apply the RHEL7 work and merge it into 1.6.x   * Author: Ryan McKern   * Company: Puppet Labs  * Github ID: [mckern|https://github.com/mckern]  * [Pull Request 814 Discussion|https://github.com/puppetlabs/puppetdb/pull/814]  * [Pull Request 814 File Diff|https://github.com/puppetlabs/puppetdb/pull/814/files]  h2. Pull Request Desc...















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




 














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

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (837): v1 shared route refactor - senior 










Pull request v1 shared route refactor has been closed.












   

 Add Comment











 













 PuppetDB /  PDB-429



  PR (837): v1 shared route refactor - senior 







 h2. v1 shared route refactor   * Author: Ryan Senior   * Company:   * Github ID: [senior|https://github.com/senior]  * [Pull Request 837 Discussion|https://github.com/puppetlabs/puppetdb/pull/837]  * [Pull Request 837 File Diff|https://github.com/puppetlabs/puppetdb/pull/837/files]  h2. Pull Request Description   This commit sta...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this 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-352) PR (814): Apply the RHEL7 work and merge it into 1.6.x - mckern

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (814): Apply the RHEL7 work and merge it into 1.6.x - mckern 










Pull request WIP: Apply the RHEL7 work and merge it into 1.6.x has been closed.












   

 Add Comment











 













 PuppetDB /  PDB-352



  PR (814): Apply the RHEL7 work and merge it into 1.6.x - mckern 







 h2. Apply the RHEL7 work and merge it into 1.6.x   * Author: Ryan McKern   * Company: Puppet Labs  * Github ID: [mckern|https://github.com/mckern]  * [Pull Request 814 Discussion|https://github.com/puppetlabs/puppetdb/pull/814]  * [Pull Request 814 File Diff|https://github.com/puppetlabs/puppetdb/pull/814/files]  h2. Pull Request Desc...















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




 














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

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Hiera /  HI-114



  No man pages for hiera 










Change By:

 Joshua Cooper




Assignee:

 Eric Sorenson Justin Holguin












   

 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 










cprice404 commented:
@puppetlabs-jenkins retest this please












   

 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-1589) PR (2328): Msgpack terminii - dalen

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2328): Msgpack terminii - dalen 










dalen commented:
Most of the code and tests in this PR are based on the PSON and YAML equivalents, so very similar in layout and test cases.












   

 Add Comment











 













 Puppet /  PUP-1589



  PR (2328): Msgpack terminii - dalen 







 h2. Msgpack terminii   * Author: Erik Dalén   * Company: Spotify  * Github ID: [dalen|https://github.com/dalen]  * [Pull Request 2328 Discussion|https://github.com/puppetlabs/puppet/pull/2328]  * [Pull Request 2328 File Diff|https://github.com/puppetlabs/puppet/pull/2328/files]  h2. Pull Request Description   Allow catalog...















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




 














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

Jira (FACT-150) Facter timeouts reap all subprocesses thus confusing Puppet

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo assigned an issue to Adrien Thebo











 






 Facter /  FACT-150



  Facter timeouts reap all subprocesses thus confusing Puppet 










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 (FACT-268) PR (621): debian/control: Depend on lsb-core. - daenney

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (621): debian/control: Depend on lsb-core. - daenney 










daenney commented:
Suggests does not pull in packages by default, only Recommends are pulled in.
As per Debian packaging policy: ``` Suggests: This is used to declare that one package may be more useful with one or more others. Using this field tells the packaging system and the user that the listed packages are related to this one and can perhaps enhance its usefulness, but that installing this one without them is perfectly reasonable. ```












   

 Add Comment











 













 Facter /  FACT-268



  PR (621): debian/control: Depend on lsb-core. - daenney 







 h2. debian/control: Depend on lsb-core.   * Author: Daniele Sluijters   * Company:   * Github ID: [daenney|https://github.com/daenney]  * [Pull Request 621 Discussion|https://github.com/puppetlabs/facter/pull/621]  * [Pull Request 621 File Diff|https://github.com/puppetlabs/facter/pull/621/files]  h2. Pull Request Description   In ...















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




 














-- 
You received th

Jira (PUP-1430) PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen 










dalen commented:
Not yet, might be able to do it tonight though.












   

 Add Comment











 













 Puppet /  PUP-1430



  PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen 







 h2. Make SSL file permissions a bit more relaxed for public files   * Author: Erik Dalén   * Company: Spotify  * Github ID: [dalen|https://github.com/dalen]  * [Pull Request 2257 Discussion|https://github.com/puppetlabs/puppet/pull/2257]  * [Pull Request 2257 File Diff|https://github.com/puppetlabs/puppet/pull/2257/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

Jira (FACT-268) PR (621): debian/control: Depend on lsb-core. - daenney

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (621): debian/control: Depend on lsb-core. - daenney 










adrienthebo commented:
@daenney I'm not qualified to make decisions on packaging, that would be the wheelhouse of @haus or @melissaanne. That being said I don't think we can make this change because of all the dependencies that the lsb packages tend to pull in. I'm not familiar with the behavior of Debian `Suggests` but if that pulls in packages by default then this will pull in the entire lsb package, which would be horrendous.
Haus, Melissa, would you folks be able to make a decision on this?












   

 Add Comment











 













 Facter /  FACT-268



  PR (621): debian/control: Depend on lsb-core. - daenney 







 h2. debian/control: Depend on lsb-core.   * Author: Daniele Sluijters   * Company:   * Github ID: [daenney|https://github.com/daenney]  * [Pull Request 621 Discussion|https://github.com/puppetlabs/facter/pull/621]  * [Pull Request 621 File Diff|https://github.com/puppetlabs/facter/pull/621/files]  h2. Pull Request Description   In ...















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




 

Jira (PDB-431) PR (839): Updated the 1.6.2 release notes - senior

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-431



  PR (839): Updated the 1.6.2 release notes - senior 










Change By:

 Kenneth Barber




Fix Version/s:

 1.6.2












   

 Add Comment











 










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




 














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

Jira (PUP-1601) functions accepting regexp string should also accept Regexp

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg created an issue











 






 Puppet /  PUP-1601



  functions accepting regexp string should also accept Regexp 










Issue Type:

  Bug




Assignee:

 Andrew Parker




Components:


 DSL




Created:


 06/Feb/14 9:47 AM




Fix Versions:


 3.6.0




Priority:

  Normal




Reporter:

 Henrik Lindberg










Functions (e.g. split) that accepts a reguar _expression_ in string form should also accept an already created regular _expression_, or the PRegexpType from which a regular _expression_ can be obtained.












   

 Add Comment











 

Jira (PDB-431) PR (839): Updated the 1.6.2 release notes - senior

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (839): Updated the 1.6.2 release notes - senior 










Pull request Updated the 1.6.2 release notes has been closed.












   

 Add Comment











 













 PuppetDB /  PDB-431



  PR (839): Updated the 1.6.2 release notes - senior 







 h2. Updated the 1.6.2 release notes   * Author: Ryan Senior   * Company:   * Github ID: [senior|https://github.com/senior]  * [Pull Request 839 Discussion|https://github.com/puppetlabs/puppetdb/pull/839]  * [Pull Request 839 File Diff|https://github.com/puppetlabs/puppetdb/pull/839/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-1224) Invalid YAML (hiera) file and automatic param binding fails in vague errors

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-1224



  Invalid YAML (hiera) file and automatic param binding fails in vague errors 










Change By:

 Henrik Lindberg









 Hi,In my chain of hiera files I have an empty file. My manifests look as follows:  {code}   node 'example.com' {      include role::vps::hypervisor  }  class role::vps::hypervisor inherits role::vps {}  class role::vps inherits role {    }  class role {    include profile::base  }class profile::base (  $firewall = params_lookup('firewall', 'global' ),  $manage_networking = true) {      # Some code here }  {code }This results in the following error: {code} Error: Could not retrieve catalog from remote server: Error 400 on SERVER: undefined method `empty?' for false:FalseClass at role.pp:2 on node example.com {code}   Once I remove the parameters in the profile::base class, the error changes in to the little bit more helpful message:Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Data retrieved from /etc/puppet/hieradata/vps.yaml is String not Hash at /etc/puppet/modules/profile/manifests/base.pp:13 on node example.com.Two issues:   * I think an empty or invalid Hiera file should not result in an error at all.   * If, for whatever reason, automatic parameter binding fails, a reasonable error should be displayed. In the past I've seen (and reported) several issues where the binding failed, and resulted in some vague issues which are hard to debug.   Environment:* Parser: future (not sure if relevant)* Hiera version: 1.3.0   * Puppet version: 3.3.2   * OS: Debian 7, 64 bit   * Env: Passenger  I wouldn't classify the priority of this issue as low, because it's easy to trigger, and really hard to find the cause off the given error message.












   

 Add Comment











 










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




 


 

Jira (PDB-430) PR (838): Updated the 1.6.2 release notes - senior

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (838): Updated the 1.6.2 release notes - senior 










Pull request Updated the 1.6.2 release notes has been closed.












   

 Add Comment











 













 PuppetDB /  PDB-430



  PR (838): Updated the 1.6.2 release notes - senior 







 h2. Updated the 1.6.2 release notes   * Author: Ryan Senior   * Company:   * Github ID: [senior|https://github.com/senior]  * [Pull Request 838 Discussion|https://github.com/puppetlabs/puppetdb/pull/838]  * [Pull Request 838 File Diff|https://github.com/puppetlabs/puppetdb/pull/838/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 (PDB-430) PR (838): Updated the 1.6.2 release notes - senior

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (838): Updated the 1.6.2 release notes - senior 










senior commented:
Needed to target 1.6.x












   

 Add Comment











 













 PuppetDB /  PDB-430



  PR (838): Updated the 1.6.2 release notes - senior 







 h2. Updated the 1.6.2 release notes   * Author: Ryan Senior   * Company:   * Github ID: [senior|https://github.com/senior]  * [Pull Request 838 Discussion|https://github.com/puppetlabs/puppetdb/pull/838]  * [Pull Request 838 File Diff|https://github.com/puppetlabs/puppetdb/pull/838/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 (PDB-431) PR (839): Updated the 1.6.2 release notes - senior

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-431



  PR (839): Updated the 1.6.2 release notes - senior 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 06/Feb/14 9:37 AM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Updated the 1.6.2 release notes


Author: Ryan Senior 


Company:


Github ID: senior


Pull Request 839 Discussion


Pull Request 839 File Diff


Pull Request Description


(webhooks-id: 996a888545ce53be5031ba0d0ba7630e)









   

Jira (PUP-1224) Invalid YAML (hiera) file and automatic param binding fails in vague errors

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Invalid YAML (hiera) file and automatic param binding fails in vague errors 










Pancentric which version of Puppet are you observing this behavior on?












   

 Add Comment











 













 Puppet /  PUP-1224



  Invalid YAML (hiera) file and automatic param binding fails in vague errors 







 Hi,   In my chain of hiera files I have an empty file. My manifests look as follows:   node 'example.com' {        include role::vps::hypervisor   }class role::vps::hypervisor inherits role::vps {  }class role::vps inherits role {      }class role {     include profile::base   }   class profile::base (    $fire...















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




 














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

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-430



  PR (838): Updated the 1.6.2 release notes - senior 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 06/Feb/14 9:35 AM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Updated the 1.6.2 release notes


Author: Ryan Senior 


Company:


Github ID: senior


Pull Request 838 Discussion


Pull Request 838 File Diff


Pull Request Description


(webhooks-id: 4dced1d50222e5d78a5996621360a672)









   

Jira (PUP-1574) Using new directory environments with puppet apply prevents evaluation of the manifest requested on the commandline.

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow assigned an issue to Joshua Partlow











 






 Puppet /  PUP-1574



  Using new directory environments with puppet apply prevents evaluation of the manifest requested on the commandline. 










Change By:

 Joshua Partlow




Assignee:

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

Jira (PUP-649) PR (2024): (#3220) crontab: allow purging unmanaged resources - ffrank

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2024): (#3220) crontab: allow purging unmanaged resources - ffrank 










Sharpie commented:
 That's a good question. @zaphod42 @adrienthebo, in the PR triage we discussed pulling the changes to the `additional_resources_generator` and just letting the tests for cron and nagios (#2060) crash and burn so they could be fixed in a way that didn't involve this patch.
Is this the road we want to go down?












   

 Add Comment











 













 Puppet /  PUP-649



  PR (2024): (#3220) crontab: allow purging unmanaged resources - ffrank 







 h2. (#3220) crontab: allow purging unmanaged resources   * Author: <>  * Company:   * Github ID: [ffrank|https://github.com/ffrank]  * [Pull Request 2024 Discussion|https://github.com/puppetlabs/puppet/pull/2024]  * [Pull Request 2024 File Diff|https://github.com/puppetlabs/puppet/pull/2024/files]  h2. Pull Request Description   This pull was request...















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




 














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

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:
:red_circle: Test failed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/209/












   

 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

Jira (PUP-1224) Invalid YAML (hiera) file and automatic param binding fails in vague errors

[Pancentric (JIRA)]

Title: Message Title










 

 Pancentric commented on an issue











 






  Re: Invalid YAML (hiera) file and automatic param binding fails in vague errors 










This is an issue for us, too. 
We are refactoring into separate staging/live/dev environments where 'develop' was where all our machines were sat.  I've copied the 'develop' environment file for file to 'staging' and when I try to do a puppet run on a host in the 'staging' env, I get this:



Error: Could not retrieve catalog from remote server: Error 400 on SERVER: undefined method `empty?' for nil:NilClass at /etc/puppet/environments/staging/manifests/site.pp:3 on node as-staging-web.pancentric.net
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run















   

 Add Comment











 













 Puppet /  PUP-1224



  Invalid YAML (hiera) file and automatic param binding fails in vague errors 







 Hi,   In my chain of hiera files I have an empty file. My manifests look as follows:   node 'example.com' {        include role::vps::hypervisor   }class role::vps::hypervisor inherits role::vps {  }class role::vps inherits role {      }class role {     include profile::base   }   class profile::base (    $fire...















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

Jira (PUP-1545) PR (2310): Serialization revamp - dalen

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2310): Serialization revamp - dalen 










Pull request Serialization revamp has been closed.












   

 Add Comment











 













 Puppet /  PUP-1545



  PR (2310): Serialization revamp - dalen 







 h2. Serialization revamp   * Author: Erik Dalén   * Company: Spotify  * Github ID: [dalen|https://github.com/dalen]  * [Pull Request 2310 Discussion|https://github.com/puppetlabs/puppet/pull/2310]  * [Pull Request 2310 File Diff|https://github.com/puppetlabs/puppet/pull/2310/files]  h2. Pull Request Description   Do a bunc...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this 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-1430) PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen 










zaphod42 commented:
@dalen Have you had a chance to merge together the changes from this and GH-2223?












   

 Add Comment











 













 Puppet /  PUP-1430



  PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen 







 h2. Make SSL file permissions a bit more relaxed for public files   * Author: Erik Dalén   * Company: Spotify  * Github ID: [dalen|https://github.com/dalen]  * [Pull Request 2257 Discussion|https://github.com/puppetlabs/puppet/pull/2257]  * [Pull Request 2257 File Diff|https://github.com/puppetlabs/puppet/pull/2257/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.
F

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 










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












   

 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

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 










cprice404 commented:
@puppetlabs-jenkins retest this please












   

 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 (PDB-429) PR (837): v1 shared route refactor - senior

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (837): v1 shared route refactor - senior 










kbarber commented:
+1












   

 Add Comment











 













 PuppetDB /  PDB-429



  PR (837): v1 shared route refactor - senior 







 h2. v1 shared route refactor   * Author: Ryan Senior   * Company:   * Github ID: [senior|https://github.com/senior]  * [Pull Request 837 Discussion|https://github.com/puppetlabs/puppetdb/pull/837]  * [Pull Request 837 File Diff|https://github.com/puppetlabs/puppetdb/pull/837/files]  h2. Pull Request Description   This commit sta...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this 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-312) PR (802): Convert unit testing to use dynamic postgres instance - kbarber

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber assigned an issue to Unassigned











 







Un-assigning, looks like we're waiting on QA Infra now, so I'll monitor this ticket independently, but its blocked so no point keeping assignment. Branan Purvine-Riley I'll ping you again once the postgresql initial work is done so we can test this out and monitor the behaviour together.









 PuppetDB /  PDB-312



  PR (802): Convert unit testing to use dynamic postgres instance - kbarber 










Change By:

 Kenneth Barber




Assignee:

 Branan Purvine-Riley












   

 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 










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












   

 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

Jira (PDB-352) PR (814): Apply the RHEL7 work and merge it into 1.6.x - mckern

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (814): Apply the RHEL7 work and merge it into 1.6.x - mckern 










kbarber commented:
@mckern looks like this needs to be rebased and modified to just contain:


The build host change


The wording for docs


Since @haus already has merged in your RHEL 7 spec changes.












   

 Add Comment











 













 PuppetDB /  PDB-352



  PR (814): Apply the RHEL7 work and merge it into 1.6.x - mckern 







 h2. Apply the RHEL7 work and merge it into 1.6.x   * Author: Ryan McKern   * Company: Puppet Labs  * Github ID: [mckern|https://github.com/mckern]  * [Pull Request 814 Discussion|https://github.com/puppetlabs/puppetdb/pull/814]  * [Pull Request 814 File Diff|https://github.com/puppetlabs/puppetdb/pull/814/files]  h2. Pull Request Desc...















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




 


 

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 










cprice404 commented:
Added commits to get rid of commented code and add back in the l4j.props file.












   

 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 (PDB-312) PR (802): Convert unit testing to use dynamic postgres instance - kbarber

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (802): Convert unit testing to use dynamic postgres instance - kbarber 










kbarber commented:
This is blocked by infastructure changes required here: https://tickets.puppetlabs.com/browse/QA-825. Basically until we get postgresql binaries installed I can't test this. QA sound on board with the idea, so I think its just a matter of waiting.












   

 Add Comment











 













 PuppetDB /  PDB-312



  PR (802): Convert unit testing to use dynamic postgres instance - kbarber 







 h2. Convert unit testing to use dynamic postgres instance   * Author: Ken Barber   * Company: Puppetlabs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 802 Discussion|https://github.com/puppetlabs/puppetdb/pull/802]  * [Pull Request 802 File Diff|https://github.com/puppetlabs/puppetdb/pull/802/files]  h2. Pull Request...















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




 














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

Jira (PDB-312) PR (802): Convert unit testing to use dynamic postgres instance - kbarber

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: PR (802): Convert unit testing to use dynamic postgres instance - kbarber 










I've raised QA-825 for the infrastructure changes required.












   

 Add Comment











 













 PuppetDB /  PDB-312



  PR (802): Convert unit testing to use dynamic postgres instance - kbarber 







 h2. Convert unit testing to use dynamic postgres instance   * Author: Ken Barber   * Company: Puppetlabs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 802 Discussion|https://github.com/puppetlabs/puppetdb/pull/802]  * [Pull Request 802 File Diff|https://github.com/puppetlabs/puppetdb/pull/802/files]  h2. Pull Request...















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




 














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

Jira (PUP-1270) 'pkg' package provider does not understand IPS package versions properly

[Kylo Ginsberg (JIRA)]

Title: Message Title










 

 Kylo Ginsberg assigned an issue to Kylo Ginsberg











 






 Puppet /  PUP-1270



  'pkg' package provider does not understand IPS package versions properly 










Change By:

 Kylo Ginsberg




Assignee:

 Peter Huene Kylo Ginsberg












   

 Add Comment











 










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




 














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

Jira (PDB-427) PR (835): Packaging/1.5.x/update - MosesMendoza

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (835): Packaging/1.5.x/update - MosesMendoza 










kbarber commented:
@MosesMendoza let us know when you want to merge this, sounded like you want to merge something in lock-step with this, so let us know. It can go into 1.5.x any time, but we can't roll-up to 1.6.x until we tag it for the 1.6.2 release (hopefully Melissa will take care of this today).












   

 Add Comment











 













 PuppetDB /  PDB-427



  PR (835): Packaging/1.5.x/update - MosesMendoza 







 h2. Packaging/1.5.x/update   * Author: <>  * Company:   * Github ID: [MosesMendoza|https://github.com/MosesMendoza]  * [Pull Request 835 Discussion|https://github.com/puppetlabs/puppetdb/pull/835]  * [Pull Request 835 File Diff|https://github.com/puppetlabs/puppetdb/pull/835/files]  h2. Pull Request Description   This PR is primarily centered around ...















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




 














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

Jira (PDB-427) PR (835): Packaging/1.5.x/update - MosesMendoza

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (835): Packaging/1.5.x/update - MosesMendoza 










MosesMendoza commented:
@kbarber we're hoping to merge both this and https://github.com/puppetlabs/packaging/pull/237 on Monday 2/10 to give us time to fix any issues that pop up.












   

 Add Comment











 













 PuppetDB /  PDB-427



  PR (835): Packaging/1.5.x/update - MosesMendoza 







 h2. Packaging/1.5.x/update   * Author: <>  * Company:   * Github ID: [MosesMendoza|https://github.com/MosesMendoza]  * [Pull Request 835 Discussion|https://github.com/puppetlabs/puppetdb/pull/835]  * [Pull Request 835 File Diff|https://github.com/puppetlabs/puppetdb/pull/835/files]  h2. Pull Request Description   This PR is primarily centered around ...















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




 














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

Jira (PUP-1600) puppet node doesn't retrieve the environment params

[frederic ragot (JIRA)]

Title: Message Title










 

 frederic ragot created an issue











 






 Puppet /  PUP-1600



  puppet node doesn't retrieve the environment params 










Issue Type:

  Bug




Affects Versions:


 3.4.2




Assignee:

 Eric Sorenson




Created:


 06/Feb/14 8:28 AM




Environment:


CentOS release 6.5 (Final)




Priority:

  Normal




Reporter:

 frederic ragot










Hi,
According to http://docs.puppetlabs.com/guides/environment.html, I have defined a variable environment in my puppet dashboard.



# /usr/bin/env PUPPET_DASHBOARD_URL=http://localhost:3000 /usr/share/puppet-dashboard/bin/external_node mynode
---
name: mynode
parameters:
...
  environment: beta
...



I have configure my master : 



[main]
  ...
modulepath = $confdir/environments/$environment/modules:$confdir/modules

[master]
  ...

[production]
 modulepath = $confdir/modules



I have installed my module in the right env :