Jira (PUP-2290) ca_server and directory based environments don't play nice together

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: ca_server and directory based environments don't play nice together 










Merged into master in 524f55.
Because directory environments add the requirement that any environment has to exist to be used, the only thing we can do for this is to provide a warning to the user that a request failed because the master couldn't find the environment.












   

 Add Comment











 













 Puppet /  PUP-2290



  ca_server and directory based environments don't play nice together 







 When a Puppet Master is stared and is a CA but does not have any environments in {{/etc/puppet/environments}} even though it is configured for directory based environments it stops accepting CSR's.   We have a Puppet Master that is CA-only and therefor don't deploy the environments to it. The fix was to simply remove the {{environmentpath}} setting from ...















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




 














-- 
You received this message because 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...@googlegrou

Jira (PUP-2290) ca_server and directory based environments don't play nice together

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker assigned an issue to Andy Parker











 






 Puppet /  PUP-2290



  ca_server and directory based environments don't play nice together 










Change By:

 Andy Parker




Assignee:

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

Jira (PUP-2177) PR (2494) Insecure shipped Cipher settings in Passenger example config

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker updated an issue











 






 Puppet /  PUP-2177



  PR (2494) Insecure shipped Cipher settings in Passenger example config  










Change By:

 Andy Parker




Fix Version/s:

 3.6.0




Fix Version/s:

 3.7.0












   

 Add Comment











 










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




 














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

Jira (PUP-1840) Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts 










Merged into master in 282837












   

 Add Comment











 













 Puppet /  PUP-1840



  Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts 







 I'm using Puppet in part to ensure [Federal Information Processing Standard 140-2](http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf) (FIPS 140-2) compliance on my network. Part of this compliance for the system underlying Puppet is to make sure that only [FIPS Approved](http://csrc.nist.gov/publications/fips/fips140-2/fips1402annexa.pdf) algo...















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




 














-- 
You received this message because 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-1699) Cache environments

[Andy Parker (JIRA)]

Title: Message Title










 

 Andy Parker commented on an issue











 






  Re: Cache environments 










Merged fixes for incorrect configured environment into master in e61fa4












   

 Add Comment











 













 Puppet /  PUP-1699



  Cache environments 







 Currently, the new directory environments are not cached - each catalog compilation will start from scratch and reparse all puppet manifests and reload types.   This can be solved by caching the result. A naive implementation that never evicts anything proved this to have a positive effect, bringing down the execution time to about 50% of the first compi...















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




 














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

