Jira (PUP-3905) Evaluate impact of ruby 2.1.5 automatically retrying idempotent http methods

2016-04-25 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  PUP-3905 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Evaluate impact of ruby 2.1.5 automatically retrying idempotent http methods  
 
 
 
 
 
 
 
 
 
 
Chris Price Ping again. Especially now that Justin isn't on your team, would be cool to have somebody else try to sort out potential impact and whether you need us to patch this behavior client-side 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-3905) Evaluate impact of ruby 2.1.5 automatically retrying idempotent http methods

2016-04-25 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley assigned an issue to Chris Price 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3905 
 
 
 
  Evaluate impact of ruby 2.1.5 automatically retrying idempotent http methods  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Assignee:
 
 Justin May Chris Price 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir

2016-04-25 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  PUP-5206 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet filebucket --local uses $bucketdir instead of $clientbucketdir  
 
 
 
 
 
 
 
 
 
 
I think Michael's final summary is absolutely correct. The issue is sorting through the exact changes, and what is a "feature" vs. a potential breaking change that needs to wait for 5.0. I'm burried in trying to clean up our entire backlog right now (a seemingly Sisyphean endeavor), but this is on my radar at this point and I'll try to work out a gameplan with my team for what changes we can make in what order in which versions. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-169) processorcount on hpux is wrong

2016-04-25 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  FACT-169 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: processorcount on hpux is wrong  
 
 
 
 
 
 
 
 
 
 
I'm kicking this back to "Open". It's not something we're going to tackle internally any time soon (HP-UX is still not something we support), but it is a real issue and I want to leave it around for anyone in the community 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-165) virtual - dmidecode: /dev/mem: Operation not permitted

2016-04-25 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  FACT-165 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: virtual - dmidecode: /dev/mem: Operation not permitted  
 
 
 
 
 
 
 
 
 
 
Does anyone know if this ticket still impacts Facter 3? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4445) Add support to TLS 1.2 connections to Puppet Forge when SSLv3 is blocked in a corporate network

2016-04-25 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  PUP-4445 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add support to TLS 1.2 connections to Puppet Forge when SSLv3 is blocked in a corporate network  
 
 
 
 
 
 
 
 
 
 
Since we believe this to be resolved and we haven't heard from you, I'm going to go ahead and close this. If you can still reproduce feel free to reopen 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5879) Ensure Puppet uses FileSystem.read where applicable to read JSON, settings and other files as UTF-8

2016-04-25 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  PUP-5879 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ensure Puppet uses FileSystem.read where applicable to read JSON, settings and other files as UTF-8  
 
 
 
 
 
 
 
 
 
 
Erick Banks I see in the actual results for test case 4 that a backslash () was missing after 'c:' in the error message. Was that stripped out by Puppet or was it perhaps missing in the original command? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5879) Ensure Puppet uses FileSystem.read where applicable to read JSON, settings and other files as UTF-8

2016-04-25 Thread Erick Banks (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erick Banks assigned an issue to Glenn Sarti 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5879 
 
 
 
  Ensure Puppet uses FileSystem.read where applicable to read JSON, settings and other files as UTF-8  
 
 
 
 
 
 
 
 
 

Change By:
 
 Erick Banks 
 
 
 

Assignee:
 
 Erick Banks Glenn Sarti 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5879) Ensure Puppet uses FileSystem.read where applicable to read JSON, settings and other files as UTF-8

2016-04-25 Thread Erick Banks (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erick Banks commented on  PUP-5879 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ensure Puppet uses FileSystem.read where applicable to read JSON, settings and other files as UTF-8  
 
 
 
 
 
 
 
 
 
 
Functional Review 
FAILED with build https://github.com/puppetlabs/puppet/commit/9b80121f10ca66939ee9acd3f469c6c615607da6. Test Case 4 did not pass. 
Environment 
vmpooler image win-2012r2-wmf5-x86_64 ConEmux64 v160416 macbook pro running OSX 10.11.3 
Test Case 1 Reproduction Steps (negative test) 
 

Use a win-2012r2-wmf5-x86_64 machine
 

Download latest public version of puppet at downloads.puppetlabs.com
 

Change the graphdir to be look like this in c:\programdata\puppetlabs\puppet\etc\puppet.conf "graphdir=c:\graph\ᚠᛇᚻ"
 

On the command line print the config by typing "puppet config print"
 

Make the graphy directory via "mkdir c:\graph"
 

Apply the null catalog to verify the graphdir is properly set by: puppet apply -e "#"
 
 
Test Case 1 Expect 
Output of "puppet config print" statement should have garbled/mangled graphdir After running "puppet apply -e "#"" there should be a directory with garbage characters (this indicates a failure mode) 
Test Case 1 Actual 
All expectations were met. 
Test Case 2 UTF-8 2-byte characters (verify fix) 
 

Use a win-2012r2-wmf5-x86_64 machine
 

Install the patched version of puppet found here http://builds.puppetlabs.lan/puppet-agent/910bd0d1fe24e1c0ddd469d02f9af49885998d34/artifacts/windows/
 

Change the graphdir to be look like this in c:\programdata\puppetlabs\puppet\etc\puppet.conf "graphdir=c:\graph\ᚠᛇᚻ"
 

On the command line print the config by typing "puppet config print"
 

Make the graphy directory via "mkdir c:\graph"
 

 

Jira (PUP-6232) generated modules will not work with ruby 1.8.7

2016-04-25 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6232 
 
 
 
  generated modules will not work with ruby 1.8.7  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Scrum Team:
 
 Code Management 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6232) generated modules will not work with ruby 1.8.7

