Jira (PUP-4131) Gem version specifiers are not idempotent

[Joshua Cooper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joshua Cooper commented on  PUP-4131 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Gem version specifiers are not idempotent  
 
 
 
 
 
 
 
 
 
 
Nicholas Fagerlund It's the latter, if the currently installed version satisfies the constraint, then the resource will be considered insync. So for example, if the constraint is > 1.0, and the system currently has installed 1.0 or later, then it will be considered insync. If the system has 0.9 installed, then it will not be insync, and puppet will install the latest version of the gem currently available that still satisfies the constraint. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop 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-4721) Is there a commit for every JIRA ticket targeted at the release?

[Joshua Cooper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joshua Cooper assigned an issue to Joshua Cooper 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4721 
 
 
 
  Is there a commit for every JIRA ticket targeted at the release?  
 
 
 
 
 
 
 
 
 

Change By:
 
 Joshua Cooper 
 
 
 

Assignee:
 
 Kylo Ginsberg Joshua Cooper 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop 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-575) Split windows wix files into respective repositories

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-575



  Split windows wix files into respective repositories 










Change By:

 Joshua Cooper




Fix Version/s:

 future












   

 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-179) Puppet needs to delegate all fact loading to Facter

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-179



  Puppet needs to delegate all fact loading to Facter 










Change By:

 Joshua Cooper




Component/s:

 Client












   

 Add Comment











 










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




 














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

Jira (HI-7) Hiera stable acceptance tests use dynamically provisioned vcloud templates.

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Hiera stable acceptance tests use dynamically provisioned vcloud templates. 










Kurt Wall Any update when this might happen?












   

 Add Comment











 













 Hiera /  HI-7



  Hiera stable acceptance tests use dynamically provisioned vcloud templates. 







 Scott Schneider has already merged in changes to master which allow the Hiera Acceptance (master) Jenkins job to run against current puppet acceptance with dynamically provisioned vcloud templates. These templates do not exhibit the sporadic networking issues which have plagued the older templates.  We need to get these changes merged down into stable an...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop 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-1270) PR (2200) 'pkg' package provider does not understand IPS package versions properly

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1270



  PR (2200) 'pkg' package provider does not understand IPS package versions properly 










Change By:

 Joshua Cooper









 It would seem the 'pkg' provider (for illumos/Solaris/OpenSolaris IPS) does notdo the right thing with IPS package versions. We're running OmniOS and seeingthis: {noformat} kekkonen ~ % pfexec puppet apply -e 'package {"mdb": ensure => latest }'Notice: Compiled catalog for kekkonen.niksula.hut.fi in environment production in 1.17 secondsNotice: Finished catalog run in 6.39 secondskekkonen ~ % pfexec pkg update -nv mdb  Packages to update:1 Estimated space available: 14.11 TBEstimated space to be consumed: 24.61 MB   Create boot environment:   NoCreate backup boot environment:  Yes  Rebuild boot archive:   NoChanged packages:omnios  developer/debug/mdb0.5.11,5.11-0.151006:20130731T194820Z -> 0.5.11,5.11-0.151006:20131019T183740Z {noformat}   So puppet thinks there are no updates, but pkg correctly notices that an updateis available (only the timestamp has changed, not the version, build release,or branch numbers).puppet resource provides some insight into this: {noformat} kekkonen ~ % puppet resource package mdbpackage { 'mdb':  ensure => '0.5.11-0.151006',} {noformat}   This version number is not correct, it's missing the build release (5.11) andtimestamp.












   

 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 

Jira (PUP-1042) Puppet apply runmode should write classes.txt file

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1042



  Puppet apply runmode should write classes.txt file 










Change By:

 Joshua Cooper




Component/s:

 Client












   

 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-927) puppet apply on Windows always uses *nix style newlines from templates

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-927



  puppet apply on Windows always uses *nix style newlines from templates 










Change By:

 Joshua Cooper




Component/s:

 Trivial




Component/s:

 Client












   

 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-408) Puppet package acceptance is sufficient for a smoke test

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Puppet package acceptance is sufficient for a smoke test 










Kurt Wall Do you have any idea when this can be done?












   

 Add Comment











 













 Puppet /  PUP-408



  Puppet package acceptance is sufficient for a smoke test 







 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 pupp...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop 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-2423) Filebucket server should warn, not fail, if checksum type is not supported

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2423



  Filebucket server should warn, not fail, if checksum type is not supported 










Change By:

 Joshua Cooper




Component/s:

 Trivial












   

 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-2040) Allow excluding content from Puppet module tool built packages

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Allow excluding content from Puppet module tool built packages 










Pieter van de Bruggen This looks like a module tool PR, please take a look












   

 Add Comment











 













 Puppet /  PUP-2040



  Allow excluding content from Puppet module tool built packages 







 Puppet module tool only excludes some files from built tarball {{.\*, ~\*, pkg, ...}}   The result is that module tarballs could have spec files, fixtures, and any temporary files created during build   It should allow excluding content with {{puppet module build --exclude PATTERN1,PATTERN2,...}}















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop 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-2040) Allow excluding content from Puppet module tool built packages

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2040



  Allow excluding content from Puppet module tool built packages 