Jira (PDB-626) PR (956): Updated the release notes for the 2.0.0 release - senior

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (956): Updated the release notes for the 2.0.0 release - senior 










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












   

 Add Comment











 













 PuppetDB /  PDB-626



  PR (956): Updated the release notes for the 2.0.0 release - senior 







 h2. Updated the release notes for the 2.0.0 release   * Author: Ryan Senior   * Company:   * Github ID: [senior|https://github.com/senior]  * [Pull Request 956 Discussion|https://github.com/puppetlabs/puppetdb/pull/956]  * [Pull Request 956 File Diff|https://github.com/puppetlabs/puppetdb/pull/956/files]  h2. Pull Request Descriptio...















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




 














-- 
You received this message because 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 htt

Jira (PDB-626) PR (956): Updated the release notes for the 2.0.0 release - senior

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (956): Updated the release notes for the 2.0.0 release - senior 










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












   

 Add Comment











 













 PuppetDB /  PDB-626



  PR (956): Updated the release notes for the 2.0.0 release - senior 







 h2. Updated the release notes for the 2.0.0 release   * Author: Ryan Senior   * Company:   * Github ID: [senior|https://github.com/senior]  * [Pull Request 956 Discussion|https://github.com/puppetlabs/puppetdb/pull/956]  * [Pull Request 956 File Diff|https://github.com/puppetlabs/puppetdb/pull/956/files]  h2. Pull Request Descriptio...















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




 














-- 
You received this message because 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 htt

Jira (PDB-625) PR (955): Fix environment end-point links to be compatible with our docs site - kbarber

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (955): Fix environment end-point links to be compatible with our docs site - kbarber 










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












   

 Add Comment











 













 PuppetDB /  PDB-625



  PR (955): Fix environment end-point links to be compatible with our docs site - kbarber 







 h2. Fix environment end-point links to be compatible with our docs site   * Author: Ken Barber   * Company: Puppet Labs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 955 Discussion|https://github.com/puppetlabs/puppetdb/pull/955]  * [Pull Request 955 File Diff|https://github.com/puppetlabs/puppetdb/pull/955/files]  h...















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




 














-- 
You received this message because 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-bug

Jira (PUP-2382) Standardize existing FFI code and refactor where necessary

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2382



  Standardize existing FFI code and refactor where necessary 










Change By:

 Joshua Cooper




Summary:

 FFI  Standardize existing  FFI code  and refactor where necessary












   

 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-625) PR (955): Fix environment end-point links to be compatible with our docs site - kbarber

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (955): Fix environment end-point links to be compatible with our docs site - kbarber 










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












   

 Add Comment











 













 PuppetDB /  PDB-625



  PR (955): Fix environment end-point links to be compatible with our docs site - kbarber 







 h2. Fix environment end-point links to be compatible with our docs site   * Author: Ken Barber   * Company: Puppet Labs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 955 Discussion|https://github.com/puppetlabs/puppetdb/pull/955]  * [Pull Request 955 File Diff|https://github.com/puppetlabs/puppetdb/pull/955/files]  h...















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




 














-- 
You received this message because 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-bu

Jira (PDB-625) PR (955): Fix environment end-point links to be compatible with our docs site - kbarber

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (955): Fix environment end-point links to be compatible with our docs site - kbarber 










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












   

 Add Comment











 













 PuppetDB /  PDB-625



  PR (955): Fix environment end-point links to be compatible with our docs site - kbarber 







 h2. Fix environment end-point links to be compatible with our docs site   * Author: Ken Barber   * Company: Puppet Labs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 955 Discussion|https://github.com/puppetlabs/puppetdb/pull/955]  * [Pull Request 955 File Diff|https://github.com/puppetlabs/puppetdb/pull/955/files]  h...















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




 














-- 
You received this message because 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-bug

Jira (PUP-2389) Create ruby 2.x branches for x86 and x64 in puppet-win32-ruby

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper created an issue











 






 Puppet /  PUP-2389



  Create ruby 2.x branches for x86 and x64 in puppet-win32-ruby 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 29/Apr/14 3:53 PM




Fix Versions:


 4.0.0




Labels:


 windows




Priority:

  Normal




Reporter:

 Joshua Cooper










We need to vendor x86 and x64 versions of ruby 2.x, and install the appropriate sets of gems into both branches.












   

 Add Comment











 

   

Jira (PUP-2388) Update git setup steps to install architecture specific version of ruby

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper created an issue











 






 Puppet /  PUP-2388



  Update git setup steps to install architecture specific version of ruby 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 29/Apr/14 3:49 PM




Priority:

  Normal




Reporter:

 Joshua Cooper










Puppet's acceptance setup step for git will need to install the appropriate version of ruby based on the agent's architecture. See https://github.com/puppetlabs/puppet/blob/3.5.1/acceptance/setup/git/pre-suite/000_EnvSetup.rb#L41-L43
Beaker's install_from_git method accepts a :rev parameter so it should be possible to specify the revision to checkout, e.g. 2.0-x86 vs 2.0-x64.












   

 Add Comment











 










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



 

Jira (PDB-625) PR (955): Fix environment end-point links to be compatible with our docs site - kbarber

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (955): Fix environment end-point links to be compatible with our docs site - kbarber 










Pull request Fix environment end-point links to be compatible with our docs site has been closed.












   

 Add Comment











 













 PuppetDB /  PDB-625



  PR (955): Fix environment end-point links to be compatible with our docs site - kbarber 







 h2. Fix environment end-point links to be compatible with our docs site   * Author: Ken Barber   * Company: Puppet Labs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 955 Discussion|https://github.com/puppetlabs/puppetdb/pull/955]  * [Pull Request 955 File Diff|https://github.com/puppetlabs/puppetdb/pull/955/files]  h...















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




 














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

Jira (PDB-626) PR (956): Updated the release notes for the 2.0.0 release - senior

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (956): Updated the release notes for the 2.0.0 release - senior 










Pull request Updated the release notes for the 2.0.0 release has been closed.












   

 Add Comment











 













 PuppetDB /  PDB-626



  PR (956): Updated the release notes for the 2.0.0 release - senior 







 h2. Updated the release notes for the 2.0.0 release   * Author: Ryan Senior   * Company:   * Github ID: [senior|https://github.com/senior]  * [Pull Request 956 Discussion|https://github.com/puppetlabs/puppetdb/pull/956]  * [Pull Request 956 File Diff|https://github.com/puppetlabs/puppetdb/pull/956/files]  h2. Pull Request Descriptio...















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




 














-- 
You received this message because 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-626) PR (956): Updated the release notes for the 2.0.0 release - senior

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-626



  PR (956): Updated the release notes for the 2.0.0 release - senior 










Change By:

 Kenneth Barber




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 (PUP-2387) Remove users, specifically AD-LDAP, do not have their home directories created with managehome set to true

[Rob Nelson (JIRA)]

Title: Message Title










 

 Rob Nelson created an issue











 






 Puppet /  PUP-2387



  Remove users, specifically AD-LDAP, do not have their home directories created with managehome set to true 










Issue Type:

  Bug




Affects Versions:


 3.5.1




Assignee:

 Kylo Ginsberg




Attachments:


 user resource bug.txt




Components:


 Types and Providers




Created:


 29/Apr/14 3:34 PM




Environment:


CentOS 6.5 nodes joined to an AD/LDAP domain via sssd configuration




Labels:


 puppetlabs-mcollective user




Priority:

  Normal




Reporter:

 Rob Nelson










I am attempting to add c

Jira (PDB-625) PR (955): Fix environment end-point links to be compatible with our docs site - kbarber

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-625



  PR (955): Fix environment end-point links to be compatible with our docs site - kbarber 










Change By:

 Kenneth Barber




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-626) PR (956): Updated the release notes for the 2.0.0 release - senior

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-626



  PR (956): Updated the release notes for the 2.0.0 release - senior 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 29/Apr/14 3:14 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Updated the release notes for the 2.0.0 release


Author: Ryan Senior 


Company:


Github ID: senior


Pull Request 956 Discussion


Pull Request 956 File Diff


Pull Request Description


(webhooks-id: 9b3f2e4c11b2c59d9f016aef5965b8d3)

Jira (PUP-2386) Puppet Package Acceptance provides the equivalent of a manual smoke test.

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow updated an issue











 






 Puppet /  PUP-2386



  Puppet Package Acceptance provides the equivalent of a manual smoke test. 