2016-04-25 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6232 
 
 
 
  generated modules will not work with ruby 1.8.7  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP 4.5.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6200) Smoke test packages (PUP 3.8.7)

2016-04-25 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte commented on  PUP-6200 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Smoke test packages (PUP 3.8.7)  
 
 
 
 
 
 
 
 
 
 
Validating 3.8.7 OS X dmg on OS X 10.11 
Install facter gem 
 
 
 
 
 
 
cfopahywkgspq62:~ root# gem install facter 
 
 
 
 
Fetching: facter-2.4.6-universal-darwin.gem (100%) 
 
 
 
 
Successfully installed facter-2.4.6-universal-darwin 
 
 
 
 
Parsing documentation for facter-2.4.6-universal-darwin 
 
 
 
 
Installing ri documentation for facter-2.4.6-universal-darwin 
 
 
 
 
1 gem installed 
 
 
 
 

 
 
 
 
 
 
 
Install dmg 
 
 
 
 
 
 
cfopahywkgspq62:~ root# curl -O http://builds.puppetlabs.lan/puppet/3.8.7/artifacts/apple/puppet-3.8.7.dmg 
 
 
 
 
  % Total% Received % Xferd  

Jira (PUP-6224) Add Ruby Generator to generate ruby classes from Object types

2016-04-25 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6224 
 
 
 
  Add Ruby Generator to generate ruby classes from Object types  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Release Notes Summary:
 
 Part of a new feature. 
 
 
 

Release Notes:
 
 Not Needed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6200) Smoke test packages (PUP 3.8.7)

2016-04-25 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6200 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Smoke test packages (PUP 3.8.7)  
 
 
 
 
 
 
 
 
 
 
All windows installs were done using the UI for MSI 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6224) Add Ruby Generator to generate ruby classes from Object types

2016-04-25 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6224 
 
 
 
  Add Ruby Generator to generate ruby classes from Object types  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Acceptance Criteria:
 
 That unit tests pass.This is an internal feature/enabler at this point - there are no user facing features. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6200) Smoke test packages (PUP 3.8.7)

2016-04-25 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6200 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Smoke test packages (PUP 3.8.7)  
 
 
 
 
 
 
 
 
 
 
Windows 10 Ent - x64 
Not a supported platform. Tested it anyway 32bit pkg  
 
 
 
 
 
 
  
 
 
 
 
C:\Program Files (x86)\Puppet Labs\Puppet\bin>puppet apply -e "notify{ 'hello world' :}" 
 
 
 
 
Could not retrieve fact='hostname', resolution='': Could not execute 'hostname': command not found 
 
 
 
 
Could not retrieve fact='hostname', resolution='': Could not execute 'hostname': command not found 
 
 
 
 
Could not retrieve fact='hostname', resolution='': Could not execute 'hostname': command not found 
 
 
 
 
Could not retrieve fact='hostname', resolution='': Could not execute 'hostname': command not found 
 
 
 
 
Warning: Could not retrieve fact fqdn 
 
 
 
 
Could not retrieve fact='hostname', resolution='': Could not execute 'hostname': command not found 
 
 
 
 
Could not retrieve fact='hostname', resolution='': Could not execute 'hostname': command not found 
 
 

Jira (PUP-6200) Smoke test packages (PUP 3.8.7)

2016-04-25 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6200 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Smoke test packages (PUP 3.8.7)  
 
 
 
 
 
 
 
 
 
 
Windows 2012 R2 x64 
32bit pkg 
 
 
 
 
 
 
ruby 1.9.3p551 (2014-11-13) [i386-mingw32] 
 
 
 
 
  
 
 
 
 
C:\Program Files (x86)\Puppet Labs\Puppet\bin>puppet apply -e "notify{ 'hello wo 
 
 
 
 
rld' :}" 
 
 
 
 
Notice: Compiled catalog for fmv536byzx7a7pp.delivery.puppetlabs.net in environm 
 
 
 
 
ent production in 0.05 seconds 
 
 
 
 
Notice: hello world 
 
 
 
 
Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hel 
 
 
 
 
lo world' 
 
 
 
 
Notice: Finished catalog run in 0.17 seconds 
 
 
 
  

Jira (PUP-6200) Smoke test packages (PUP 3.8.7)