Change By:

 Joshua Cooper




Assignee:

 Pieter van de Bruggen












   

 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-1046) puppet module generate should produce a skeleton spec test

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1046



  puppet module generate should produce a skeleton spec test 










Change By:

 Joshua Cooper




Assignee:

 Joshua Cooper Pieter van de Bruggen












   

 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-2512) Validation for `enable` in service{} is lacking.

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2512



  Validation for `enable` in service{} is lacking. 










Change By:

 Joshua Cooper




Component/s:

 Trivial












   

 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-1046) puppet module generate should produce a skeleton spec test

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: puppet module generate should produce a skeleton spec test 










Pieter van de Bruggen I was not able to get the skeleton spec test to work correctly. Can you take a look at this?












   

 Add Comment











 













 Puppet /  PUP-1046



  puppet module generate should produce a skeleton spec test 







 # Overview #   In order to make `rake spec` give meaningful feedback with a module generated using `puppet module generate` once #11285 is implemented, the generate action should produce an example rspec-puppet based spec test for the module.   I think the example could simply add the class to the catalog and make sure it got added.















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop 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-2512) Validation for `enable` in service{} is lacking.

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2512



  Validation for `enable` in service{} is lacking. 










Change By:

 Joshua Cooper









 {noformat} [root@ccoifar9r5c1giy postgresql]# puppet resource service postgresql enable=runningError: The systemd provider can not handle attribute enableError: /Service[postgresql]/enable: change from true to running failed: The systemd provider can not handle attribute enable {noformat}   I discovered this while breaking Postgresql.  It happily passes a value of running into the providers which then explode.












   

 Add Comment











 










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




 














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

Jira (FACT-482) processor.rb crashes Facter within MCollective on MS Windows

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: processor.rb crashes Facter within MCollective on MS Windows 