Change By:

 Joshua Partlow









 As a first pass, the most time will be saved by taking care of using Puppet's service scripts for starting and stopping puppet master...so PUP-408, PUP-409, PUP-417 will cover all unix smoke testing.  Leaving windows manual until the MSI packaging is handled.I'm not sure if we smoke test solaris at all?












   

 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-625) PR (955): Fix environment end-point links to be compatible with our docs site - kbarber

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (955): Fix environment end-point links to be compatible with our docs site - kbarber 










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












   

 Add Comment











 













 PuppetDB /  PDB-625



  PR (955): Fix environment end-point links to be compatible with our docs site - kbarber 







 h2. Fix environment end-point links to be compatible with our docs site   * Author: Ken Barber   * Company: Puppet Labs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 955 Discussion|https://github.com/puppetlabs/puppetdb/pull/955]  * [Pull Request 955 File Diff|https://github.com/puppetlabs/puppetdb/pull/955/files]  h...















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




 














-- 
You received this message because 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-bu

Jira (PUP-408) Puppet package acceptance is sufficient for a smoke test

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow updated an issue











 






 Puppet /  PUP-408



  Puppet package acceptance is sufficient for a smoke test 










Change By:

 Joshua Partlow









 The current version of the package acceptance test jobs for Puppet does not sufficiently cover what we have been checking for smoke tests.Looking at the list of tests from PP-364, the points we are missing are:* The ability to test the msi packages on vcloud windows templates* A Beaker that uses the service scripts for starting and stopping puppet master*  A test that checks puppet agent service scripts?*  An acceptance test for puppetmaster-passenger on Debian* Man tests for puppet and facterAgent runs, pid file locks, logging are all covered by various acceptence tests.












   

 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-2386) Puppet Package Acceptance provides the equivalent of a manual smoke test.

[Joshua Partlow (JIRA)]

Title: Message Title










 

 Joshua Partlow created an issue











 






 Puppet /  PUP-2386



  Puppet Package Acceptance provides the equivalent of a manual smoke test. 










Issue Type:

  Epic




Assignee:


 Unassigned




Created:


 29/Apr/14 2:18 PM




Priority:

  Normal




Reporter:

 Joshua Partlow












   

 Add Comment











 










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




 














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

Jira (PUP-838) FFI Puppet::Util::Windows::Process module

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-838



  FFI Puppet::Util::Windows::Process module 










Change By:

 Joshua Cooper









 This code was already FFI'ed awhile ago, but there are refactors remaining, such as relying on common DWORD definitions, and function declarations, e.g. CloseHandle .












   

 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-1760) Update win32-security gem to latest (after string_to_sid fix)

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1760



  Update win32-security gem to latest (after string_to_sid fix) 










Change By:

 Joshua Cooper




Issue Type:

 New Feature Task












   

 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-392) Validate win32 gems on x64

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-392



  Validate win32 gems on x64 










Change By:

 Joshua Cooper









 Some of the win32 gems that we use contain native code and will need to be validated that they run on x64 systems.  In many cases, we can eliminate the need for Some  The current set  of  gems is in https://github.com/puppetlabs/puppet/blob/master/ext/project_data.yaml. It currently includes{code}  ffi: '1.9.0'  sys-admin: '1.5.6'  win32-api: '1.4.8'  win32-dir: '~> 0.4.3'  win32-eventlog: '~> 0.5.3'  win32-process: '~> 0.6.5'  win32-security: '~> 0.1.4'  win32-service: '0.7.2'  win32-taskscheduler: '~> 0.2.2'  win32console:  '1.3.2'  windows-api: '~> 0.4.2'  windows-pr: '~> 1.2.2'  minitar: '~> 0.5.4'{code}First step is to audit  the  list of  gems  use  and make sure we are using  ffi  for making native calls, but others don ' t ed versions .  For example, PUP-1760 and PUP-1283.Second is to verify the gems work on both x86 and x64 platforms.Finally, some gems may no longer needed, e.g. win32-process, and removed from puppet-win32-ruby and project_data.yaml due to FFI'ing of puppet code (PUP-838)












   

 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-1283) Update win32-service gem

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1283



  Update win32-service gem 










Change By:

 Joshua Cooper




Issue Type:

 Bug Task












   

 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-392) Validate win32 gems on x64

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-392



  Validate win32 gems on x64 










Change By:

 Joshua Cooper




Summary:

 Validate /patch  win32 gems on x64












   

 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-392) Validate/patch win32 gems on x64

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-392



  Validate/patch win32 gems on x64 










Change By:

 Joshua Cooper









 Some of the win32 gems that we use contain native code and will need to be validated that they run on x64 systems.  In many cases, we can eliminate the need for  Some of the gems use ffi for making native calls, but others don't .












   

 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-1281) Remove win32console gem in ruby 2.0 on windows

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1281



  Remove win32console gem in ruby 2.0 on windows 










Change By:

 Joshua Cooper




Issue Type:

 Bug Task












   

 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-390) Modify build process to generate x86 and x64 versions of ruby

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-390



  Modify build process to generate x86 and x64 versions of ruby 










Change By:

 Joshua Cooper




Issue Type:

 New Feature Task












   

 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-392) Validate/patch win32 gems on x64

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-392



  Validate/patch win32 gems on x64 










Change By:

 Joshua Cooper




Issue Type:

 New Feature Task












   

 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-391) Validate FFI'ed native windows code against Ruby 2 x64

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-391



  Validate FFI'ed native windows code against Ruby 2 x64 










Change By:

 Joshua Cooper




Issue Type:

 New Feature Task












   

 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-391) Validate FFI'ed native windows code against Ruby 2 x64

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-391



  Validate FFI'ed native windows code against Ruby 2 x64 










Change By:

 Joshua Cooper




Summary:

 Update Validate FFI'ed  native windows code  to support  against Ruby 2  x64












   

 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-840) FFI Puppet::Util::Colors module

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-840



  FFI Puppet::Util::Colors module 










