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

[Halt (JIRA)]

Title: Message Title










 

 Halt commented on an issue











 






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










It's missing not only from Amazon Linux AMI, the whole Debian family is also effected ( just with puppetlabs packages, the default repo packages are working well ) 












   

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

Jira (PDB-595) PuppetDB load testing script?

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-595



  PuppetDB load testing script? 










Change By:

 Kenneth Barber




Fix Version/s:

 2.0.0




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

Jira (PUP-2357) Validation missing for meaningless sequences

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Validation missing for meaningless sequences 










More rules:


All BinaryExpressions are idem except:


AssignmentExpression


RelationshipExpression




All UnaryExpressions are idem (e.g. UnaryMinusExpression, VariableExpression, NotExpression) except:


Epp render expressions


ParenthesizedExpression is idem if the _expression_ is contains is idem (this allows parentheses without effect for stylistic reasons)
















   

 Add Comment











 













 Puppet /  PUP-2357



  Validation missing for meaningless sequences 







 There is currently no validation of the future parser's result wrt. evaluation of meaningless sequences. If user enters:  {code}  1 2 3 hello goodbye  {code}  The evaluator will just "do what it is 

Jira (PUP-2357) Validation missing for meaningless sequences

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Validation missing for meaningless sequences 










Interpolated String, and Heredoc are both text producing, and while they may have interpolation of expressions that are not idem, they are still always considered idem as it is very bad form to rely on this side effect and throwing away the constructed string. 



"This is ${$a = 10} bad" # treated as idem, and flagged as error even if assignment is a side effect
$b = 10















   

 Add Comment











 













 Puppet /  PUP-2357



  Validation missing for meaningless sequences 







 There is currently no validation of the future parser's result wrt. evaluation of meaningless sequences. If user enters:  {code}  1 2 3 hello goodbye  {code}  The evaluator will just "do what it is told", and produce a 1, then a 2, etc.  The only place were a "side effect free" _expression_ may appear is as the last _expression_ in a sequence / block as this ...















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




 






 

Jira (PUP-2357) Validation missing for meaningless sequences

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Validation missing for meaningless sequences 










An IfExpression is idem if all of its three expressions; test, then_expression, and else_expression are idem












   

 Add Comment











 













 Puppet /  PUP-2357



  Validation missing for meaningless sequences 







 There is currently no validation of the future parser's result wrt. evaluation of meaningless sequences. If user enters:  {code}  1 2 3 hello goodbye  {code}  The evaluator will just "do what it is told", and produce a 1, then a 2, etc.  The only place were a "side effect free" _expression_ may appear is as the last _expression_ in a sequence / block as this ...















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




 














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

Jira (PUP-2182) Package resource not working as expected in 3.5.0

[Sean Edge (JIRA)]

Title: Message Title










 

 Sean Edge commented on an issue











 






  Re: Package resource not working as expected in 3.5.0 










Peter Huene No worries. I care less about this since I have the workaround of including the arch in the package name "jre.x86_64" and that does what I want/expect.
Yes, the openjdk package was already there, which was satisfying "jre" from a virtual package/whatprovides perspective. However, I want the package named "jre" specifically.



[root@fw ~]# rpm -q jre
jre-1.7.0_51-fcs.x86_64
[root@fw ~]# rpm -e jre
[root@fw ~]# rpm -q puppet
puppet-3.5.1-1.el6.noarch
[root@fw ~]# cat /tmp/test.pp
package { 'jre': ensure => 'latest' }
[root@fw ~]# puppet apply /tmp/test.pp
Notice: Compiled catalog for fw in environment production in 0.75 seconds
Notice: Finished catalog run in 1.69 seconds
[root@fw ~]# rpm -q --whatprovides jre
java-1.7.0-openjdk-1.7.0.51-2.4.4.1.el6_5.x86_64
[root@fw ~]# rpm -q jre
package jre is not installed