Merged ab541d567 to facter-2 to be released in 2.1












   

 Add Comment











 













 Facter /  FACT-482



  processor.rb crashes Facter within MCollective on MS Windows 







 The use of facter facts plugin for mcollective causes the following error on MS Windows only:   in `rescue in block in get_fact' Failed to load facts: ThreadError: deadlock; recursive locking   This setup works very well on *nix operating systems though. Can the code at lib/facter/processor.rb:120 with "Thread::exclusive do" be refactored to allow such ...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop 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-2453) Windows agent not catching catalog

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2453



  Windows agent not catching catalog 










Change By:

 Joshua Cooper




Labels:

 windows












   

 Add Comment











 










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




 














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

Jira (PUP-2337) Directory environments can be massively slower than dynamic enviroments

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Directory environments can be massively slower than dynamic enviroments 










Henrik Lindberg now that 3.6.x is out, can we close this as a duplicate of a known issue?












   

 Add Comment











 













 Puppet /  PUP-2337



  Directory environments can be massively slower than dynamic enviroments 







 Per [this thread|https://groups.google.com/d/topic/puppet-users/wzy8NPWauu4/discussion] on puppet-users, multiple people are reporting massive slowdowns and increased CPU consumption when directory environments are turned on. One of the users included before-and-after profiling information, which I've attached to the ticket.















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop 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-2337) Directory environments can be massively slower than dynamic enviroments

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2337



  Directory environments can be massively slower than dynamic enviroments 










Change By:

 Joshua Cooper




Assignee:

 Henrik Lindberg












   

 Add Comment











 










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




 














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

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper 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" 










Glad to hear the issue was resolved Stefan Lasiewski, I'll go ahead and close this ticket.












   

 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-bugs@googlegroups.com.
Visit this group at http://groups.googl

Jira (PUP-2370) factpath conf setting ignored

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: factpath conf setting ignored 










Hi Jürgen Weber Puppet has historically supported pluginsync'ing of module content (including module facts). In 3.4, we added the ability to pluginsync external facts, see https://projects.puppetlabs.com/issues/9546.
The plugindest and pluginfactdest settings control where puppet pluginsyncs modules and external facts, respectively. Since you're not changing those settings, puppet continues to download into the default location /var/lib/puppet/lib/*.
The factpath setting on the other hand controls where facter will try to load external facts from. So factpath is not ignored, it's just not used in the way you think it is, so I'm going to close this bug.












   

 Add Comment











 













 Puppet /  PUP-2370



  factpath conf setting ignored 







 {noformat}  grep factpath /etc/puppet/puppet.conf  factpath=/var/lib/facter  {noformat}   {noformat}  # puppet agent --configprint all | grep factpath  factpath = /var/lib/facter  {noformat}   remove my old path/default path location  {noformat}# rm -rf /var/lib/puppet/lib/facter/{noformat}   run puppet  {noformat}  # puppet agent -t -v factpath=/var/l...















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




 

Jira (PUP-2370) factpath conf setting ignored

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2370



  factpath conf setting ignored 










Change By:

 Joshua Cooper









 {noformat} grep factpath /etc/puppet/puppet.conffactpath=/var/lib/facter {noformat}  {noformat} # puppet agent --configprint all | grep factpathfactpath = /var/lib/facter {noformat}   remove my old path/default path location {noformat} # rm -rf /var/lib/puppet/lib/facter/ {noformat} run puppet {noformat} # puppet agent -t -v factpath=/var/lib/facterInfo: Retrieving pluginfactsInfo: Retrieving pluginNotice: /File[/var/lib/puppet/lib/facter]/ensure: createdNotice: /File[/var/lib/puppet/lib/facter/ip6tables_version.rb]/ensure: defined content as '{md5}091123ad703f1706686bca4398c5b06f'Notice: /File[/var/lib/puppet/lib/facter/hostname_info.rb]/ensure: defined content as '{md5}3c9fdbff15e050928fb8970c59b1f125'Notice: /File[/var/lib/puppet/lib/facter/util]/ensure: createdNotice: /File[/var/lib/puppet/lib/facter/util/puppet_settings.rb]/ensure: defined content as '{md5}9f1d2593d0ae56bfca89d4b9266aeee1' {noformat}   and it goes to the default path still.new location: ls /var/lib/facter/ | wc -l0old/default location: ls /var/lib/puppet/lib/facter/ | wc -l14












   

 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-2454) User ID's below 1000, not 500, are generally considered system users on OpenBSD

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: User ID's below 1000, not 500, are generally considered system users on OpenBSD 










Hi Jasper Lievisse Adriaanse it looks like there are some comments on your PR. I'm reassigning this ticket to you, when you get a chance, please update the PR, and move this ticket to ready for merge.












   

 Add Comment











 













 Puppet /  PUP-2454



  User ID's below 1000, not 500, are generally considered system users on OpenBSD 







 Users can still modify this with 'uid_start' in adduser.conf, but in that  case they'd need to provide an actual value instead of 'true'.















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop 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-2454) User ID's below 1000, not 500, are generally considered system users on OpenBSD

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2454



  User ID's below 1000, not 500, are generally considered system users on OpenBSD 










Change By:

 Joshua Cooper




Assignee:

 Jasper Lievisse Adriaanse












   

 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-2570) Inconsistent results with Solaris kernelrelease fact

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Inconsistent results with Solaris kernelrelease fact 










Hi John Lyman thanks for the bug report. The agent uses facter to determine the set of facts. I have seen issues like you describe in facter when there is more than one resolution for a fact on a given platform. However, the kernel fact on solaris is surprisingly simple. Note that all of the other resolutions in that file are confined to different platforms.
Another thought is that you might have multiple facter versions installed? perhaps as a package and as a gem?
Could you verify that facter is returning the correct values:


while : ; do facter kernelrelease; done



Can you also capture facter --version? 












   

 Add Comment











 













 Puppet /  PUP-2570



  Inconsistent results with Solaris kernelrelease fact 







 While testing 3.5.1 puppet master, I discovered that the kernelrelease fact does not return the expected results. I expect it to return "5.10", but it randomly gets truncated to "5.1".   For example, I changed my site.pp to the following:  {code}  fail "kernelrelease = $::kernelrelease"  {code}   On the client, I run puppet agent in a loop and filter t...















 This message was sent by Atlassian JIRA (v6.

Jira (PUP-2580) Parameter path failure on file

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Parameter path failure on file 










Hi Tony Berry I'm set this bug status to Needs Information. If you resolve the issue you were seeing please, mark this ticket as closed.












   

 Add Comment











 













 Puppet /  PUP-2580



  Parameter path failure on file 







 This is the error I'm getting from a smoketest failure on Jenkins:  Parameter path failed on File[]: File paths must be fully qualified, not '' at /home/ec2-user/puppet/modules/gnoscommon/manifests/init.pp:19   I can't get anywhere to see what the problem is. It's telling me not to have a space somewhere but where I don't know. This problem is failing my...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop 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-2634) source_permissions invalid option?

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: source_permissions invalid option? 










The source_permissions option is only available when using 3.4 puppet master and agent, close this ticket.












   

 Add Comment











 













 Puppet /  PUP-2634



  source_permissions invalid option? 







 I just tried to set source_permissions on my default File resource:  File { owner => 'S-1-5-18', group => 'Administrators', source_permissions => ignore }   But windows puppet agent v3.4.0-rc2 says:  Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter source_permissions at /etc/puppet/modules/nscp/manifests/in...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop 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-2716) ssl_server_ca_chain is not documented

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper created an issue











 






 Puppet /  PUP-2716



  ssl_server_ca_chain is not documented 










Issue Type:

  Bug




Assignee:

 Kylo Ginsberg




Components:


 Client, Networking Services




Created:


 02/Jun/14 3:18 PM




Priority:

  Minor




Reporter:

 Joshua Cooper










The ssl_server_ca_chain setting is used in webrick to add intermediate root certificates (chain) to the SSL context. When the ssl server sends its Server Certificate message, it includes the chain of certs so that clients can validate the connection.
For example, :localcacerts might contain the cert for C=US/O=GeoTrust Inc./CN=GeoTrust Global CA
and :ssl_server_ca_chain might contain the cert for /C=US/O=GeoTrust Inc./CN=GeoTrust SSL CA - G2.












   

 Add Comment











 
 

Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Could not autoload puppet /util /instrumentation /listeners /log 










Brian Wilkins It looks like the agent's cert was revoked on the server side. You can confirm that by looking at the list of revoked certs (by serial number) on the master:


# openssl crl -in `puppet master --configprint cacrl` -noout -text
...
Revoked Certificates:
Serial Number: 02
Revocation Date: Jun  2 20:15:12 2014 GMT



More importantly, are you able to run the daemonized agent with --trace?












   

 Add Comment











 













 Puppet /  PUP-724



  Could not autoload puppet /util /instrumentation /listeners /log 














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




 














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

Jira (FACT-200) PR (596): (maint) Redirect dmidecode stderr to /dev/null - haus

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: PR (596): (maint) Redirect dmidecode stderr to /dev/null - haus 










Merged into stable in 28c0bec5a and was released in 1.7.5












   

 Add Comment











 













 Facter /  FACT-200



  PR (596): (maint) Redirect dmidecode stderr to /dev/null - haus 







 h2. (maint) Redirect dmidecode stderr to /dev/null   * Author: Matthaus Owens   * Company: Puppet Labs  * Github ID: [haus|https://github.com/haus]  * [Pull Request 596 Discussion|https://github.com/puppetlabs/facter/pull/596]  * [Pull Request 596 File Diff|https://github.com/puppetlabs/facter/pull/596/files]  h2. Pull Request Descrip...















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




 














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

Jira (FACT-199) PR (595): Update detection of GCE instances - apchamberlain

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: PR (595): Update detection of GCE instances - apchamberlain 










Per https://github.com/puppetlabs/facter/pull/595#issuecomment-41826962, we decided to close this and reinvestigate GCE detection.












   

 Add Comment











 













 Facter /  FACT-199



  PR (595): Update detection of GCE instances - apchamberlain 







 h2. Update detection of GCE instances    * Author: Alex Chamberlain <>  * Company: Puppet Labs, Inc.  * Github ID: [apchamberlain|https://github.com/apchamberlain]  * [Pull Request 595 Discussion|https://github.com/puppetlabs/facter/pull/595]  * [Pull Request 595 File Diff|https://github.com/puppetlabs/facter/pull/595/files]  h2. Pull Request Description ...















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




 














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

Jira (FACT-183) PR (590): Extract Facter execution methods to mixin - adrienthebo

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: PR (590): Extract Facter execution methods to mixin - adrienthebo 










Merged into facter-2 in commit 2ff7ae91064d and released in 2.0.1












   

 Add Comment











 













 Facter /  FACT-183



  PR (590): Extract Facter execution methods to mixin - adrienthebo 







 h2. Extract Facter execution methods to mixin   * Author: Adrien Thebo git...@somethingsinistral.net>  * Company: Puppet Labs  * Github ID: [adrienthebo|https://github.com/adrienthebo]  * [Pull Request 590 Discussion|https://github.com/puppetlabs/facter/pull/590]  * [Pull Request 590 File Diff|https://github.com/puppetlabs/facter/pull/590/files]  h2















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




 














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

Jira (FACT-192) PR (593): 21868/stable/cherry pick mavericks pkging - MosesMendoza

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: PR (593): 21868/stable/cherry pick mavericks pkging - MosesMendoza 










Merged into stable in 833e019f2 and released in 1.7.5 












   

 Add Comment











 













 Facter /  FACT-192



  PR (593): 21868/stable/cherry pick mavericks pkging - MosesMendoza 







 h2. 21868/stable/cherry pick mavericks pkging   * Author: <>  * Company:   * Github ID: [MosesMendoza|https://github.com/MosesMendoza]  * [Pull Request 593 Discussion|https://github.com/puppetlabs/facter/pull/593]  * [Pull Request 593 File Diff|https://github.com/puppetlabs/facter/pull/593/files]  h2. Pull Request Description   This PR includes the c...















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




 














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

Jira (HI-70) PR (166): (maint) Add fedora 20 to mock list - melissaanne

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: PR (166): (maint) Add fedora 20 to mock list - melissaanne 










Merged to stable in 498416eff released in 1.3.1












   

 Add Comment











 













 Hiera /  HI-70



  PR (166): (maint) Add fedora 20 to mock list - melissaanne 







 h2. (maint) Add fedora 20 to mock list   * Author: Melissa <>  * Company:   * Github ID: [melissaanne|https://github.com/melissaanne]  * [Pull Request 166 Discussion|https://github.com/puppetlabs/hiera/pull/166]  * [Pull Request 166 File Diff|https://github.com/puppetlabs/hiera/pull/166/files]  h2. Pull Request Description  (webhooks-id: d052e...















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




 














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

Jira (HI-67) PR (164): use pooling api - justinstoller

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: PR (164): use pooling api - justinstoller 










This was merged to stable in 9248fa4e and released in 1.3.1












   

 Add Comment











 













 Hiera /  HI-67



  PR (164): use pooling api - justinstoller 







 h2. use pooling api   * Author: Justin Stoller   * Company:   * Github ID: [justinstoller|https://github.com/justinstoller]  * [Pull Request 164 Discussion|https://github.com/puppetlabs/hiera/pull/164]  * [Pull Request 164 File Diff|https://github.com/puppetlabs/hiera/pull/164/files]  h2. Pull Request Description   @sschneid ...















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




 














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

Jira (HI-68) PR (165): Use the same kind of gem source switching as Puppet - justinstoller

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Hiera /  HI-68



  PR (165): Use the same kind of gem source switching as Puppet - justinstoller 










Change By:

 Joshua Cooper




Fix Version/s:

 1.3.1












   

 Add Comment











 










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




 














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

Jira (HI-68) PR (165): Use the same kind of gem source switching as Puppet - justinstoller

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: PR (165): Use the same kind of gem source switching as Puppet - justinstoller 










This was merged in https://github.com/puppetlabs/hiera/commit/2aa5bfb3be86ca031d3105c48893b06fa0dfffc5 and released in hiera 1.3.1












   

 Add Comment











 













 Hiera /  HI-68



  PR (165): Use the same kind of gem source switching as Puppet - justinstoller 







 h2. Use the same kind of gem source switching as Puppet   * Author: Justin Stoller   * Company:   * Github ID: [justinstoller|https://github.com/justinstoller]  * [Pull Request 165 Discussion|https://github.com/puppetlabs/hiera/pull/165]  * [Pull Request 165 File Diff|https://github.com/puppetlabs/hiera/pull/165/files]  h2. Pull ...















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




 














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

Jira (FACT-481) Infinite loop if EC2 metadata server times out

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Infinite loop if EC2 metadata server times out 










Kurt Wall looks like you had multiple facter versions installed:


Unable to add resolve nil for fact interfaces: undefined method `supported_platforms' for Facter::Util::IP:Class
undefined method `get_interfaces' for Facter::Util::IP:Class















   

 Add Comment











 













 Facter /  FACT-481



  Infinite loop if EC2 metadata server times out 







 On a Rackspace VM, Facter gets into an infinite loop when trying to contact the EC2 metadata server. The retry loop in lib/facter/ec2/rest.rb doesn't increment the counter on each iteration. This causes the Puppet agent to permanently hang.   To reproduce on a non-Rackspace system, just run:  FACTER_virtual=xen bin/facter   (Assuming there's no metada...















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




 














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

Jira (PUP-2705) External facts pluginsync not preserving executable bit

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: External facts pluginsync not preserving executable bit 










Hi Matteo, thank you for debugging the problem and submitting a PR. I've left a comment on the PR.












   

 Add Comment











 













 Puppet /  PUP-2705



  External facts pluginsync not preserving executable bit 







 As per the subject, the external facts feature in puppet 3.6.1 is partially broken.   I've tried to add a script into the /facts.d path and given it executable permissions too.   Once the agent runs, it successfully syncs the plugin across in the external facts directory (/var/lib/puppet/facts.d). However, the script lacks the original permissions.















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop 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-2097) Could not evaluate: Failed to get security information: Incorrect function

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2097



  Could not evaluate: Failed to get security information: Incorrect function 










Change By:

 Joshua Cooper




Assignee:

 Louis Mayorga












   

 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-724) Could not autoload puppet /util /instrumentation /listeners /log

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Could not autoload puppet /util /instrumentation /listeners /log 










mike jeski Rudy McComb Brian Wilkins Tamas Szasz Ronald Valente The error definitely originates on the agent side, so ignore my earlier comments about adding --debug and --trace to your puppet master.
Part of the confusion is that if the puppet reports setting includes log, then the log messages from the client's report will be written into the master's syslog, as happened here:


May 28 10:59:46 calfrmprd01 puppet-master[31917]: (///Puppet) Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation



This makes it appear as though the error came from the master, when in reality it came from .
Could you please update your comments to include the following information about your puppet agents only:


ruby version


puppet version


linux distro(s), e.g. Ubuntu 12.04 LTS


type of filesystems relevant to puppet, e.g. mount -l


how did you install puppet, e.g. rpm, apt, yum, gem, source, etc


are there multiple versions of puppet installed, e.g. as package (if so where from), as a gem, as tarball


did the issue show up recently after updating puppet?


If so, what version were you running previously?


How did you update? using puppet itself, package manager, gem update?




if you are able to reproduce the problem with a daemonized agent, can you add --trace to the script that launches puppet, e.g. on Ubuntu, edit /etc/default/puppet and restart the puppet service:




DAEMON_OPTS="--trace"

Jira (PUP-2700) Puppet 3.6.1 File recurse improperly handles spaces in filenames

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2700



  Puppet 3.6.1 File recurse improperly handles spaces in filenames 










Change By:

 Joshua Cooper









 This one's new on me.We're using file{ : recurse => remote} to pull a directory structure from a remote puppet fileserver. It would appear that there's a mismatch causing it to multiply urlencode resources it's recursing over, causing it to render a space ' ' as %2520 in the file_content call.Here's a convenient, if ugly, example:In the Fileserver: {noformat} [29/May/2014:14:15:18 -0700] "GET /production/file_content/puppet/python340/lib/python3.4/site-packages/setuptools/__pycache__/script%2520template%2520(dev).cpython-34.pyc HTTP/1.1" 404 147 "-" "-" {noformat}   in the client: {noformat} Error 404 on SERVER: Not Found: Could not find file_content puppet/python340/lib/python3.4/site-packages/setuptools/__pycache__/script%20template%20(dev).cpython-34.pycError: /Stage[main]/.../File[/opt/python340/lib/python3.4/site-packages/setuptools/__pycache__/script template (dev).cpython-34.pyc]/ensure: change from absent to file failed:Could not set 'file' on ensure: Error 404 on SERVER: Not Found: Could not find file_content puppet/python340/lib/python3.4/site-packages/setuptools/__pycache__/script%20template%20(dev).cpython-34.pyc {noformat}












   

 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 ht

Jira (PUP-2699) Puppet specs on windows triggers "Excluding C from search path. Fact file paths must be an absolute directory"

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2699



  Puppet specs on windows triggers "Excluding C from search path. Fact file paths must be an absolute directory" 










Change By:

 Joshua Cooper




Component/s:

 Client












   

 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-2699) Puppet specs on windows triggers "Excluding C from search path. Fact file paths must be an absolute directory"

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2699



  Puppet specs on windows triggers "Excluding C from search path. Fact file paths must be an absolute directory" 










Change By:

 Joshua Cooper




Labels:

 windows












   

 Add Comment











 










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




 














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




Component/s:

 Client












   

 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




Component/s:

 Client












   

 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-2521) Remove windows-pr gem as a Windows dependency

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2521



  Remove windows-pr gem as a Windows dependency 










Change By:

 Joshua Cooper




Labels:

 windows












   

 Add Comment











 










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




 














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




Component/s:

 Client












   

 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-2656) FFI Puppet::Util::Windows::Registry

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2656



  FFI Puppet::Util::Windows::Registry 










Change By:

 Joshua Cooper




Component/s:

 Client












   

 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-2656) FFI Puppet::Util::Windows::Registry

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2656



  FFI Puppet::Util::Windows::Registry 










Change By:

 Joshua Cooper




Labels:

 windows












   

 Add Comment











 










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




 














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

Jira (PUP-2383) Need x64 win-builder to generate both 32 and 64bit MSIs

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2383



  Need x64 win-builder to generate both 32 and 64bit MSIs 










Change By:

 Joshua Cooper




Component/s:

 Client












   

 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-2521) Remove windows-pr gem as a Windows dependency

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2521



  Remove windows-pr gem as a Windows dependency 










Change By:

 Joshua Cooper




Component/s:

 Client












   

 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




Component/s:

 Client












   

 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-2388) Update git setup steps to install architecture specific version of ruby

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2388



  Update git setup steps to install architecture specific version of ruby 










Change By:

 Joshua Cooper




Component/s:

 Client












   

 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




Component/s:

 Client












   

 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-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




Component/s:

 Client












   

 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-766) FFI native windows root certs code

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-766



  FFI native windows root certs code 










Change By:

 Joshua Cooper




Component/s:

 Client












   

 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) 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




Component/s:

 Client












   

 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-2388) Update git setup steps to install architecture specific version of ruby

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2388



  Update git setup steps to install architecture specific version of ruby 










Change By:

 Joshua Cooper




Labels:

 windows












   

 Add Comment











 










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




 














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




Component/s:

 Client












   

 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-2389) Create ruby 2.x branches for x86 and x64 in puppet-win32-ruby

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2389



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










Change By:

 Joshua Cooper




Component/s:

 Client












   

 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




Component/s:

 Client












   

 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::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




Component/s:

 Client












   

 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-2657) FFI Puppet::Util::Windows::Error

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2657



  FFI Puppet::Util::Windows::Error 










Change By:

 Joshua Cooper




Labels:

 windows












   

 Add Comment











 










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




 














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




Component/s:

 Client












   

 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-2657) FFI Puppet::Util::Windows::Error

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: FFI Puppet::Util::Windows::Error 










Merged into master in d38153bd7 to be released in 3.7.0












   

 Add Comment











 













 Puppet /  PUP-2657



  FFI Puppet::Util::Windows::Error 







 Need to FFI   {panel}  def initialize(message, code = GetLastError.call, original = nil)  {panel}















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop 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-2657) FFI Puppet::Util::Windows::Error

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2657



  FFI Puppet::Util::Windows::Error 










Change By:

 Joshua Cooper




Component/s:

 Client












   

 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




Component/s:

 Client












   

 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-2554) FFI Puppet::Util::ADSI module

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2554



  FFI Puppet::Util::ADSI module 










Change By:

 Joshua Cooper




Component/s:

 Client












   

 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




Component/s:

 Client












   

 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-2389) Create ruby 2.x branches for x86 and x64 in puppet-win32-ruby

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






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










Matthaus Owens yes, though the problem is that ruby 2.1 still has test failures when run on windows, so I don't think it's ready for prime time yet. The end of this thread https://groups.google.com/d/topic/rubyinstaller/8Je3OEbtb3w/discussion mentions the remaining two bugs in ruby core:
test_float: https://bugs.ruby-lang.org/issues/8358
test_machine_stackoverflow: https://bugs.ruby-lang.org/issues/9739












   

 Add Comment











 













 Puppet /  PUP-2389



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







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















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




 














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

Jira (PUP-2383) Need x64 win-builder to generate both 32 and 64bit MSIs

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Need x64 win-builder to generate both 32 and 64bit MSIs 










Moses Mendoza thanks, I think we are good as-is. I will keep this ticket open until we get to the stage where we're actually generating x86 and x64 MSIs, to see if we need to update the wix toolset for example.












   

 Add Comment











 













 Puppet /  PUP-2383



  Need x64 win-builder to generate both 32 and 64bit MSIs 







 Need to verify that existing win-builders are x64 and can generate MSIs for both platforms. If win-builders are x32, then we will need to provision new x64 builders.















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




 














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

Jira (FACT-341) Windows operatingsystemrelease support

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Windows operatingsystemrelease support 










Louis Mayorga that's correct, PE 3.x hasn't moved to facter 2.x yet. That said if this is something that would greatly help, you can always file a Puppet Enterprise feature request to have this fact backported to pe-facter. If you do, make sure to link to this ticket.












   

 Add Comment











 













 Facter /  FACT-341



  Windows operatingsystemrelease support 







 operatingsystemrelease should return any of the following XP, Vista, 7, 2003, 2008, 2008R2 rather than the kernel version.















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop 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-2515) Notice: Run of Puppet configuration client already in progress; skipping (/var/lib/puppet/state/agent_catalog_run.lock exists)

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Notice: Run of Puppet configuration client already in progress; skipping (/var/lib/puppet/state/agent_catalog_run.lock exists) 










Den Mat When the problem occurs, can you check the contents of the agent's lock file: cat `puppet agent --configprint agent_catalog_run_lockfile`. I'm specifically wondering if it's empty (as described in PUP-1070), or contains the pid of the currently running, but blocked agent.
You're seeing two processes, because the agent forks and applies the catalog in a child process, and the child is stuck in select trying to either connect or read from the master, while the parent process waits for the child process to exit.
However, puppet sets both a TCP connect and read timeout based on the configtimeout setting, which defaults to 2 minutes. So I would not expect the agent to block indefinitely. The 2 minute read timeout is actually surprising to me...
When this happens again, can you verify that the master has an established connection from the agent? If not, then it sounds like the agent's blocking connect or read system call was not interrupted.
Also, can you confirm that you are not using a load-balancer to front your puppetmaster?












   

 Add Comment











 













 Puppet /  PUP-2515



  Notice: Run of Puppet configuration client already in progress; skipping (/var/lib/puppet/state/agent_catalog_run.lock exists) 







 Puppet stops responding on the client. We issue the following:  {code}  $ sudo service puppet restart  Stopping puppet agent: [ OK ]  Starting puppet agent: [ OK ]  {code}  {code}  $ sudo puppet agent --test  Notice: Run of Puppet configuration client already in progress; skipping...

Jira (PUP-2657) FFI Puppet::Util::Windows::Error

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2657



  FFI Puppet::Util::Windows::Error 










Change By:

 Joshua Cooper




Assignee:

 Joshua Cooper












   

 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-2657) FFI Puppet::Util::Windows::Error

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2657



  FFI Puppet::Util::Windows::Error 










Change By:

 Joshua Cooper




Assignee:

 Joshua Cooper












   

 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-2661) Invalid parameter allow_virtual for puppet 3.6.1

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2661



  Invalid parameter allow_virtual for puppet 3.6.1 










Change By:

 Joshua Cooper




Assignee:

 Eric Sorenson Shaw Xiao












   

 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-2661) Invalid parameter allow_virtual for puppet 3.6.1

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Invalid parameter allow_virtual for puppet 3.6.1 










Shaw Xiao can you run puppet --version on the master? Also please check that you don't have multiple puppet versions installed. For example as a gem, installed into ruby's site_lib, through your package manager.












   

 Add Comment











 













 Puppet /  PUP-2661



  Invalid parameter allow_virtual for puppet 3.6.1 







 I have both master and client puppet machine installed with 3.6.1.   {code}  Package {    allow_virtual => true,  }  {code}  If I put the above setting as release note (http://docs.puppetlabs.com/puppet/latest/reference/release_notes.html#puppet-361) suggested, I got error  "Error: Could not retrieve catalog from remote server: Error 400 on S...















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




 














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

Jira (PUP-1070) puppetd doesn't always cleanup lockfile properly

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1070



  puppetd doesn't always cleanup lockfile properly 










Change By:

 Joshua Cooper




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-1070) puppetd doesn't always cleanup lockfile properly

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: puppetd doesn't always cleanup lockfile properly 










Merged in c7c482225 to master for 3.7.0












   

 Add Comment











 













 Puppet /  PUP-1070



  puppetd doesn't always cleanup lockfile properly 







 ok I had the patch #2661 now running for some weeks and I had nearly no problems anymore. However from time to time (maybe once,twice a week) a random client doesn't remove its lockfile (@/var/lib/puppet/state/puppetdlock@), hence future runs fail. I assume this might still happen due to a uncatched exception (as in #2261), however the problem is a) hard ...















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




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop 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-2692) Puppet master passenger processes keep growing

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2692



  Puppet master passenger processes keep growing 










Change By:

 Joshua Cooper




Sprint:

 Week 2014- 5 6 - 28 4  to 2014-6- 4 11












   

 Add Comment











 










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




 














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

Jira (FACT-234) Add Facts showing the UUID of partitions

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Facter /  FACT-234



  Add Facts showing the UUID of partitions 










Change By:

 Joshua Cooper




Sprint:

 Week 2014-6- 4 11  to 2014-6- 11 18












   

 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-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




Sprint:

 Week 2014- 5 6 - 28 4  to 2014-6- 4 11












   

 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-2639) Increase environment_timeout defeault.

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2639



  Increase environment_timeout defeault. 










Change By:

 Joshua Cooper




Sprint:

 Week 2014- 5 6 - 28 4  to 2014-6- 4 11












   

 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-2401) Add acceptance tests for ssh_authorized_key type

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2401



  Add acceptance tests for ssh_authorized_key type 










Change By:

 Joshua Cooper




Sprint:

 Week 2014- 5 6 - 28 4  to 2014-6- 4 11












   

 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




Sprint:

 Week 2014-6- 11 18  to 2014-6- 18 25












   

 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-1362) Rubyize yumhelper.py to remove dependency on python

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1362



  Rubyize yumhelper.py to remove dependency on python 










Change By:

 Joshua Cooper




Sprint:

 Week 2014- 5 6 - 28 4  to 2014-6- 4 11












   

 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-2521) Remove windows-pr gem as a Windows dependency

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2521



  Remove windows-pr gem as a Windows dependency 










Change By:

 Joshua Cooper




Sprint:

 Week 2014-6-18 to 2014-6-25












   

 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




Sprint:

 Week 2014-6- 11 18  to 2014-6- 18 25












   

 Add Comment











 










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




 














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

Jira (FACT-459) MTU interface facts not being reported on Archlinux.

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Facter /  FACT-459



  MTU interface facts not being reported on Archlinux. 










Change By:

 Joshua Cooper




Sprint:

 Week 2014- 5 6 - 28 4  to 2014-6- 4 11












   

 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




Sprint:

 Week 2014- 5 6 - 28 4  to 2014-6- 4 11












   

 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-2689) A node can't always collect its own exported resources

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2689



  A node can't always collect its own exported resources 










Change By:

 Joshua Cooper




Sprint:

 Week 2014- 5 6 - 28 4  to 2014-6- 4 11












   

 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-2356) (PR 2577) Add yum repo extra options

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2356



  (PR 2577) Add yum repo extra options 










Change By:

 Joshua Cooper




Sprint:

 Week 2014- 5 6 - 28 4  to 2014-6- 4 11












   

 Add Comment











 










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




 














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

Jira (FACT-335) Revisit how facter detects GCE instances

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Facter /  FACT-335



  Revisit how facter detects GCE instances 










Change By:

 Joshua Cooper




Sprint:

 Week 2014-6- 4 11  to 2014-6- 11 18












   

 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-2402) Add acceptance tests for sshkey type

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2402



  Add acceptance tests for sshkey type 










Change By:

 Joshua Cooper




Sprint:

 Week 2014- 5 6 - 28 4  to 2014-6- 4 11












   

 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-1807) Empty string should not equal undef

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1807



  Empty string should not equal undef 










Change By:

 Joshua Cooper




Sprint:

 Week 2014- 5 6 - 28 4  to 2014-6- 4 11












   

 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-2656) FFI Puppet::Util::Windows::Registry

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2656



  FFI Puppet::Util::Windows::Registry 










Change By:

 Joshua Cooper




Sprint:

 Week 2014- 5 6 - 28 4  to 2014-6- 4 11












   

 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-417) Add acceptance cells which test with passenger instead of webrick.

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-417



  Add acceptance cells which test with passenger instead of webrick. 










Change By:

 Joshua Cooper




Sprint:

 Week 2014-3-05 to 2014-3-12, Week 2014-3-12 to 2014-3-19, Week 2014-6- 4 11  to 2014-6- 11 18












   

 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-2369) Add extra info to property's return

[Joshua Cooper (JIRA)]

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-2369



  Add extra info to property's return 










Change By:

 Joshua Cooper




Sprint:

 Week 2014-5-7 to 2014-5-14, Week 2014- 5 6 - 28 4  to 2014-6- 4 11












   

 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.