Change By:

 Joshua Cooper









 In order to maintain compatibility with ruby 1.9.x, this ticket is about FFI'ing the {{Puppet::Util::Colors}} module, so use FFI instead of:{code}WriteConsole = Win32API.new( "kernel32", "WriteConsoleW", ['l', 'p', 'l', 'p', 'p'], 'l' ){code}We should always prefer wide character APIs, and not make assumptions about pointer lengths:{code}  lpNumberOfCharsWritten = ' ' * 4{code}Note that none of this code is needed in ruby 2.x, since that ruby version correctly handles unicode characters (such as those used by the puppet module tool), and translation of ANSI escape sequences to the Windows console API. See PUP-1281 for more information.












   

 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-2385) FFI Puppet::Util::Windows::File4.0. module

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper created an issue











 






 Puppet /  PUP-2385



  FFI Puppet::Util::Windows::File4.0. module 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 29/Apr/14 1:26 PM




Fix Versions:


 4.0.0




Labels:


 windows




Priority:

  Normal




Reporter:

 Joshua Cooper










Need to FFI move_file_ex using MoveFileExW, and refactor common function declarations, e.g. CreateFileW.












   

 Add Comment











 


 

Jira (PUP-2385) FFI Puppet::Util::Windows::File module

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2385



  FFI Puppet::Util::Windows::File module 










Change By:

 Joshua Cooper




Summary:

 FFI Puppet::Util::Windows:: File4.0. File  module












   

 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-625) PR (955): Fix environment end-point links to be compatible with our docs site - kbarber

[gepetto-bot (JIRA)]

Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-625



  PR (955): Fix environment end-point links to be compatible with our docs site - kbarber 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 29/Apr/14 1:24 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Fix environment end-point links to be compatible with our docs site


Author: Ken Barber 


Company: Puppet Labs Inc.


Github ID: kbarber


Pull Request 955 Discussion


Pull Request 955 File Diff


Pull Request Description

The links in the environments end-point weren't compatible with the markdown that our docs site uses. This patch fixes the links to be compatible.
Signed-off-by: Ken Barber 

(web

Jira (PUP-839) FFI Puppet::Util::Windows::Security module

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-839



  FFI Puppet::Util::Windows::Security module 










Change By:

 Joshua Cooper









 Use FFI to define and invoke Windows APIs. Always call the wide-version, where applicable, e.g. CreateFileW. Also don't do things like:{code}  def supports_acl?(path)flags = 0.chr * 4{code}












   

 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-838) FFI Puppet::Util::Windows::Process module

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-838



  FFI Puppet::Util::Windows::Process module 










Change By:

 Joshua Cooper









 This code was already FFI'ed awhile ago, but there are refactors remaining, such as relying on common DWORD definitions, and function declarations, e.g. CloseHandle












   

 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-2384) Puppet agent does not pick up changes in /etc/resolv.conf

[Rick Renshaw (JIRA)]

Title: Message Title










 

 Rick Renshaw created an issue











 






 Puppet /  PUP-2384



  Puppet agent does not pick up changes in /etc/resolv.conf 










Issue Type:

  Bug




Affects Versions:


 3.x




Assignee:

 Andy Parker




Components:


 Networking Services, PE




Created:


 29/Apr/14 1:18 PM




Environment:


Linux x86_64




Priority:

  Normal




Reporter:

 Rick Renshaw










Puppet agent does not change the DNS resolver it uses when /etc/resolv.conf changes.
Workaround is restart pe-puppet service on changes.












   

 Add Comment

 

Jira (PUP-837) FFI Puppet::Util::Windows::SID module

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-837



  FFI Puppet::Util::Windows::SID module 










Change By:

 Joshua Cooper









 Use FFI to define and invoke Windows APIs. Always call the wide-version, where applicable, e.g. ConvertStringSidtoSidW. Also don't do things like:{code}strncpy(sid_buf, str_ptr.unpack('L')[0], sid_buf.size - 1)sid_buf[sid_buf.size - 1] = 0.chrreturn sid_buf.strip{code}












   

 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-836) FFI Puppet::Util::Windows::User module

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-836



  FFI Puppet::Util::Windows::User module 










Change By:

 Joshua Cooper









 Use FFI to invoke wide-character versions of the Windows APIs, e.g. CreateWellKnownSid, etc. Also don't do things like:{code}sid = 0.chr * 80size = [80].pack('L')member = 0.chr * 4{code}












   

 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-836) FFI Puppet::Util::Windows::User module

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-836



  FFI Puppet::Util::Windows::User module 










Change By:

 Joshua Cooper









 Use FFI to  define and  invoke  wide-character versions of the  Windows APIs . Always call the wide-version ,  where applicable,  e.g.  CreateWellKnownSid, etc  LogonUserW . Also don't do things like:{code}sid = 0.chr * 80size = [80].pack('L')member = 0.chr * 4{code}












   

 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-2382) FFI Standardize existing and refactor where necessary

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2382



  FFI Standardize existing and refactor where necessary 










Change By:

 Joshua Cooper









 We need to standardize on how windows types, e.g. DWORD, HANDLE, etc are represented in FFI, and refactor places where duplicate methods are defined, e.g. CloseHandle, etc. 












   

 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-835) FFI native windows code

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-835



  FFI native windows code 










Change By:

 Joshua Cooper




Issue Type:

 Bug Task












   

 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-2371) Truthiness and nullness

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: Truthiness and nullness 










Ah. PUP-2368 is indeed a separate issue, but the cause is very similar to PUP-1967.












   

 Add Comment











 













 Puppet /  PUP-2371



  Truthiness and nullness 







 Puppet's definition of what is truly True, False or Nil is completely insane. Now that Puppet 4 has opened up I think it's a good time to fix this, once and for all.   The problem has recently hit me in Types and Providers where trying to use Boolean parameters and properties is just impossible because the RAL in a lot of places checks for truthiness ins...















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




 