You are correct, "latest" is a local repo in which we combine many packages from various vendors for our deployments. We mirror CentOS, Puppetlabs, PostgreSQL, etc. repos using mrepo. The "jre" package we've had to manually download, since Oracle doesn't make it easy for us to mirror, from Oracle's site because we've recently switched to CentOS from RHEL and we'll no longer be able to use the RH packaged version of Oracle Java.
Option #3 sounds the most reasonable. It also has my vote. I can see how that could be a useful feature if you don't care what kind of JRE you get, you just want to ensure one is there.












   

 Add Comment











 













 Puppet /  PUP-2182



  Package resource not working as expected in 3.5.0 







 One of my modules has th

Jira (PUP-2357) Validation missing for meaningless sequences

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Validation missing for meaningless sequences 










More rules:


A CaseExpression is idem if its test, all values, and all option's then_expression are idem


A SelectorExpression is always idem - using a selector for its possible side effect and throwing away its produced value is bad design














   

 Add Comment











 













 Puppet /  PUP-2357



  Validation missing for meaningless sequences 







 There is currently no validation of the future parser's result wrt. evaluation of meaningless sequences. If user enters:  {code}  1 2 3 hello goodbye  {code}  The evaluator will just "do what it is told", and produce a 1, then a 2, etc.  The only place were a "side effect free" _expression_ may appear is as the last _expression_ in a sequence / block as this ...















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




 





  

Jira (PUP-2365) Puppet module tool on windows cannot connect to the forge

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper created an issue











 






 Puppet /  PUP-2365



  Puppet module tool on windows cannot connect to the forge 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 25/Apr/14 11:02 AM




Labels:


 windows




Priority:

  Normal




Reporter:

 Joshua Cooper










Due to heartbleed, operations obtained a wildcard SSL certificate issued by 


Issuer: C=US, ST=UT, L=Salt Lake City, O=The USERTRUST Network, OU=http://www.usertrust.com, CN=UTN-USERFirst-Hardware


 This certificate is not installed by default on Windows hosts, as a result the PMT cannot make an authenticated SSL connection to the forge:



C:\work\puppet [master +4 ~1 -0 !]> bundle exec puppet module search registry
Notice: Searching https://forgeapi.puppetlabs.com ...
Error: Could not connect via HTTPS to https://forgeapi.puppetlabs.com
  Unable to verify the SSL certificate
The certificate may not be signed by a valid CA
The CA bundle included with OpenSSL may not be valid or up to date
Error: Try 'puppet help module search' for usage



To workaround the issue, copy the following contents to a file named utn.pem


   

Jira (PUP-2365) Puppet module tool on windows cannot connect to the forge

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2365



  Puppet module tool on windows cannot connect to the forge 