2016-04-25 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6200 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Smoke test packages (PUP 3.8.7)  
 
 
 
 
 
 
 
 
 
 
Win2008 R2 x64 
32bit Agent 
 
 
 
 
 
 
ruby 1.9.3p551 (2014-11-13) [i386-mingw32] 
 
 
 
 
  
 
 
 
 
C:\Program Files (x86)\Puppet Labs\Puppet\bin>puppet apply -e "notify{ 'hello wo 
 
 
 
 
rld' :}" 
 
 
 
 
Notice: Compiled catalog for skhm60xyl6j8913.delivery.puppetlabs.net in environm 
 
 
 
 
ent production in 0.03 seconds 
 
 
 
 
Notice: hello world 
 
 
 
 
Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hel 
 
 
 
 
lo world' 
 
 
 
 
Notice: Finished catalog run in 0.02 seconds 
 
 
 
 

Jira (PUP-6200) Smoke test packages (PUP 3.8.7)

2016-04-25 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney commented on  PUP-6200 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Smoke test packages (PUP 3.8.7)  
 
 
 
 
 
 
 
 
 
 
Running on Debian 7 when installed from packages: 
 
 
 
 
 
 
root@klk6ki5l5yss3px:~# puppet apply -e "notify{ 'hello world' :}" 
 
 
 
 
Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations 
 
 
 
 
   (at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1139:in `issue_deprecation_warning') 
 
 
 
 
Notice: Compiled catalog for klk6ki5l5yss3px.delivery.puppetlabs.net in environment production in 0.01 seconds 
 
 
 
 
Notice: hello world 
 
 
 
 
Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hello world' 
 
 
 
 
Notice: Finished catalog run in 0.02 seconds 
 
 
 
 
root@klk6ki5l5yss3px:~# puppet --version 
 
 
 
 
3.8.7 
 
 
 
 
root@klk6ki5l5yss3px:~# puppet help 
   

Jira (PUP-6200) Smoke test packages (PUP 3.8.7)

2016-04-25 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6200 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Smoke test packages (PUP 3.8.7)  
 
 
 
 
 
 
 
 
 
 
Windows 2003 R2 x64 
64bit - Fails to install with warning - Expected 32bit 
 
 
 
 
 
 
C:\Program Files (x86)\Puppet Labs\Puppet\bin>puppet apply -e "notify{ 'hello wo 
 
 
 
 
rld' :}" 
 
 
 
 
Notice: Compiled catalog for iesaxx8xygka8pc.delivery.puppetlabs.net in environm 
 
 
 
 
ent production in 0.05 seconds 
 
 
 
 
Notice: hello world 
 
 
 
 
Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hel 
 
 
 
 
lo world' 
 
 
 
 
Notice: Finished catalog run in 0.02 seconds 
 
 
 
 
  
 
 
 
 
C:\Program Files (x86)\Puppet Labs\Puppet\bin>puppet help 
 
 

Jira (FACT-960) Memory details missing on Windows

2016-04-25 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-960 
 
 
 
  Memory details missing on Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Component/s:
 
 DOCS 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-2419) Deprecate "req_bits" Setting

2016-04-25 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2419 
 
 
 
  Deprecate "req_bits" Setting  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Sprint:
 
 Client 2016-05-18 (Freeze) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-3941) Puppet agent will accept yaml content

2016-04-25 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3941 
 
 
 
  Puppet agent will accept yaml content  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Sprint:
 
 Client 2016-05-18 (Freeze) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4617) puppet cert list should display long names for extensions

2016-04-25 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4617 
 
 
 
  puppet cert list should display long names for extensions  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Sprint:
 
 Client 2016-05-18 (Freeze) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6099) Additional file and mount autorequire

2016-04-25 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6099 
 
 
 
  Additional file and mount autorequire  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Sprint:
 
 Client Community Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6200) Smoke test packages (PUP 3.8.7)

2016-04-25 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney commented on  PUP-6200 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Smoke test packages (PUP 3.8.7)  
 
 
 
 
 
 
 
 
 
 
Running on CentOS 7 when installed from packages: 
 
 
 
 
 
 
[root@i2uzzu73w5pdw5v ~]#  puppet apply -e "notify{ 'hello world' :}" 
 
 
 
 
Notice: Compiled catalog for i2uzzu73w5pdw5v.delivery.puppetlabs.net in environment production in 0.01 seconds 
 
 
 
 
Notice: hello world 
 
 
 
 
Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hello world' 
 
 
 
 
Notice: Finished catalog run in 0.01 seconds 
 
 
 
 
[root@i2uzzu73w5pdw5v ~]# puppet --version 
 
 
 
 
3.8.7 
 
 
 
 
[root@i2uzzu73w5pdw5v ~]# puppet help 
 
 
 
 
  
 
 
 
 
Usage: puppet  [options]  [options] 
 
 
 

Jira (PUP-6200) Smoke test packages (PUP 3.8.7)

2016-04-25 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney commented on  PUP-6200 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Smoke test packages (PUP 3.8.7)  
 
 
 
 
 
 
 
 
 
 
Running the gem on CentOS 7: 
 
 
 
 
 
 
[root@qf7b2t9esb806a5 ~]# puppet apply -e 'notify{ 'hello world!' :}' 
 
 
 
 
-bash: !': event not found 
 
 
 
 
[root@qf7b2t9esb806a5 ~]# puppet apply -e "notify{ 'hello world!' :}" 
 
 
 
 
-bash: !': event not found 
 
 
 
 
[root@qf7b2t9esb806a5 ~]# puppet apply -e 'notify{ "hello world^C:}' 
 
 
 
 
[root@qf7b2t9esb806a5 ~]# puppet apply -e "notify{ 'hello world' :}" 
 
 
 
 
Notice: Compiled catalog for qf7b2t9esb806a5.delivery.puppetlabs.net in environment production in 0.01 seconds 
 
 
 
 
Notice: hello world 
 
 
 
 
Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hello world' 
 
 
 
 
Notice: Finished catalog run in 0.47 seconds 
 

Jira (PUP-6200) Smoke test packages (PUP 3.8.7)

2016-04-25 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6200 
 
 
 
  Smoke test packages (PUP 3.8.7)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 
 
 
 
 
 
 
 (Initial planned release date: 2016-04-21)Procedure may vary by project and point in the release cycle. Ask around.In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc).For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master.  Manual smoke testing can therefore be limited to other package formats than deb and rpm.For the Puppet gem, we don't yet have automated acceptance testing, so some quick manual smoke testing should always be performed.  Platform packages express their dependencies differently than gems, so it's possible to encounter a situation where the build pipeline produced packages out of sync with the gems.Lighter testing of Z releases is acceptable.  * Add a link to the Packages repository that you receive from the "Tag and create packages" subtask  * Ping folks on your team for help with different platforms.  * When you pick up a platform, please leave a comment below that you are testing it. When it looks good, leave another comment, preferably with a code snippet showing the commands executed and their output.  * When all platforms picked have been smoke tested, move this ticket to done.IMPORTANT: Please edit the description of this ticket and remove "Example:" below. Edit the platforms to smoke test on, and the smoke test procedure. Example: Smoke test platforms:  *  pick some platforms such as  *  gem - select one Linux for the universal gem, Windows with x64 platform-specific gem, and Windows with x86 platform-specific gem  * Windows 2003/2008/2012 (msi)  *  Solaris 10/11 (tarball or gem?)  *  OSX (dmg)  *  (Note if you are smoke testing Puppet and pick an rpm or deb based platform, concentrate on testing a gem or tarball, since acceptance should have adequately smoke tested those packages.)*  RHEL /  7 or CentOS  5/6/ 7*  Fedora 19/20*  Debian  6/ 7 * Ubuntu 10.04/12.04/14.04   Smoke test procedure:  * Start/stop/restart a master (if the platform supports that)  * Start/stop/restart an agent  * Help/man  * Write and run some manifestsDependencies:  * Tag and create packages  * For Windows MSIs - Push tag 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
   

Jira (FACT-1157) No clear warning error about Duplicate Fact implementations

2016-04-25 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1157 
 
 
 
  No clear warning error about Duplicate Fact implementations  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Summary:
 
 No clear warning error about Duplicate  Facts   Fact implementations 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1153) Facter build includes libcrypto.so multiple times

2016-04-25 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  FACT-1153 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter build includes libcrypto.so multiple times  
 
 
 
 
 
 
 
 
 
 
So we're definitely actually linking against libcrypto.so multiple times. We recently changed Leatherman to avoid linking dependency libs multiple times, so possibly this is fixed up now. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6185) Windows stat / lstat are inefficient - may calculate mode too frequently

2016-04-25 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes commented on  PUP-6185 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Windows stat / lstat are inefficient - may calculate mode too frequently  
 
 
 
 
 
 
 
 
 
 
Per backlog grooming, need more information. What is acceptance criteria? Current number of calls vs. expected number of calls. 
If part of 4.5 needs to be done by 5/9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6199) Tag the release and create packages (PUP 3.8.7)

2016-04-25 Thread Morgan Rhodes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Morgan Rhodes commented on  PUP-6199 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Tag the release and create packages (PUP 3.8.7)  
 
 
 
 
 
 
 
 
 
 
Packages available at http://builds.puppetlabs.lan/puppet/3.8.7/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-2652) ticket/master/pdb 2546 hup support

2016-04-25 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2652 
 
 
 
  ticket/master/pdb 2546 hup support  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/04/25 2:00 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
Add HUP support to PDB 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   






Jira (PUP-5825) systemd service provider always enables service in chroot

2016-04-25 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5825 
 
 
 
  systemd service provider always enables service in chroot  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Release Notes Summary:
 
 Same as PUP-5296. 
 
 
 

Release Notes:
 
 Bug Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1392) Facter fails when locale files are missing for specified locale on CentOS 7

2016-04-25 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1392 
 
 
 
  Facter fails when locale files are missing for specified locale on CentOS 7  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Release Notes Summary:
 
 An issue where Facter fails in some invalid locale environments with"failed to initialize logging system due to a locale error: Invalid or unsupported charset:ANSI_X3.4-1968" has been addressed; it should now always fall back to a C locale. 
 
 
 

Release Notes:
 
 Bug Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5825) systemd service provider always enables service in chroot

2016-04-25 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow commented on  PUP-5825 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: systemd service provider always enables service in chroot  
 
 
 
 
 
 
 
 
 
 
Michael Smith Does this need the DOCS bug fix release notes filled in? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1400) Facter : cannot load such file -- facter/util/file_read

2016-04-25 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1400 
 
 
 
  Facter : cannot load such file -- facter/util/file_read   
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Affects Version/s:
 
 PE 2015.2.1 
 
 
 

Affects Version/s:
 
 FACT 3.0.0 
 
 
 

Key:
 
 PE FACT - 13225 1400 
 
 
 

Project:
 
 Puppet Enterprise [Internal] Facter 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1401) facter fails on Mac OS X when run in LC_ALL=C locale

2016-04-25 Thread Michal Ruzicka (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michal Ruzicka updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1401 
 
 
 
  facter fails on Mac OS X when run in LC_ALL=C locale  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michal Ruzicka 
 
 
 
 
 
 
 
 
 
 The following happens on my mac:{code}$ LC_ALL=C facter --traceundefined method `each' for nil:NilClass/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/macosx.rb:39:in `'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:130:in `load'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:130:in `kernel_load'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:115:in `load_file'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:49:in `block (2 levels) in load_all'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:47:in `each'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:47:in `block in load_all'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:45:in `each'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:45:in `load_all'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/collection.rb:104:in `load_all'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter.rb:126:in `to_hash'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/application.rb:46:in `run'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/bin/facter:20:in `'/Users/mruzicka/.rvm/gems/ruby-2.1.5/bin/facter:23:in `load'/Users/mruzicka/.rvm/gems/ruby-2.1.5/bin/facter:23:in `'/Users/mruzicka/.rvm/gems/ruby-2.1.5/bin/ruby_executable_hooks:15:in `eval'/Users/mruzicka/.rvm/gems/ruby-2.1.5/bin/ruby_executable_hooks:15:in `{code}The underlying problem seems to be that the output of the {{/usr/sbin/system_profiler}} command contains UTF-8 characters on my mac even when run in the  {{  LC_ALL=C }}  locale:{code}LC_ALL=C /usr/sbin/system_profiler -xml SPSoftwareDataType... user_name Michal Růžička (mruzicka)...{code}which causes an exception in [{{lib/facter/util/macosx.rb}}|https://github.com/puppetlabs/facter/blob/2.4.6/lib/facter/util/macosx.rb] while reding the output of the command as the code only expects  {{ US-ASCII }}  when the {{LC_ALL=C}} is in effect. Given the behavior of the {{/usr/sbin/system_profiler}} command the code should rather _always_ expect UTF-8 irrespective of the locale settings. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add 

Jira (FACT-1401) facter fails on Mac OS X when run in LC_ALL=C locale

2016-04-25 Thread Michal Ruzicka (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michal Ruzicka updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1401 
 
 
 
  facter fails on Mac OS X when run in LC_ALL=C locale  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michal Ruzicka 
 
 
 
 
 
 
 
 
 
 The following happens on my mac:{code}$ LC_ALL=C facter --traceundefined method `each' for nil:NilClass/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/macosx.rb:39:in `'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:130:in `load'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:130:in `kernel_load'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:115:in `load_file'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:49:in `block (2 levels) in load_all'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:47:in `each'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:47:in `block in load_all'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:45:in `each'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:45:in `load_all'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/collection.rb:104:in `load_all'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter.rb:126:in `to_hash'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/application.rb:46:in `run'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/bin/facter:20:in `'/Users/mruzicka/.rvm/gems/ruby-2.1.5/bin/facter:23:in `load'/Users/mruzicka/.rvm/gems/ruby-2.1.5/bin/facter:23:in `'/Users/mruzicka/.rvm/gems/ruby-2.1.5/bin/ruby_executable_hooks:15:in `eval'/Users/mruzicka/.rvm/gems/ruby-2.1.5/bin/ruby_executable_hooks:15:in `{code}The underlying problem seems to be that the output of the {{/usr/sbin/system_profiler}} command contains UTF-8 characters on my mac even when run in the LC_ALL=C locale:{code}LC_ALL=C /usr/sbin/system_profiler -xml SPSoftwareDataType... user_name Michal Růžička (mruzicka)...{code} The code which causes an exception  in [{{lib/facter/util/macosx.rb}}|https://github.com/puppetlabs/facter/blob/2.4.6/lib/facter/util/macosx.rb]  while reding the output of the command as the code only expects {{US-ASCII}} when the {{LC_ALL=C}} is in effect. Given the behavior of the {{/usr/sbin/system_profiler}} command the code  should  rather _always_  expect UTF-8  output from the command  irrespective of the locale settings. 
 
 
 
 
 
 
 
 
 
 
 
 

 
   

Jira (PUP-6224) Add Ruby Generator to generate ruby classes from Object types

2016-04-25 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6224 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add Ruby Generator to generate ruby classes from Object types  
 
 
 
 
 
 
 
 
 
 
Thomas Hallgren Can you help me with the Acceptance Criteria here. Not sure how much you can do from puppet to verify functionality yet. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6224) Add Ruby Generator to generate ruby classes from Object types

2016-04-25 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6224 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add Ruby Generator to generate ruby classes from Object types  
 
 
 
 
 
 
 
 
 
 
merged to master at: 3b6513a 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1401) facter fails on Mac OS X when run in LC_ALL=C locale

2016-04-25 Thread Michal Ruzicka (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michal Ruzicka updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1401 
 
 
 
  facter fails on Mac OS X when run in LC_ALL=C locale  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michal Ruzicka 
 
 
 
 
 
 
 
 
 
 The following happens on my mac:{code}$ LC_ALL=C facter --traceundefined method `each' for nil:NilClass/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/macosx.rb:39:in `'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:130:in `load'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:130:in `kernel_load'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:115:in `load_file'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:49:in `block (2 levels) in load_all'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:47:in `each'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:47:in `block in load_all'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:45:in `each'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/loader.rb:45:in `load_all'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/util/collection.rb:104:in `load_all'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter.rb:126:in `to_hash'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/application.rb:46:in `run'/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/bin/facter:20:in `'/Users/mruzicka/.rvm/gems/ruby-2.1.5/bin/facter:23:in `load'/Users/mruzicka/.rvm/gems/ruby-2.1.5/bin/facter:23:in `'/Users/mruzicka/.rvm/gems/ruby-2.1.5/bin/ruby_executable_hooks:15:in `eval'/Users/mruzicka/.rvm/gems/ruby-2.1.5/bin/ruby_executable_hooks:15:in `{code}The underlying problem seems to be that the output of the {{/usr/sbin/system_profiler}} command contains UTF-8 characters on my mac even when run in the LC_ALL=C locale:{code}LC_ALL=C /usr/sbin/system_profiler -xml SPSoftwareDataType... user_name Michal Růžička (mruzicka)...{code}The code in [{{lib/facter/util/macosx.rb}}|https://github.com/puppetlabs/ pe- facter/blob/ 3 2 . 8 4 . x 6 /lib/facter/util/macosx.rb] should expect UTF-8 output from the command irrespective of the locale settings. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
  

Jira (PUP-6232) generated modules will not work with ruby 1.8.7

2016-04-25 Thread garrett honeycutt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 garrett honeycutt commented on  PUP-6232 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: generated modules will not work with ruby 1.8.7  
 
 
 
 
 
 
 
 
 
 
Rake 11 dropped support for ruby 1.8.7, so we need to pin it to v10. 
PR @ https://github.com/puppetlabs/puppet/pull/4913 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1401) facter fails on Mac OS X when run in LC_ALL=C locale

2016-04-25 Thread Michal Ruzicka (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michal Ruzicka created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1401 
 
 
 
  facter fails on Mac OS X when run in LC_ALL=C locale  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 FACT 2.4.6 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/04/25 1:02 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Michal Ruzicka 
 
 
 
 
 
 
 
 
 
 
The following happens on my mac: 
 
 
 
 
 
 
$ LC_ALL=C facter --trace 
 
 
 
 
undefined method `each' for nil:NilClass 
 
 
 
 
/Users/mruzicka/.rvm/gems/ruby-2.1.5/gems/facter-2.4.6-universal-darwin/lib/facter/macosx.rb:39:in `' 
 
 
 

Jira (PUP-6224) Add Ruby Generator to generate ruby classes from Object types

2016-04-25 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-6224 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add Ruby Generator to generate ruby classes from Object types  
 
 
 
 
 
 
 
 
 
 
You can't do anything from Puppet until PUP-6225 is implemented so I suggest we add the acceptance criteria there. This feature should be considered internal. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4188) Agent applies broken cached catalog when puppetserver dies mid-run

2016-04-25 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-4188 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Agent applies broken cached catalog when puppetserver dies mid-run  
 
 
 
 
 
 
 
 
 
 
Thanks for the ping Rémi. This will take a little investigation to narrow down root causes. This would also be ripe for some acceptance testing. I'll drop this in Client Triage sprint. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6232) generated modules will not work with ruby 1.8.7

2016-04-25 Thread garrett honeycutt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 garrett honeycutt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6232 
 
 
 
  generated modules will not work with ruby 1.8.7  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/04/25 12:47 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 garrett honeycutt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6231) generated modules do not pass metadata_lint

2016-04-25 Thread garrett honeycutt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 garrett honeycutt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6231 
 
 
 
  generated modules do not pass metadata_lint  
 
 
 
 
 
 
 
 
 

Change By:
 
 garrett honeycutt 
 
 
 
 
 
 
 
 
 
 Generating a module will create a metadata.json that is missing the summary field.To reproduce ``` {code} puppet module generate foo-barcd barbundle installrake metadata_lint ``` {code} produces ``` {code} Error: Required field 'summary' not found in metadata.json.Errors found in metadata.json ``` {code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6231) generated modules do not pass metadata_lint

2016-04-25 Thread garrett honeycutt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 garrett honeycutt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6231 
 
 
 
  generated modules do not pass metadata_lint  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.4.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/04/25 12:45 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 garrett honeycutt 
 
 
 
 
 
 
 
 
 
 
Generating a module will create a metadata.json that is missing the summary field. 
To reproduce 
``` puppet module generate foo-bar cd bar bundle install rake metadata_lint ``` 
produces 
``` Error: Required field 'summary' not found in metadata.json. Errors found in metadata.json ``` 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

Jira (FACT-1392) Facter fails when locale files are missing for specified locale on CentOS 7

2016-04-25 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow commented on  FACT-1392 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter fails when locale files are missing for specified locale on CentOS 7  
 
 
 
 
 
 
 
 
 
 
Michael Smith Does this need the DOCS bug fix release notes filled in? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4188) Agent applies broken cached catalog when puppetserver dies mid-run

2016-04-25 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4188 
 
 
 
  Agent applies broken cached catalog when puppetserver dies mid-run  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Sprint:
 
 Client Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1284) Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result

2016-04-25 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson commented on  FACT-1284 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result  
 
 
 
 
 
 
 
 
 
 
validated on ubunut1404 with master puppet-agent SHA: b26610f40d5f6e9b05355ac98e993e519bd43a9e 
 
 
 
 
 
 
root@uz218phjjrzcanq:~# facter --custom-dir . foo 
 
 
 
 
true
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1284) Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result

2016-04-25 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow commented on  FACT-1284 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result  
 
 
 
 
 
 
 
 
 
 
Michael Smith Branan Riley Does this need the DOCS bug fix release notes filled in? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1284) Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result

2016-04-25 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson assigned an issue to Eric Thompson 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1284 
 
 
 
  Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Assignee:
 
 Eric Thompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6199) Tag the release and create packages (PUP 3.8.7)

2016-04-25 Thread Morgan Rhodes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Morgan Rhodes commented on  PUP-6199 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Tag the release and create packages (PUP 3.8.7)  
 
 
 
 
 
 
 
 
 
 
Packages being built at http://jenkins-release.delivery.puppetlabs.net/job/puppet-packaging-2016-04-25-11-51-11-3.8.7/ 
Will be available at builds.puppetlabs.lan/puppet/3.8.7 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1284) Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result

2016-04-25 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1284 
 
 
 
  Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Release Notes:
 
 Bug Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1284) Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result

2016-04-25 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1284 
 
 
 
  Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Release Notes Summary:
 
 Facter::Util::Resolution.exec will now set the Ruby $? exit status variable 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6224) Add Ruby Generator to generate ruby classes from Object types

2016-04-25 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6224 
 
 
 
  Add Ruby Generator to generate ruby classes from Object types  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Scope Change Category:
 
 Found 
 
 
 

Scope Change Reason:
 
 Blocks other issues in this sprint 
 
 
 

Sprint:
 
 Language  Triage  2016-05-04 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6224) Add Ruby Generator to generate ruby classes from Object types

2016-04-25 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6224 
 
 
 
  Add Ruby Generator to generate ruby classes from Object types  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 We need a way to generate a Ruby implementation from a Puppet  TypeSet  {{Object}} type . Such a generator would make it possible for us to describe the Puppet Language AST as a  TypeSet  set of object types  (in PL) and then generate the ruby classes. This would give us a couple of advantages.1. We no longer have a need for the third-party rgen gem.2. No dynamic creation of the AST classes need to take place everytime a Puppet runtime starts up.3. No transformation is needed when serializing the AST since everything is already Pcore.The generator should be designed in such a way that it also can generate  a TypeSet  an {{Object}}  to  an  anonymous  classes  class  that doesn't  polute  pollute  the Ruby namespace or the Puppet loader. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6224) Add Ruby Generator to generate ruby classes from Object types

2016-04-25 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6224 
 
 
 
  Add Ruby Generator to generate ruby classes from Object types  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Summary:
 
 Add Ruby Generator to generate ruby  modules  classes  from  TypeSets  Object types 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-2372) Support for unchanged reports using the benchmarking tool

2016-04-25 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2372 
 
 
 
  Support for unchanged reports using the benchmarking tool  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Story Points:
 
 5 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-2597) puppetdb 4.0.2 2016-04-20 Release

2016-04-25 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2597 
 
 
 
  puppetdb 4.0.2 2016-04-20 Release  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Story Points:
 
 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4188) Agent applies broken cached catalog when puppetserver dies mid-run

2016-04-25 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4188 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Agent applies broken cached catalog when puppetserver dies mid-run  
 
 
 
 
 
 
 
 
 
 
Rémi this ticket seems to have fallen between the cracks, I alerted some folks to take a look at it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6230) Data in modules interpret nil as {}

2016-04-25 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6230 
 
 
 
  Data in modules interpret nil as {}  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6230) Data in modules interpret nil as {}

2016-04-25 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6230 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Data in modules interpret nil as {}  
 
 
 
 
 
 
 
 
 
 
Merged to stable at: 0e6cac5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6230) Data in modules interpret nil as {}

2016-04-25 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6230 
 
 
 
  Data in modules interpret nil as {}  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Release Notes Summary:
 
 A regression was fixed where an explicit nil values in hiera data files used in modules and environment was turned into an empty hash by mistake. 
 
 
 

Release Notes:
 
 Bug Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6230) Data in modules interpret nil as {}

2016-04-25 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6230 
 
 
 
  Data in modules interpret nil as {}  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP 4.5.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6230) Data in modules interpret nil as {}

2016-04-25 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6230 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Data in modules interpret nil as {}  
 
 
 
 
 
 
 
 
 
 
Moved to release PUP 4.4.3 (or PUP 4.5.0, whichever comes first). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6230) Data in modules interpret nil as {}

2016-04-25 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6230 
 
 
 
  Data in modules interpret nil as {}  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP 4.4.2 
 
 
 

Fix Version/s:
 
 PUP 4.4.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5727) acceptance: cached catalog should allow encodings from utf8

2016-04-25 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte commented on  PUP-5727 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: acceptance: cached catalog should allow encodings from utf8  
 
 
 
 
 
 
 
 
 
 
Test fails on the following platforms using puppet-agent at sha b26610f containing puppet at sha 1d21af. 
 

arista4
 

cisconx
 

osx 10.9
 

osx 10.10
 

sles10
 
 
Here is a sample error from the run on osx 10.10 
 
 
 
 
 
 
ryl2jiujugpk92z.delivery.puppetlabs.net (sles10-64-1) 16:10:53$ puppet agent -t --environment supports_utf8_h2no9ukg --server ixenzkha9gzwh5r.delivery.puppetlabs.net 
 
 
 
 
  Info: Using configured environment 'supports_utf8_h2no9ukg' 
 
 
 
 
  Info: Retrieving pluginfacts 
 
 
 
 
  Info: Retrieving plugin 
 
 
 
 
  Info: Caching catalog for ryl2jiujugpk92z.delivery.puppetlabs.net 
 
 
 
 
  Info: Applying configuration version '1461453039' 
 
 
 
 
  Error: invalid byte sequence in US-ASCII 
 

Jira (PUP-5879) Ensure Puppet uses FileSystem.read where applicable to read JSON, settings and other files as UTF-8

2016-04-25 Thread Chun Du (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chun Du commented on  PUP-5879 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ensure Puppet uses FileSystem.read where applicable to read JSON, settings and other files as UTF-8  
 
 
 
 
 
 
 
 
 
 
Kenn Hussey Is this targeted for PE 2016.1.2? If so, Erick Banks please validate ASAP. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6230) Data in modules interpret nil as {}

2016-04-25 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6230 
 
 
 
  Data in modules interpret nil as {}  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6059) File type does not fsync temp file before checksum verification during file creation

2016-04-25 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin assigned an issue to Sean Griffin 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6059 
 
 
 
  File type does not fsync temp file before checksum verification during file creation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

Assignee:
 
 qa Sean Griffin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-2650) Investigate convergence test failure on 2016-04-21

2016-04-25 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior commented on  PDB-2650 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Investigate convergence test failure on 2016-04-21  
 
 
 
 
 
 
 
 
 
 
Another one http://jenkins-enterprise.delivery.puppetlabs.net:8080/job/enterprise_pe-puppetdb-extensions_unit-clj-puppetdb_master/539/JDK=oraclejdk8,PUPPETDB_DBTYPE=postgres,label=integration/console 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4188) Agent applies broken cached catalog when puppetserver dies mid-run

2016-04-25 Thread JIRA
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rémi commented on  PUP-4188 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Agent applies broken cached catalog when puppetserver dies mid-run  
 
 
 
 
 
 
 
 
 
 
Hello, 
Any updates on this issue ? 
Thanks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (NPUP-41) Implement the `type` function.

2016-04-25 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Native Puppet /  NPUP-41 
 
 
 
  Implement the `type` function.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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