-- 
You received this message because 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-2371) Truthiness and nullness

[Charlie Sharpsteen (JIRA)]

Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: Truthiness and nullness 










Linked in PUP-1967 which is an older issue that PUP-2368 duplicates. The root cause of failure in defaultto false is that Puppet checks the hash of defaults for truthiness where the design of the code is assuming a check for nil (no default defined). Thus a default value of false gets treated the same as nil (no default).












   

 Add Comment











 













 Puppet /  PUP-2371



  Truthiness and nullness 







 Puppet's definition of what is truly True, False or Nil is completely insane. Now that Puppet 4 has opened up I think it's a good time to fix this, once and for all.   The problem has recently hit me in Types and Providers where trying to use Boolean parameters and properties is just impossible because the RAL in a lot of places checks for truthiness ins...















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




 














-- 
You received this message because 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-2380) autoloading provider fails at random

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: autoloading provider fails at random 










Hi Daniele Sluijters can you run the master with --debug --trace and paste the output into the ticket?












   

 Add Comment











 













 Puppet /  PUP-2380



  autoloading provider fails at random 







 I recently wrote a provider which works just fine in all my tests but when running it in our production environment it will fail at random. The output I get is the following:   {noformat}  Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload puppet/type/pyenv_python: Could not autoload p  uppet/provider/pyenv_pyth...















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




 














-- 
You received this message because 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-2380) autoloading provider fails at random

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2380



  autoloading provider fails at random 










Change By:

 Joshua Cooper




Assignee:

 Kylo Ginsberg Daniele Sluijters












   

 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-1060) enablerepo and disablerepo for yum type

[Rob Reynolds (JIRA)]

Title: Message Title










 

 Rob Reynolds assigned an issue to Rob Reynolds











 






 Puppet /  PUP-1060



  enablerepo and disablerepo for yum type 










Change By:

 Rob Reynolds




Assignee:

 Rob Reynolds












   

 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-617) Packages pushed

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-617



  Packages pushed 










Change By:

 Kenneth Barber




Fix Version/s:

 2.0.0












   

 Add Comment











 










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




 














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

Jira (PDB-614) Tag the release and create packages

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-614



  Tag the release and create packages 










Change By:

 Kenneth Barber




Fix Version/s:

 2.0.0












   

 Add Comment











 










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




 














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

Jira (PDB-615) Smoke test packages

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-615



  Smoke test packages 










Change By:

 Kenneth Barber




Fix Version/s:

 2.0.0












   

 Add Comment











 










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




 














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

Jira (PDB-616) Go/no-go meeting

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-616



  Go/no-go meeting 










Change By:

 Kenneth Barber




Fix Version/s:

 2.0.0












   

 Add Comment











 










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




 














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

Jira (PDB-609) Ensure tests are passing

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-609



  Ensure tests are passing 










Change By:

 Kenneth Barber




Fix Version/s:

 2.0.0












   

 Add Comment











 










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




 














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

Jira (PUP-2363) yumrepo priority absent is still broken.

[Jason A. Smith (JIRA)]

Title: Message Title










 

 Jason A. Smith updated an issue











 






 Puppet /  PUP-2363



  yumrepo priority absent is still broken. 










Change By:

 Jason A. Smith









 According to the types reference documentation:http://docs.puppetlabs.com/references/latest/type.html#yumrepo-attribute-prioritythe priority attribute can also take the value 'absent' which should mean that the priority is removed from the repo file, but puppet 3.5.1 currently complains: # $  puppet apply --verbose /tmp/test.ppError: Parameter priority failed on Yumrepo[test]: Must be within range 1-99 at /tmp/test.pp:3Wrapped exception:Must be within range 1-99 # $  cat /tmp/test.ppyumrepo { 'test':  priority => absent,}












   

 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-612) Is a new version in Jira created for the next version in the series?

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-612



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










Change By:

 Kenneth Barber




Fix Version/s:

 2.0.0












   

 Add Comment











 










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




 














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

Jira (PDB-608) Prepare documentation indexes for new major release

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-608



  Prepare documentation indexes for new major release 










Change By:

 Kenneth Barber




Fix Version/s:

 2.0.0












   

 Add Comment











 










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




 














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

Jira (PUP-2290) ca_server and directory based environments don't play nice together

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: ca_server and directory based environments don't play nice together 










Confirmed that server returns a 404. The 404 body has a message that says "Not Found: Could not find ", but this message is simply dropped in the rest indirection and it just returns nil (to mean - not found) which is interpreted by the higher layer making the cert request to mean "the cert was not found".












   

 Add Comment











 













 Puppet /  PUP-2290



  ca_server and directory based environments don't play nice together 







 When a Puppet Master is stared and is a CA but does not have any environments in {{/etc/puppet/environments}} even though it is configured for directory based environments it stops accepting CSR's.   We have a Puppet Master that is CA-only and therefor don't deploy the environments to it. The fix was to simply remove the {{environmentpath}} setting from ...















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




 














-- 
You received this message because 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...@googlegroup

Jira (PUP-2371) Truthiness and nullness

[JIRA]

Title: Message Title










 

 Igor Galić commented on an issue











 






  Re: Truthiness and nullness 










aaah. That's why I see so much type/provider code munging booleans.












   

 Add Comment











 













 Puppet /  PUP-2371



  Truthiness and nullness 







 Puppet's definition of what is truly True, False or Nil is completely insane. Now that Puppet 4 has opened up I think it's a good time to fix this, once and for all.   The problem has recently hit me in Types and Providers where trying to use Boolean parameters and properties is just impossible because the RAL in a lot of places checks for truthiness ins...















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




 