Change By:

 Joshua Cooper









 Due to heartbleed, operations obtained a wildcard SSL certificate issued by {code}Issuer: C=US, ST=UT, L=Salt Lake City, O=The USERTRUST Network, OU=http://www.usertrust.com, CN=UTN-USERFirst-Hardware{code} This certificate is not installed by default on Windows hosts, as a result the PMT cannot make an authenticated SSL connection to the forge:{code}C:\work\puppet [master +4 ~1 -0 !]> bundle exec puppet module search registryNotice: Searching https://forgeapi.puppetlabs.com ...Error: Could not connect via HTTPS to https://forgeapi.puppetlabs.com  Unable to verify the SSL certificateThe certificate may not be signed by a valid CAThe CA bundle included with OpenSSL may not be valid or up to dateError: Try 'puppet help module search' for usage{code}To workaround the issue, copy the following contents to a file named utn.pem{ code noformat }-BEGIN CERTIFICATE-MIIEdDCCA1ygAwIBAgIQRL4Mi1AAJLQR0zYq/mUK/TANBgkqhkiG9w0BAQUFADCBlzELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xHzAdBgNVBAMTFlVUTi1VU0VSRmlyc3QtSGFyZHdhcmUwHhcNOTkwNzA5MTgxMDQyWhcNMTkwNzA5MTgxOTIyWjCBlzELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xHzAdBgNVBAMTFlVUTi1VU0VSRmlyc3QtSGFyZHdhcmUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCx98M4P7Sof885glFn0G2f0v9Y8+efK+wNiVSZuTiZFvfgIXlIwrthdBKWHTxqctU8EGc6Oe0rE81m65UJM6Rsl7HoxuzBdXmcRl6Nq9Bq/bkqVRcQVLMZ8Jr28bFdtqdt++BxF2uiiPsA3/4aMXcMmgF6sTLjKwEHOG7DpV4jvEWbe1DByTCP2+UretNb+zNAHqDVmBe8i4fDidNdoI6yqqr2jmmIBsX6iSHzCJ1pLgkzmykNRg+MzEk0sGlRvfkGzWitZky8PqxhvQqIDsjfPe58BEydCl5rkdbux+0ojatNh4lz0G6k0B4WixThdkQDf2Os5M1JnMWS9KsyoUhbAgMBAAGjgbkwgbYwCwYDVR0PBAQDAgHGMA8GA1UdEwEB/wQFMAMBAf8wHQYDVR0OBBYEFKFyXyYbKJhDlV0HN9WFlp1L0sNFMEQGA1UdHwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9VVE4tVVNFUkZpcnN0LUhhcmR3YXJlLmNybDAxBgNVHSUEKjAoBggrBgEFBQcDAQYIKwYBBQUHAwUGCCsGAQUFBwMGBggrBgEFBQcDBzANBgkqhkiG9w0BAQUFAAOCAQEARxkP3nTGmZev/K0oXnWO6y1n7k57K9cM//bey1WiCuFMVGWTYGufEpytXoMs61quwOQt9ABjHbjAbPLPSbtNk28GpgoiskliCE7/yMgUsogWXecB5BKV5UU0s4tpvc+0hY91UZ59Ojg6FEgSxvunOxqNDYJAB+gECJChicsZUN/KHAG8HQQZexB2lzvukJDKxA4fFm517zP4029bHpbj4HR3dHuKom4t3XbWOTCC8KucUvIqx69JXn7HaOWCgchqJ/kniCrVWFCVH/A7HFe7fRQ5YiuayZSSKqMiDP+JJn1fIytH1xUdqWqeUQ0qUZ6B+dQ7XnASfxAynB67nfhmqA==-END CERTIFICATE-{ code noformat }And execute as an administrator:{ code noformat }C:\> certutil -v -addstore Root utn.pemRootSignature matches Public KeyCertificate "CN=UTN-USERFirst-Hardware, OU=http://www.usertrust.com, O=The USERTRUST Network, L=Salt Lake City, S=UT, C=US" added to store.CertUtil: -addstore command completed successfully.{ code noformat }

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

[Kurt Wall (JIRA)]

Title: Message Title










 

 Kurt Wall commented on an issue











 






  Re: PR (2477) Multiple values for diff_args causes diff execution failure 










This bug is "pre-verified" in master at SHA=da4ecf4. After it passes CI, it can be moved directly to Resolved. Multiple args for diff_args does not cause an execution failure:



# x.pp
file { '/tmp/newfile':
	content => "\nhello\nworld\n"
}

# puppet config print show_diff diff_args
show_diff = true
diff_args = -u --strip-trailing-cr

# puppet apply x.pp --debug
[...]
Debug: Executing 'diff -u --strip-trailing-cr /tmp/newfile /tmp/puppet-file20140425-4009-vrmvy9-0'
Notice: /Stage[main]/Main/File[/tmp/newfile]/content: 
--- /tmp/newfile	2014-04-25 11:16:22.188633067 -0700
+++ /tmp/puppet-file20140425-4009-vrmvy9-0	2014-04-25 11:16:58.394053675 -0700
@@ -0,0 +1,3 @@
+
+hello
+world

Info: FileBucket got a duplicate file {md5}d41d8cd98f00b204e9800998ecf8427e
Info: /Stage[main]/Main/File[/tmp/newfile]: Filebucketed /tmp/newfile to puppet with sum d41d8cd98f00b204e9800998ecf8427e
Notice: /Stage[main]/Main/File[/tmp/newfile]/content: content changed '{md5}d41d8cd98f00b204e9800998ecf8427e' to '{md5}c8e130abb812b881b34c8b8a681074c6'















   

 Add Comment











 













 Puppet /  PUP-2073



  PR (2477) Multiple values for diff_args causes diff execution failure 







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

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

[Kurt Wall (JIRA)]

Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-2073



  PR (2477) Multiple values for diff_args causes diff execution failure 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall












   

 Add Comment











 










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




 














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

Jira (PUP-2365) Puppet module tool on windows cannot connect to the forge

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Puppet module tool on windows cannot connect to the forge 










Fixes to the acceptance setup step were made in stable eaf3d06 and in master 00ad563. However, the underlying issue remains.












   

 Add Comment











 













 Puppet /  PUP-2365



  Puppet module tool on windows cannot connect to the forge 







 Due to heartbleed, operations obtained a wildcard SSL certificate issued by {code}Issuer: C=US, ST=UT, L=Salt Lake City, O=The USERTRUST Network, OU=http://www.usertrust.com, CN=UTN-USERFirst-Hardware{code} This certificate is not installed by default on Windows hosts, as a result the PMT cannot make an authenticated SSL connection to the forge:   {code}...















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




 














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

Jira (PUP-2345) Upgrading from 3.4 to 3.5 causes Puppet to fail with "Could not evaluate: uninitialized constant Puppet::FileSystem::File"

[Stefan Lasiewski (JIRA)]

Title: Message Title










 

 Stefan Lasiewski commented on an issue











 






  Re: Upgrading from 3.4 to 3.5 causes Puppet to fail with "Could not evaluate: uninitialized constant Puppet::FileSystem::File" 










I'm not sure, but this might be a duplicate of PUP-1603 :
https://tickets.puppetlabs.com/browse/PUP-1603












   

 Add Comment











 













 Puppet /  PUP-2345



  Upgrading from 3.4 to 3.5 causes Puppet to fail with "Could not evaluate: uninitialized constant Puppet::FileSystem::File" 







 I am running a Scientific Linux 6.x system with Foreman and Puppet 3.4.   Yesterday I ran `yum update`. Afterwards, Puppet failed. Downgrading Puppet from 3.5 to 3.4 prevents the error, and is what I am doing for a workaround.   Steps to reproduce:   1. Notice that the error doesn't happen with Puppet 3.4   [root@puppetmaster ~]# puppet --version  3















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




 














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

Jira (PUP-1805) Drop Ruby 1.8.7 support

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1805



  Drop Ruby 1.8.7 support 










Change By:

 Charlie Sharpsteen




Epic Name:

 Depreciate 1.8.7












   

 Add Comment











 










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




 














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

Jira (PUP-1805) Drop Ruby 1.8.7 support

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1805



  Drop Ruby 1.8.7 support 










Change By:

 Charlie Sharpsteen




Issue Type:

 Improvement Epic












   

 Add Comment











 










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




 














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

Jira (PUP-2366) Replace hosts using Ruby 1.8.7 for Puppet 4.0 Acceptance

[Adrien Thebo (JIRA)]

Title: Message Title










 

 Adrien Thebo created an issue











 






 Puppet /  PUP-2366



  Replace hosts using Ruby 1.8.7 for Puppet 4.0 Acceptance 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 25/Apr/14 1:11 PM




Priority:

  Normal




Reporter:

 Adrien Thebo










Word on the street is that we're going to be dropping Ruby 1.8.7 support in Puppet 4.0. As part of this we need to remove all Acceptance builds on nodes that exclusively run Ruby 1.8.7 and cannot be switched to run Ruby 1.9.3.












   

 Add Comment











 










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




 

Jira (PUP-1805) Drop Ruby 1.8.7 support

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1805



  Drop Ruby 1.8.7 support 










Change By:

 Charlie Sharpsteen




Epic Name:

 Depreciate Deprecate  1.8.7












   

 Add Comment











 










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




 














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

Jira (PUP-2047) Create branch and update CI for Puppet 4

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen assigned an issue to Charlie Sharpsteen











 






 Puppet /  PUP-2047



  Create branch and update CI for Puppet 4 










Change By:

 Charlie Sharpsteen




Assignee:

 Charlie Sharpsteen












   

 Add Comment











 










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




 














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

Jira (PUP-2338) ACL silently fails on symlinks

[Ethan Brown (JIRA)]