-- 
You received this message because 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-2381) Tags should issue an error when they are invalid

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Tags should issue an error when they are invalid 










You are correct in that tags are processed differently depending on backend. (in fact the entire query is processed differently).












   

 Add Comment











 













 Puppet /  PUP-2381



  Tags should issue an error when they are invalid 







 The docs ( http://docs.puppetlabs.com/puppet/3/reference/lang_reserved.html#tags ) state ( emphasis added) that tags names *should* confirm to {noformat}\A[a-z0-9_][a-z0-9_:\.\-]*\Z{noformat}   and also:   {quote}  Tags *must* begin with a lowercase letter, number, or underscore, and can include:    - Lowercase letters   - Numbers   - Underscores   - ...















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




 














-- 
You received this message because 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-611) Is there a commit for every bug targeted at the release?

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber assigned an issue to Ryan Senior











 






 PuppetDB /  PDB-611



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










Change By:

 Kenneth Barber




Assignee:

 Ryan Senior












   

 Add Comment











 










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




 














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

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

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber assigned an issue to Ryan Senior











 






 PuppetDB /  PDB-610



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










Change By:

 Kenneth Barber




Assignee:

 Ryan Senior












   

 Add Comment











 










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




 














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

Jira (PDB-608) Prepare documentation indexes for new major release

[Kenneth Barber (JIRA)]

Title: Message Title










 

 Kenneth Barber assigned an issue to Kenneth Barber











 






 PuppetDB /  PDB-608



  Prepare documentation indexes for new major release 










Change By:

 Kenneth Barber




Assignee:

 Kenneth Barber












   

 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-2381) Tags should issue an error when they are invalid

[Lee Lowder (JIRA)]

Title: Message Title










 

 Lee Lowder created an issue











 






 Puppet /  PUP-2381



  Tags should issue an error when they are invalid 










Issue Type:

  Bug




Affects Versions:


 3.5.1, 3.4.3, 2.7.23




Assignee:


 Unassigned




Created:


 29/Apr/14 6:29 AM




Priority:

  Normal




Reporter:

 Lee Lowder










The docs ( http://docs.puppetlabs.com/puppet/3/reference/lang_reserved.html#tags ) state ( emphasis added) that tags names should confirm to 


\A[a-z0-9_][a-z0-9_:\.\-]*\Z


and also:

Tags must begin with a lowercase letter, number, or underscore, and can include:


Lowercase letters


Numbers


Underscores


Colons


Periods
  

Jira (PUP-2371) Truthiness and nullness

[Daniele Sluijters (JIRA)]

Title: Message Title










 

 Daniele Sluijters commented on an issue











 






  Re: Truthiness and nullness 










Yes. Unfortunately it's a one-line fix which causes a lot of spec failures and I haven't had the courage yet to look at it. I believe Adrien Thebo wanted to go for it.












   

 Add Comment











 













 Puppet /  PUP-2371



  Truthiness and nullness 







 Puppet's definition of what is truly True, False or Nil is completely insane. Now that Puppet 4 has opened up I think it's a good time to fix this, once and for all.   The problem has recently hit me in Types and Providers where trying to use Boolean parameters and properties is just impossible because the RAL in a lot of places checks for truthiness ins...















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




 














-- 
You received this message because 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-2371) Truthiness and nullness

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Truthiness and nullness 










Seems like the best cause of action is to fix PUP-2368 while we are working on the new stuff.












   

 Add Comment











 













 Puppet /  PUP-2371



  Truthiness and nullness 







 Puppet's definition of what is truly True, False or Nil is completely insane. Now that Puppet 4 has opened up I think it's a good time to fix this, once and for all.   The problem has recently hit me in Types and Providers where trying to use Boolean parameters and properties is just impossible because the RAL in a lot of places checks for truthiness ins...















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




 














-- 
You received this message because 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-1985) Allow class & define parameters to reference earlier parameters

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Allow class & define parameters to reference earlier parameters 










yes, naturally  IIRC, it evaluates all of the default expressions, and then sets them - there is no partial result. When an argument is given it can be referenced. I think it gets even more weir when you also use resource default expressions (i.e. Foo  { x => 'value'}
) due to the lazyness of the evaluation of those.
This is not easily fixed for the 3x defines and classes.












   

 Add Comment











 













 Puppet /  PUP-1985



  Allow class & define parameters to reference earlier parameters 







 It would be good if code like this was possible:   {code}  class postgresql (    $version = '9.0',    $datadir = "/var/lib/postgresql/${version}/main",  ) { ... }  {code}   or used in expressions:   {code}  class foo (    $concurrent_reads = 20,    $concurrent_writes = $concurrent_reads/2,  ) { ... }  {code}   Some of this can be possible to workaroun...















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




 














-- 
You received this message because you are subscribed to the Google G

Jira (PUP-2371) Truthiness and nullness

[Daniele Sluijters (JIRA)]

Title: Message Title










 

 Daniele Sluijters commented on an issue











 






  Re: Truthiness and nullness 