Title: Message Title










 

 Ethan Brown assigned an issue to Ethan Brown











 






 Puppet /  PUP-2338



  ACL silently fails on symlinks 










Change By:

 Ethan Brown




Assignee:

 Ethan Brown












   

 Add Comment











 










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




 














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

Jira (PUP-2287) Lambda with default valued parameter cannot be overridden

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg updated an issue











 






 Puppet /  PUP-2287



  Lambda with default valued parameter cannot be overridden 










Change By:

 Henrik Lindberg









 If a default value is given for a lambdas parameter it will not be overridden by a given value.   The logic in  runtime3  evaluator_impl  L 209-217   {code}     given_argument = m[1]     argument_name = m[0].name     default_expression = m[0].value     value = if default_expression   evaluate(default_expression, scope)     else   given_argument     end   {code}   is where it goes wrong.   It should check if a value was given, and if that value is nil or undef, or no value given before using the default _expression_. m.size == 2 indicates that value was given.   The impact of this is minimal since all current functions that use lambdas would typically not use default values. Once lambdas spread beyond the current handful of function this will naturally bite people badly.   Suggest fixing this for 3.6.












   

 Add Comment











 










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




 














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

Jira (PDB-602) PR (947): Updated acceptance tests to use a proper release of leiningen - senior

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-602



  PR (947): Updated acceptance tests to use a proper release of leiningen - senior 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 25/Apr/14 2:57 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Updated acceptance tests to use a proper release of leiningen


Author: Ryan Senior 


Company:


Github ID: senior


Pull Request 947 Discussion


Pull Request 947 File Diff


Pull Request Description


(webhooks-id: 0be555de61efdeef26349fc525bc38aa)







 

Jira (PUP-2367) Puppet master service dies on SIGHUP

[Timur Alperovich (JIRA)]

Title: Message Title










 

 Timur Alperovich created an issue











 






 Puppet /  PUP-2367



  Puppet master service dies on SIGHUP 










Issue Type:

  Bug




Affects Versions:


 3.5.1, 3.5.0




Assignee:


 Unassigned




Created:


 25/Apr/14 3:20 PM




Environment:


Ubuntu 12.04




Priority:

  Normal




Reporter:

 Timur Alperovich










Puppet master service dies when receives a SIGHUP. This only happens if puppet is run as root. Running puppet master as root with --debug and --no-daemonize shows the actual error: Notice: Starting Puppet master version 3.5.0 Notice: Caught HUP; calling restart Notice: Restarting with '/usr/bin/puppet master --masterport=8140 --debug --no-daemonize' /usr/lib/ruby/vendor_ruby/facter/util/directory_loader.rb:75:in `open': Permission denied - /root/.facter/facts.d (Errno::EACCES) from /usr/lib/ruby/vendor_ruby/facter/util/directory_loader.rb:75:in `entries' from /usr/lib/ruby/vendor_ruby/facter/util/directory_loader.rb:75:in `entries' from /usr/lib/ruby/vendor_ruby/facter/util/directory_loader.rb:55:in `load' from /usr/lib/ruby/vendor_ruby/facter/util/composite_loader.rb:10:in `block in load' from /usr/lib/ruby/vendor_ruby/facter/util/composite_loader.rb:10:in `each' from /usr/lib/ruby/vendor_ruby/facter/util/composite_loader.rb:10:in `load' from /usr/lib/ruby/vendor_ruby/facter/util/collection.rb:158:in `load_external_facts' from /usr/lib/ruby/vendor_ruby/facter/util/collection.rb:99:in `load' from /usr/lib/ruby/vendor_ruby/facter/util/collection.rb:73:in 

Jira (PUP-1109) Convert puppet startup script to upstart

[Timur Alperovich (JIRA)]

Title: Message Title










 

 Timur Alperovich commented on an issue











 






  Re: Convert puppet startup script to upstart 










We have implemented two upstart scripts for puppet and puppet master internally. I'm adding them to the bug in case these prove to be useful:



description "puppet agent"

start on runlevel [2345]
stop on runlevel [!2345]

# Workaround (as suggested here: https://projects.puppetlabs.com/issues/22848)
env LANG="en_US.UTF-8"

respawn