The typical way to make them "true" (hah) booleans is to use either of require 'puppet/property/boolean' or require 'puppet/paramter/boolean' and add a , boolean => true, parent => Puppet::Parameter::Boolean to it. 
Unfortunately because of PUP-2368 (and I'm guessing in a few other places too) that only works when setting the property to 'true', never to 'false'.












   

 Add Comment











 













 Puppet /  PUP-2371



  Truthiness and nullness 







 Puppet's definition of what is truly True, False or Nil is completely insane. Now that Puppet 4 has opened up I think it's a good time to fix this, once and for all.   The problem has recently hit me in Types and Providers where trying to use Boolean parameters and properties is just impossible because the RAL in a lot of places checks for truthiness ins...















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




 














-- 
You received this message because 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+unsubsc

Jira (PUP-2371) Truthiness and nullness

[Henrik Lindberg (JIRA)]

Title: Message Title










 

 Henrik Lindberg commented on an issue











 






  Re: Truthiness and nullness 










uh, yeah.. well... newvalues(true, false) defines an Enum of two symbols, could just as well have been newvalues(:red, :green). Here we would want to define that the value should be a Boolean. Not sure if you can do that. I guess it gets really difficult when also facing booleans in string form.
Because of this mess we think the best approach is to write a new catalog/type system with clearly defined rules, and then deal with backwards compatibility separately (at the border). Trying to fix the current under-specified mess is probably just going to cause a lot of grief. 












   

 Add Comment











 













 Puppet /  PUP-2371



  Truthiness and nullness 







 Puppet's definition of what is truly True, False or Nil is completely insane. Now that Puppet 4 has opened up I think it's a good time to fix this, once and for all.   The problem has recently hit me in Types and Providers where trying to use Boolean parameters and properties is just impossible because the RAL in a lot of places checks for truthiness ins...















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




 

Jira (PUP-2371) Truthiness and nullness

[Daniele Sluijters (JIRA)]

Title: Message Title










 

 Daniele Sluijters commented on an issue











 






  Re: Truthiness and nullness 










As an example for Type/Providers insanity:


  newproperty(:anything) do
newvalues(true, false)
defaultto false
  end



But on the provider side you don't get false, you get :false. If you try to fix this by using require 'puppet/property/boolean` and setting the property to boolean you hit PUP-2368, parameters have similar weirdness.












   

 Add Comment











 













 Puppet /  PUP-2371



  Truthiness and nullness 







 Puppet's definition of what is truly True, False or Nil is completely insane. Now that Puppet 4 has opened up I think it's a good time to fix this, once and for all.   The problem has recently hit me in Types and Providers where trying to use Boolean parameters and properties is just impossible because the RAL in a lot of places checks for truthiness ins...















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




 








   

Jira (PUP-2368) using booleans result in unmanaged property

[Daniele Sluijters (JIRA)]

Title: Message Title










 

 Daniele Sluijters updated an issue











 






 Puppet /  PUP-2368



  using booleans result in unmanaged property 










Change By:

 Daniele Sluijters




Summary:

 setter on provider is never called using booleans result in unmanaged property












   

 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-1985) Allow class & define parameters to reference earlier parameters

[JIRA]

Title: Message Title










 

 Erik Dalén commented on an issue











 






  Re: Allow class & define parameters to reference earlier parameters 










So, this seems to work with values you specify as parameters, but not with default values.
Illustration: code define foo ( $bar = 1, $baz = $bar, ) { notify  { $baz: }
} foo  {'test1': bar => 'test'}
foo  {'test2': }
code
code Notice: Compiled catalog for 10.48.20.37.office.spotify.net in environment production in 0.08 seconds Notice: test Notice: /Stage[main]/Main/Foo[test1]/Notify[test]/message: defined 'message' as 'test' Notice: undef Notice: /Stage[main]/Main/Foo[test2]/Notify[undef]/message: defined 'message' as 'undef' Notice: Finished catalog run in 0.53 seconds code












   

 Add Comment











 













 Puppet /  PUP-1985



  Allow class & define parameters to reference earlier parameters 







 It would be good if code like this was possible:   {code}  class postgresql (    $version = '9.0',    $datadir = "/var/lib/postgresql/${version}/main",  ) { ... }  {code}   or used in expressions:   {code}  class foo (    $concurrent_reads = 20,    $concurrent_writes = $concurrent_reads/2,  ) { ... }  {code}   Some of this can be possible to workaroun...















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




   

Jira (PUP-2380) autoloading provider fails at random

[Daniele Sluijters (JIRA)]

Title: Message Title










 

 Daniele Sluijters updated an issue











 






 Puppet /  PUP-2380



  autoloading provider fails at random 










Change By:

 Daniele Sluijters









 I recently wrote a provider which works just fine in all my tests but when running it in our production environment it will fail at random. The output I get is the following:{noformat}Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload puppet/type/pyenv_python: Could not autoload puppet/provider/pyenv_python/pyenv: can't convert nil into String on node super-secret-foo/usr/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:194:in `is_http_200?'/usr/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:100:in `find'/usr/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:201:in `find'/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:259:in `retrieve_new_catalog'/usr/lib/ruby/vendor_ruby/puppet/util.rb:327:in `thinmark'/usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'/usr/lib/ruby/vendor_ruby/puppet/util.rb:326:in `thinmark'/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:258:in `retrieve_new_catalog'/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:69:in `retrieve_catalog'/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:109:in `prepare_and_retrieve_catalog'/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:175:in `run'/usr/lib/ruby/vendor_ruby/puppet/agent.rb:48:in `run'/usr/lib/ruby/vendor_ruby/puppet/agent/locker.rb:20:in `lock'/usr/lib/ruby/vendor_ruby/puppet/agent.rb:48:in `run'/usr/lib/ruby/vendor_ruby/puppet/agent.rb:118:in `with_client'/usr/lib/ruby/vendor_ruby/puppet/agent.rb:45:in `run'/usr/lib/ruby/vendor_ruby/puppet/agent.rb:83:in `run_in_fork'/usr/lib/ruby/vendor_ruby/puppet/agent.rb:44:in `run'/usr/lib/ruby/vendor_ruby/puppet/application.rb:179:in `call'/usr/lib/ruby/vendor_ruby/puppet/application.rb:179:in `controlled_run'/usr/lib/ruby/vendor_ruby/puppet/agent.rb:42:in `run'/usr/lib/ruby/vendor_ruby/puppet/application/agent.rb:355:in `onetime'/usr/lib/ruby/vendor_ruby/puppet/application/agent.rb:321:in `run_command'/usr/lib/ruby/vendor_ruby/puppet/application.rb:372:in `run'/usr/lib/ruby/vendor_ruby/puppet/application.rb:479:in `plugin_hook'/usr/lib/ruby/vendor_ruby/puppet/application.rb:372:in `run'/usr/lib/ruby/vendor_ruby/puppet/util.rb:479:in `exit_on_fail'/usr/lib/ruby/vendor_ruby/puppet/application.rb:372:in `run'/usr/lib/ruby/vendor_ruby/puppet/context.rb:51:in `override'/usr/lib/ruby/vendor_ruby/puppet.rb:233:in `override'/usr/lib/ruby/vendor_ruby/puppet/application.rb:362:in `run'/usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:137:in `run'/usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:91:in `execute'/usr/bin/puppet:4Warning: Not using cache on failed catalogError: Could not retrieve catalog; skipping run{noformat}It looks like we're getting an HTTP error of some kind  and  but that's all I can make of  it  also looks like the error handling is broken .












  

Jira (PUP-2380) autoloading provider fails at random

[Daniele Sluijters (JIRA)]

Title: Message Title










 

 Daniele Sluijters created an issue











 






 Puppet /  PUP-2380



  autoloading provider fails at random 










Issue Type:

  Bug




Affects Versions:


 3.5.1




Assignee:

 Kylo Ginsberg




Components:


 Types and Providers




Created:


 29/Apr/14 1:01 AM




Priority:

  Normal




Reporter:

 Daniele Sluijters










I recently wrote a provider which works just fine in all my tests but when running it in our production environment it will fail at random. The output I get is the following:


Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload puppet/type/pyenv_python: Could not autoload p
uppet/provider/pyenv_python/pyenv: can't convert nil into String on node vm0046.healthcare.nedap.local
/usr/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:194:in `is_http_200?'
/usr/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:100:in `find'
/usr/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:201:in `find'
/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:259:in `retrieve_new_catalog'
/usr/lib/ruby/vendor_ruby/puppet/util.rb:327:in `thinmark'
/usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'
/usr/lib/ruby/vendor_ruby/puppet/util.rb:326:in `thinmark'
/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:258:in `retrieve_new_catalog'
/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:69:in `retrieve_catalog'
/usr/lib/ruby/vendor_ruby/puppet/configur

Jira (PUP-2380) autoloading provider fails at random

[Daniele Sluijters (JIRA)]

Title: Message Title










 

 Daniele Sluijters updated an issue











 






 Puppet /  PUP-2380



  autoloading provider fails at random 










Change By:

 Daniele Sluijters









 I recently wrote a provider which works just fine in all my tests but when running it in our production environment it will fail at random. The output I get is the following:{noformat}Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload puppet/type/pyenv_python: Could not autoload puppet/provider/pyenv_python/pyenv: can't convert nil into String on node  vm0046.healthcare.nedap.local  super-secret-foo /usr/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:194:in `is_http_200?'/usr/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:100:in `find'/usr/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:201:in `find'/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:259:in `retrieve_new_catalog'/usr/lib/ruby/vendor_ruby/puppet/util.rb:327:in `thinmark'/usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'/usr/lib/ruby/vendor_ruby/puppet/util.rb:326:in `thinmark'/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:258:in `retrieve_new_catalog'/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:69:in `retrieve_catalog'/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:109:in `prepare_and_retrieve_catalog'/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:175:in `run'/usr/lib/ruby/vendor_ruby/puppet/agent.rb:48:in `run'/usr/lib/ruby/vendor_ruby/puppet/agent/locker.rb:20:in `lock'/usr/lib/ruby/vendor_ruby/puppet/agent.rb:48:in `run'/usr/lib/ruby/vendor_ruby/puppet/agent.rb:118:in `with_client'/usr/lib/ruby/vendor_ruby/puppet/agent.rb:45:in `run'/usr/lib/ruby/vendor_ruby/puppet/agent.rb:83:in `run_in_fork'/usr/lib/ruby/vendor_ruby/puppet/agent.rb:44:in `run'/usr/lib/ruby/vendor_ruby/puppet/application.rb:179:in `call'/usr/lib/ruby/vendor_ruby/puppet/application.rb:179:in `controlled_run'/usr/lib/ruby/vendor_ruby/puppet/agent.rb:42:in `run'/usr/lib/ruby/vendor_ruby/puppet/application/agent.rb:355:in `onetime'/usr/lib/ruby/vendor_ruby/puppet/application/agent.rb:321:in `run_command'/usr/lib/ruby/vendor_ruby/puppet/application.rb:372:in `run'/usr/lib/ruby/vendor_ruby/puppet/application.rb:479:in `plugin_hook'/usr/lib/ruby/vendor_ruby/puppet/application.rb:372:in `run'/usr/lib/ruby/vendor_ruby/puppet/util.rb:479:in `exit_on_fail'/usr/lib/ruby/vendor_ruby/puppet/application.rb:372:in `run'/usr/lib/ruby/vendor_ruby/puppet/context.rb:51:in `override'/usr/lib/ruby/vendor_ruby/puppet.rb:233:in `override'/usr/lib/ruby/vendor_ruby/puppet/application.rb:362:in `run'/usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:137:in `run'/usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:91:in `execute'/usr/bin/puppet:4Warning: Not using cache on failed catalogError: Could not retrieve catalog; skipping run{noformat}It looks like we're getting an HTTP error of some kind and it also looks like the error handling is broken.