script
  . /etc/default/puppet
  [ "$START" = "yes" ] || exit 0
  # Check if the certname is set 
  cert=`sed -n -e '/\[agent\]/,/certname.*/{ s/.*certname=\(.*\)/\1/;
   t match; d; :match p; }' /etc/puppet/puppet.conf`
  if [ -z $cert ]; then
echo "Certname is not set!"
exit 1
  fi  
  exec /usr/bin/puppet agent --no-daemonize $DAEMON_OPTS
end script






description "puppet master"

start on runlevel [2345]
stop on runlevel [!2345]

# Workaround (as suggested here: https://projects.puppetlabs.com/issues/22848)
env LANG="en_US.UTF-8"

respawn

script
  . /etc/default/puppetmaster
  [ "$START" = "yes" ] || exit 0
  # Check if the certname is set 
  cert=`sed -n -e '/\[master\]/,/certname.*/{ s/.*certname=\(.*\)/\1/;
   t match; d; :match p; }' /etc/puppet/puppet.conf`
  if [ -z $cert ]; then
echo "Certname is not set!"
exit 1
  fi  
  exec /usr/bin/puppet master --no-daemonize $DAEMON_OPTS --masterport=$PORT
end script















   

 Add Comment











 













 Puppet /  PUP-1109



  Convert puppet startup script to upstart 







 May be a "won't-fix", but converting puppet init.d scripts to upstart has significant b

Jira (PDB-600) Create docs indexes for environments end-point and benchmark docs

[Ryan Senior (JIRA)]

Title: Message Title










 

 Ryan Senior updated an issue











 






 PuppetDB /  PDB-600



  Create docs indexes for environments end-point and benchmark docs 










Change By:

 Ryan Senior




Sprint:

 20140423 to 20140507












   

 Add Comment











 










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




 














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

Jira (PDB-600) Create docs indexes for environments end-point and benchmark docs

[Ryan Senior (JIRA)]

Title: Message Title










 

 Ryan Senior updated an issue











 






 PuppetDB /  PDB-600



  Create docs indexes for environments end-point and benchmark docs 










Change By:

 Ryan Senior




Sprint:

 20140423 to 20140507












   

 Add Comment











 










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




 














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

Jira (PDB-602) PR (947): Updated acceptance tests to use a proper release of leiningen - senior

[Ryan Senior (JIRA)]

Title: Message Title










 

 Ryan Senior updated an issue











 






 PuppetDB /  PDB-602



  PR (947): Updated acceptance tests to use a proper release of leiningen - senior 










Change By:

 Ryan Senior




Sprint:

 20140423 to 20140507












   

 Add Comment











 










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




 














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

Jira (PDB-602) PR (947): Updated acceptance tests to use a proper release of leiningen - senior

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (947): Updated acceptance tests to use a proper release of leiningen - senior 










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












   

 Add Comment











 













 PuppetDB /  PDB-602



  PR (947): Updated acceptance tests to use a proper release of leiningen - senior 







 h2. Updated acceptance tests to use a proper release of leiningen   * Author: Ryan Senior   * Company:   * Github ID: [senior|https://github.com/senior]  * [Pull Request 947 Discussion|https://github.com/puppetlabs/puppetdb/pull/947]  * [Pull Request 947 File Diff|https://github.com/puppetlabs/puppetdb/pull/947/files]  h2. Pull Requ...















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




 














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

Jira (PUP-2344) Functions unable to call functions in different modules

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Functions unable to call functions in different modules 










Merged to master 7a35a89












   

 Add Comment











 













 Puppet /  PUP-2344



  Functions unable to call functions in different modules 







 With two modules, a and b, and one function in each module, a::func1 and b::func2, it doesn't seem possible for a::func1 to make a call to b::func2.   It needs to be possible with the new function API and the new loader system for function calls between modules to take place. The new loaders try to limit the visibility of modules so that they can more st...















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




 














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

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

[Francois Conil (JIRA)]

Title: Message Title










 

 Francois Conil assigned an issue to Unassigned











 






 Puppet /  PUP-2348



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










Change By:

 Francois Conil




Assignee:

 Francois Conil












   

 Add Comment











 










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




 














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