date:20160627

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6450 
 
 
 
  Group resource members order can break idempotence in Windows  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.5.2 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Windows 
 
 
 

Created:
 

 2016/06/27 9:01 PM 
 
 
 

Environment:
 
 
Windows 2016.1.1 agent 
 
 
 

Labels:
 

 windows 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Ethan Brown 
 
 
 
 
 
 
 
 
 
 
Given the following hiera array:

Jira (PDOC-81) @param tag help text should be in JSON

2016-06-27 Thread Jason Kincl (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Kincl updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-81 
 
 
 
  @param tag help text should be in JSON  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jason Kincl 
 
 
 
 
 
 
 
 
 
 When generating the JSON format, it should include the @param help textFrom the example README  on Classes / Defined Types :{code}# @param  num_a [Integer] the  first_arg The  first  number to be compared  parameter for this class {code}The " the The  first  number to be compared  parameter for this class " text should be in the JSON format output. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (PDOC-81) @param tag help text should be in JSON

2016-06-27 Thread Jason Kincl (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Kincl updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-81 
 
 
 
  @param tag help text should be in JSON  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jason Kincl 
 
 
 

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-6447) Allow UTF8 files to have a leading BOM to be more tolerant of files produced on Windows

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6447 
 
 
 
  Allow UTF8 files to have a leading BOM to be more tolerant of files produced on Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 
 
 
 
 
 
 
 UTF-8 files produced on Windows often contain a BOM.  Puppet now reads most files as utf-8, but doesn't allow for them to have a leading BOM.This can be a problem for end users on Windows, where they might need to go through workarounds to produce content without a BOM.  For instance, PowerShell can write files as UTF-8 with the {{Out-File}} cmdlet, specifying {{-Encoding UTF8}} - but the files are written with a BOM, which ends up blowing up Ruby if we try to read the files in Puppet  (under certain circumstances) .An easy solution is to modify any calls specifying {{utf-8}} when opening files for read, to instead specify {{bom|utf-8}}.  Ruby will handle the BOM correctly in this case. Note that the Ruby {{YAML.load_file}} API already handles the BOM situation correctly, so {{YAML}} files will generally be excluded from this problem. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (HI-520) Add Unicode specs for loading YAML files

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-520 
 
 
 
  Add Unicode specs for loading YAML files  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Affects Versions:
 

 HI 3.2.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Windows 
 
 
 

Created:
 

 2016/06/27 5:37 PM 
 
 
 

Labels:
 

 i18n utf-8 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Ethan Brown 
 
 
 
 
 
 
 
 
 
 
The Hiera yaml_load_file delegates to Rubys loading of YAML files which specifies :encoding => 'bom|utf8' when loading files. 
This isn't documented well, and we don't have any protection against regressions in the ability of Hiera to load YAML files (for instance, if another YAML parser was selected). 
Some additional specs should be added to cover this situation.

Jira (HI-519) Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown commented on  HI-519 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8  
 
 
 
 
 
 
 
 
 
 
Steve Barlow / Kenn Hussey I'm not sure the correct fixVersion here given I would like to target agent 1.6.0 if possible. I thought that that might be 3.3.0 and created that version... then realized it might actually be 3.2.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 (HI-519) Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-519 
 
 
 
  Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Fix Version/s:
 
 HI 3.3.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 (HI-519) Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-519 
 
 
 
  Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 HI 3.2.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/27 5:31 PM 
 
 
 

Fix Versions:
 

 HI 3.3.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Ethan Brown 
 
 
 
 
 
 
 
 
 
 
When using a YAML backend, files are automatically loaded as UTF-8 by default, thanks to Ruby code at https://github.com/ruby/ruby/blob/trunk/ext/psych/lib/psych.rb#L474-L476 
However, when loading JSON files, Puppet simply calls Ruby's File.read without specifying an encoding. On Windows this will cause problems trying to read UTF8 files, as Ruby will attempt to instead use the default external encoding. 
See code at https://github.com/puppetlabs/hiera/blob/4e85a733cbce09634a59005cda6ae169648c67ab/lib/hiera/filecache.rb#L50-L61 
The fix should be to specify :encoding => 'bom|utf8' as an option to File.read. 
If there are other consumers of the FileCache class, then the read_file method should probably take an additional options parameter so that callers may override the default behavior. 
It might also be useful to scan the

Jira (PDOC-81) @param tag help text should be in JSON

2016-06-27 Thread Jason Kincl (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Kincl created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-81 
 
 
 
  @param tag help text should be in JSON  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 DOCS 
 
 
 

Created:
 

 2016/06/27 5:28 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Jason Kincl 
 
 
 
 
 
 
 
 
 
 
When generating the JSON format, it should include the @param help text 
From the example README: 
 
 
 
 
 
 
# @param num_a [Integer] the first number to be compared
 
 
 
 
 
 
 
The "the first number to be compared" text should be in the JSON format output.

Jira (PUP-6445) Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6445 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor  
 
 
 
 
 
 
 
 
 
 
Two tickets raised and are linked 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6449) Update vendored win32-xxxx gems in puppet-agent

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6449 
 
 
 
  Update vendored win32- gems in puppet-agent  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/27 4:44 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Glenn Sarti 
 
 
 
 
 
 
 
 
 
 
As part of the investigation into PUP-6445 it was found that the vendored gems in puppet-agent are lagging behind what we test on etc. for the puppet gem. 
example locations to update; https://github.com/puppetlabs/puppet-win32-ruby/tree/2.1.9.0-x64/ruby/lib/ruby/gems/2.1.0/gems 
https://github.com/puppetlabs/puppet-agent/tree/master/configs/components 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA

Jira (PUP-6244) Acceptance: fix module upgrade tests

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6244 
 
 
 
  Acceptance: fix module upgrade tests  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 
 
 
 
 
 
 
 The following module upgrade acceptance tests are being skipped because they attempt to set the {{modulepath}} via {{puppet.conf}} which is no longer supported. These tests should be fixed and unskipped. * tests/modules/upgrade/that_was_installed_twice.rb* tests/modules/upgrade/with_scattered_dependencies.rb 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6245) Acceptance: fix zpool create zone test

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6245 
 
 
 
  Acceptance: fix zpool create zone test  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

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 (PUP-6409) "integer too big to convert to `int' at" with lookupvar

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Price commented on  PUP-6409 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "integer  too big to convert to `int' at" with lookupvar  
 
 
 
 
 
 
 
 
 
 
The timeout code does appear to use Java threads behind the scenes, but I don't see anywhere where it is creating another instance of one of these special RubyThread objects, and it seems like those objects are the ones that would have the offending object ID on them. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6244) Acceptance: fix module upgrade tests

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6244 
 
 
 
  Acceptance: fix module upgrade tests  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

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 (PUP-5501) basic_install.rb and with_version.rb module tests fail in AIX

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5501 
 
 
 
  basic_install.rb and with_version.rb module tests fail in AIX  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

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-5501) basic_install.rb and with_version.rb module tests fail in AIX

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5501 
 
 
 
  basic_install.rb and with_version.rb module tests fail in AIX  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

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 (PUP-1125) Exec checks should be turned into metaparameters

2016-06-27 Thread Felix Frank (JIRA)

Title: Message Title

Felix Frank commented on PUP-1125

Re: Exec checks should be turned into metaparameters

Hi Steve Potter,
late reply, I missed your post. Frankly, I don't believe that your use cases necessarily call for these metaparameters.
1) The list of DBvols per server should be part of their Hiera data. Puppet should be your authority for such things. Failing that, this example would warrant a custom fact, I believe.
2) In and of itself, it's tempting to force Puppet to not touch the user once it has been created. Please note the following factors, however:
1. There is a module to manage things only one: https://forge.puppet.com/binford2k/manageonce 2. If you use only_if or manageonce::, all other properties of your user resources will fall out of management as well. This can be undesirable.
Granted, the final point is tricky. Off the top of my head, I cannot think of a way to work around it cleanly without falling back to yet another custom fact.

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-2844) allow core and extensions tests to be run simultaneously

2016-06-27 Thread Wyatt Alt (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2844 
 
 
 
  allow core and extensions tests to be run simultaneously  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/27 4:12 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
This used to be possible, but today they try to use the same databases and interfere with each other. Sometimes it's useful to be able to run the suites at the same time. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-6447) Allow UTF8 files to have a leading BOM to be more tolerant of files produced on Windows

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6447 
 
 
 
  Allow UTF8 files to have a leading BOM to be more tolerant of files produced on Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 
 
 
 
 
 
 
 UTF-8 files produced on Windows often contain a BOM.  Puppet now reads most files as utf-8, but doesn't allow for them to have a leading BOM.This can be a problem for end users on Windows, where they might need to go through workarounds to produce content without a BOM.   For instance, PowerShell can write files as UTF-8 with the {{Out-File}} cmdlet, specifying {{-Encoding UTF8}} - but the files are written with a BOM, which ends up blowing up Ruby if we try to read the files in Puppet.   An easy solution is to modify any calls specifying {{utf-8}} when opening files for read, to instead specify {{bom|utf-8}}.  Ruby will handle the BOM correctly in this case. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6447) Allow UTF8 files to have a leading BOM to be more tolerant of files produced on Windows

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6447 
 
 
 
  Allow UTF8 files to have a leading BOM to be more tolerant of files produced on Windows  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Windows 
 
 
 

Created:
 

 2016/06/27 4:10 PM 
 
 
 

Labels:
 

 windows i18n utf-8 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Ethan Brown 
 
 
 
 
 
 
 
 
 
 
UTF-8 files produced on Windows often contain a BOM. Puppet now reads most files as utf-8, but doesn't allow for them to have a leading BOM. 
This can be a problem for end users on Windows, where they might need to go through workarounds to produce content without a BOM. An easy solution is to modify any calls specifying utf-8 when opening files for read, to instead specify bom|utf-8. Ruby will handle the BOM correctly in this case.

Jira (PUP-6447) Allow UTF8 files to have a leading BOM to be more tolerant of files produced on Windows

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6447 
 
 
 
  Allow UTF8 files to have a leading BOM to be more tolerant of files produced on Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Fix Version/s:
 
 PUP 4.6.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6409) "integer too big to convert to `int' at" with lookupvar

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6409 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "integer  too big to convert to `int' at" with lookupvar  
 
 
 
 
 
 
 
 
 
 
Isn't things like "timeouts" also done with threads? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6430) Support Fedora 24 in DNF

2016-06-27 Thread Rick Sherman (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rick Sherman commented on  PUP-6430 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support Fedora 24 in DNF  
 
 
 
 
 
 
 
 
 
 
I'm good with that. Just seems like wasted effort to have to bump this list twice a year. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6430) Support Fedora 24 in DNF

2016-06-27 Thread Peter Souter (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Souter commented on  PUP-6430 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support Fedora 24 in DNF  
 
 
 
 
 
 
 
 
 
 
Rick Sherman I asked around about doing that, right now it'd require changes to the defaultfor method... can we split that into a separate ticket? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1447) Debug logging when Windows identity resolution fails throws an exception

2016-06-27 Thread Michael Smith (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1447 
 
 
 
  Debug logging when Windows identity resolution fails throws an exception  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 FACT 3.0.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/27 3:08 PM 
 
 
 

Fix Versions:
 

 FACT 3.3.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Michael Smith 
 
 
 
 
 
 
 
 
 
 
When resolving identity facts on Windows fails, it will attempt to log some things to debug. However, that's not helpful because attempting to log triggers an exception: 
 
 
 
 
 
 
2016-06-24 19:43:22.586970 DEBUG puppetlabs.facter - resolving id facts. 
 
 
 
 
2016-06-24 19:43:22.586970 FATAL puppetlabs.facter - unhandled exception: boost::too_few_args: format-string referred to more

Jira (PUP-6430) Support Fedora 24 in DNF

2016-06-27 Thread Rick Sherman (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rick Sherman commented on  PUP-6430 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support Fedora 24 in DNF  
 
 
 
 
 
 
 
 
 
 
I'd like to propose we change the provider to default to DNF for >= 22. If and when there is a new package management tool we can limit the scope then   
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6409) "integer too big to convert to `int' at" with lookupvar

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Price commented on  PUP-6409 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "integer  too big to convert to `int' at" with lookupvar  
 
 
 
 
 
 
 
 
 
 
One thing I notice is that some of the obvious places where JRuby ends up creating these thread objects is in calls to `popen3`, so I'd be curious whether or not you happen to be using that or similar methods for launching external processes in any of your modules? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6445) Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown commented on  PUP-6445 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor  
 
 
 
 
 
 
 
 
 
 
Merged up to master in https://github.com/puppetlabs/puppet/commit/c7ce556cef0e98f84a4f7a86ad097536740632fb 
Glenn Sarti could you file 2 new related tickets for this? 
 

Updating modulesync Gemfile / updating all modules with this new pinning
 

Updating the puppet-agent repo to pin to the same versions for the agent releases based on Vanagon
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6409) "integer too big to convert to `int' at" with lookupvar

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Price commented on  PUP-6409 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "integer  too big to convert to `int' at" with lookupvar  
 
 
 
 
 
 
 
 
 
 
Jürgen Thomann when this begins to happen to you, does it affect 100% of the catalog compilations that are looking up an undefined variable? Or is it only a subset of them? 
I'm poking around in this JRuby code, trying to think of a way that I can write a more reliable reproducer, and it's weird to me that the exception seems like it may be related to a RubyThread object, when we shouldn't be using any threads inside of the JRuby containers. It seems like generating a bunch of ruby objects in order to get that ObjectId counter into the "too high" territory will be easy, but it seems like after that I have to figure out how to cause a new RubyThread to be allocated. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6445) Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown commented on  PUP-6445 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor  
 
 
 
 
 
 
 
 
 
 
Merged to stable branch, targeting Puppet 4.5.3 release at https://github.com/puppetlabs/puppet/commit/2c586c242c883800f04411ada8bb8e44f7f4abb9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6233) Serivce SMF restart should use -s

2016-06-27 Thread William Hopper (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6233 
 
 
 
  Serivce SMF restart should use -s  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Acceptance Criteria:
 
 When restarting a service with puppet in Solaris 11 .2 , the {{-s}} flag should be used, which makes the restart action atomic. SMF (and thus puppet) should not return before the service has finished restarting.  In Solaris 11.1 and older, the {{-s}} flag should not be used, 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6233) Serivce SMF restart should use -s

2016-06-27 Thread William Hopper (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  PUP-6233 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Serivce SMF restart should use -s  
 
 
 
 
 
 
 
 
 
 
And another failure - the original implementation didn't take into account the fact that the -s flag for smf restart only exists in Solaris 11.2 and above (see https://blogs.oracle.com/SolarisSMF/entry/synchronous_actions). I put a PR up to address the issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6094) {{puppet -h|--help}} should be equivalent to {{puppet help}}

2016-06-27 Thread Michael Smith (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  PUP-6094 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: {{puppet -h|--help}} should be equivalent to {{puppet help}}  
 
 
 
 
 
 
 
 
 
 
Lori Landesman any consideration that we might want to take advantage of this discrepancy in Puppet to introduce new help output? I guess I'm on the side of avoiding too many variations on similar behavior, so I'd rather have puppet help and puppet --help do the same thing. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6432) Puppet::Util::Execution.execute cannot handle Unicode output on Windows

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6432 
 
 
 
  Puppet::Util::Execution.execute cannot handle Unicode output on Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 Windows  Triage  2016-07-27 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1446) Improve the windows user check in facter/acceptance/test/facts/window.rb

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1446 
 
 
 
  Improve the windows user check in facter/acceptance/test/facts/window.rb  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 Windows  Triage  2016-07-27 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6438) Parallel spec on Windows improvements, assoc lib/provider refactors

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6438 
 
 
 
  Parallel spec on Windows improvements, assoc lib/provider refactors  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

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-6438) Parallel spec on Windows improvements, assoc lib/provider refactors

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6438 
 
 
 
  Parallel spec on Windows improvements, assoc lib/provider refactors  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Acceptance Criteria:
 
 All puppet CI tests remain green.Spec tests running in parallel 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6323) Support tdnf package provider for VMware PhotonOS

2016-06-27 Thread Maggie Dreyer (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6323 
 
 
 
  Support tdnf package provider for VMware PhotonOS  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 

Scope Change Reason:
 
 Extra bandwidth, onboarding 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6323) Support tdnf package provider for VMware PhotonOS

2016-06-27 Thread Maggie Dreyer (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6323 
 
 
 
  Support tdnf package provider for VMware PhotonOS  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 

Sprint:
 
 Client 2016- 07 06 - 13 29  ( HA, 1.5.3 failover ) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6445) Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti assigned an issue to Ethan Brown 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6445 
 
 
 
  Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Assignee:
 
 Ethan Brown 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1927) Yum Package Provider Ignores Source Parameter

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1927 
 
 
 
  Yum Package Provider Ignores Source Parameter  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6446) Cant use 'master' or 'agent' as environment names

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to javipolo 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6446 
 
 
 
  Cant use 'master' or 'agent' as environment names  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 javipolo 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6446) Cant use 'master' or 'agent' as environment names

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6446 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cant use 'master' or 'agent' as environment names  
 
 
 
 
 
 
 
 
 
 
Is this still the case on 4.x? In 3.x the names you used (main, agent, master) are reserved as it is possible in 3.x. to create dynamic environments in the conf itself by simply using names other than those that have defined sections in the conf. Those so called "dynamic environments" are no longer supported. On puppet 4.x the environment name environment is reserved. (Have to check the documentation if other names are also reserved). 
If this ticket is for 3.x only, then we are not going to make changes (we cannot because of the dynamic environments). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1427) identity.privileged fact is not set on zlinux based sles11

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1427 
 
 
 
  identity.privileged fact is not set on zlinux based sles11  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

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 (FACT-1427) identity.privileged fact is not set on zlinux based sles11

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1427 
 
 
 
  identity.privileged fact is not set on zlinux based sles11  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment Reason:
 
 Covered by existing acceptance tests 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1427) identity.privileged fact is not set on zlinux based sles11

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1427 
 
 
 
  identity.privileged fact is not set on zlinux based sles11  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1427) identity.privileged fact is not set on zlinux based sles11

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1427 
 
 
 
  identity.privileged fact is not set on zlinux based sles11  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5909) Implement a PCore serializer for JSON Machine to Machine

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5909 
 
 
 
  Implement a PCore serializer for JSON Machine to Machine  
 
 
 
 
 
 
 
 
 

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-6138) Acceptance: pin to released version of puppet-server

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6138 
 
 
 
  Acceptance: pin to released version of puppet-server  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

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 (PDB-2834) Use :unbuffered-stream instead of :stream in extensions

2016-06-27 Thread Susan McNerney (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Susan McNerney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2834 
 
 
 
  Use :unbuffered-stream instead of :stream in extensions  
 
 
 
 
 
 
 
 
 

Change By:
 
 Susan McNerney 
 
 
 

Due Date:
 
 2016/07/19 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2834) Use :unbuffered-stream instead of :stream in extensions

2016-06-27 Thread Susan McNerney (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Susan McNerney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2834 
 
 
 
  Use :unbuffered-stream instead of :stream in extensions  
 
 
 
 
 
 
 
 
 

Change By:
 
 Susan McNerney 
 
 
 

Fix Version/s:
 
 PDB 4.1.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-6430) Support Fedora 24 in DNF

2016-06-27 Thread Kenn Hussey (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6430 
 
 
 
  Support Fedora 24 in DNF  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenn Hussey 
 
 
 

Sub-team:
 
 Platforms 
 
 
 

Scrum Team:
 
 Release Engineering 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-348) Facter should provide a convenient way to cache values

2016-06-27 Thread Kenn Hussey (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  FACT-348 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter should provide a convenient way to cache values  
 
 
 
 
 
 
 
 
 
 
Eric Sorenson do you have an update on whether/when we should be pursuing this? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2834) Use :unbuffered-stream instead of :stream in extensions

2016-06-27 Thread Rajasree Talla (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rajasree Talla commented on  PDB-2834 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Use :unbuffered-stream instead of :stream in extensions  
 
 
 
 
 
 
 
 
 
 
Ryan SeniorSusan McNerney Couch release leads approved this fix to go in to Couch Z. Please make sure the appropriate PDB version is attached to this. As an FYI, we are targeting all FOSS releases to land by July 19 for 2016.1.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-6446) Cant use 'master' or 'agent' as environment names

2016-06-27 Thread javipolo (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 javipolo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6446 
 
 
 
  Cant use 'master' or 'agent' as environment names  
 
 
 
 
 
 
 
 
 

Change By:
 
 javipolo 
 
 
 
 
 
 
 
 
 
 When using an environment named *master*, *agent* or *main*, it does not workHere I show having 2 environments named *production* and *master*When I get modulepath for *production* expansion is correctly done and everything works fine, but when I try to get it for *master* environment, it just prints the default basemodulepath{code} # Show environments config root@puppetmaster:~# grep environments /etc/puppet/puppet.confenvironmentpath = $confdir/environmentsroot@puppetmaster:~# # GOOD root@puppetmaster:~# cat /etc/puppet/environments/production/environment.conf modulepath=./modules:./external_modules:$basemodulepathroot@puppetmaster:~# puppet config print modulepath --environment production/etc/puppet/environments/production/modules:/etc/puppet/environments/production/external_modules:/etc/puppet/modules:/usr/share/puppet/modulesroot@puppetmaster:~# # WRONG root@puppetmaster:~# cat /etc/puppet/environments/master/environment.conf modulepath=./modules:./external_modules:$basemodulepathroot@puppetmaster:~# puppet config print modulepath --environment master/etc/puppet/modules:/usr/share/puppet/modulesroot@puppetmaster:~#{code}It's quite trivial to reproduce it, just create a new environment named after those reserved words ... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

Jira (PUP-6446) Cant use 'master' or 'agent' as environment names

2016-06-27 Thread javipolo (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 javipolo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6446 
 
 
 
  Cant use 'master' or 'agent' as environment names  
 
 
 
 
 
 
 
 
 

Change By:
 
 javipolo 
 
 
 
 
 
 
 
 
 
 When using an environment named *master*, *agent* or *main*, it does not workHere I show having 2 environments named *production* and *master*When I get modulepath for *production* expansion is correctly done and everything works fine, but when I try to get it for *master* environment, it just prints the default basemodulepath{code}root@puppetmaster:~# grep environments /etc/puppet/puppet.confenvironmentpath = $confdir/environmentsroot@puppetmaster:~#  cat /etc/puppet/environments/production/environment.conf modulepath=./modules:./external_modules:$basemodulepath   root@puppetmaster:~# cat /etc/puppet/environments/ master production /environment.conf modulepath=./modules:./external_modules:$basemodulepathroot@puppetmaster:~# puppet config print modulepath --environment production/etc/puppet/environments/production/modules:/etc/puppet/environments/production/external_modules:/etc/puppet/modules:/usr/share/puppet/modulesroot@puppetmaster:~# root@puppetmaster:~# cat /etc/  puppet /environments/master/environment.conf modulepath=./modules:./external_modules:$basemodulepathroot@puppetmaster:~# puppet  config print modulepath --environment master/etc/puppet/modules:/usr/share/puppet/modulesroot@puppetmaster:~#{code}It's quite trivial to reproduce it, just create a new environment named after those reserved words ... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are

Jira (PUP-6446) Cant use 'master' or 'agent' as environment names

2016-06-27 Thread javipolo (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 javipolo created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6446 
 
 
 
  Cant use 'master' or 'agent' as environment names  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.8.7 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Puppet Server 
 
 
 

Created:
 

 2016/06/27 10:25 AM 
 
 
 

Environment:
 
 
linux, debian jessie 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 javipolo 
 
 
 
 
 
 
 
 
 
 
When using an environment named master, agent or main, it does not work 
Here I show having 2 environments named production and master When I get modulepath for production expansion is correctly done and everything works fine, but when I try to get it for master environment, it just prints the default basemodulepath

Jira (PUP-6445) Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6445 
 
 
 
  Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 
 
 
 
 
 
 
 During investigation into CI PR failures for Puppet [~daniel.lu] found that several gems had been updated and that all subsequent PRs in Appveyor were failing with the same error.e.g.{code}C:\source\puppet-pete>bundle exec rspec spec/unitDL is deprecated, please use FiddleC:/source/puppet-pete/lib/puppet/defaults.rb:274:in `block in ': undefined method `split' for nil:NilClass (NoMethodError)from C:/source/puppet-pete/lib/puppet/settings.rb:919:in `block in define_settings'from C:/source/puppet-pete/lib/puppet/settings.rb:918:in `each'from C:/source/puppet-pete/lib/puppet/settings.rb:918:in `define_settings'from C:/source/puppet-pete/lib/puppet.rb:81:in `define_settings'from C:/source/puppet-pete/lib/puppet/defaults.rb:151:in `'from C:/source/puppet-pete/lib/puppet/defaults.rb:1:in `'from C:/source/puppet-pete/lib/puppet.rb:116:in `require'from C:/source/puppet-pete/lib/puppet.rb:116:in `'from C:/source/puppet-pete/lib/puppet.rb:33:in `'{code}This error could replicated locally on a Windows workstation as well. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

Jira (PUP-6445) Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6445 
 
 
 
  Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Acceptance Criteria:
 
 Puppet should not errorPuppet should pass all unit  and integration tests 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6445) Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti assigned an issue to Glenn Sarti 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6445 
 
 
 
  Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Assignee:
 
 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 (FACT-1422) Facter should detect PhotonOS

2016-06-27 Thread William Hopper (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  FACT-1422 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter should detect PhotonOS  
 
 
 
 
 
 
 
 
 
 
Gareth Rushgrove Can we assume the release string 1.0 TP2 equates to Major version 1, minor version 0, full version 1.0 TP2? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1427) identity.privileged fact is not set on zlinux based sles11

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte assigned an issue to John Duarte 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1427 
 
 
 
  identity.privileged fact is not set on zlinux based sles11  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Assignee:
 
 John Duarte 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1427) identity.privileged fact is not set on zlinux based sles11

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte commented on  FACT-1427 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: identity.privileged fact is not set on zlinux based sles11  
 
 
 
 
 
 
 
 
 
 
Need to retest. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6445) Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6445 
 
 
 
  Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Priority:
 
 Normal Blocker 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6445) Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6445 
 
 
 
  Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Affects Version/s:
 
 PUP 4.5.2 
 
 
 

Story Points:
 
 1 
 
 
 

Sprint:
 
 Windows 2016-06-29 
 
 
 

Scrum Team:
 
 Windows 
 
 
 

Fix Version/s:
 
 PUP 4.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

Jira (PUP-6445) Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6445 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor  
 
 
 
 
 
 
 
 
 
 
PR Added https://github.com/puppetlabs/puppet/pull/5062 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1427) identity.privileged fact is not set on zlinux based sles11

2016-06-27 Thread Steve Barlow (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1427 
 
 
 
  identity.privileged fact is not set on zlinux based sles11  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

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 (PUP-6409) "integer too big to convert to `int' at" with lookupvar

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Price commented on  PUP-6409 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "integer  too big to convert to `int' at" with lookupvar  
 
 
 
 
 
 
 
 
 
 
Yes, thank you Jürgen Thomann! I'll keep an eye on that JRuby ticket, and also read through this code again to see if it gives me a better idea of how to come up with a local reproducer so that we can confirm the JRuby fix when it goes 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-6445) Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6445 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor  
 
 
 
 
 
 
 
 
 
 
There is a namespacing problem 
https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/api_types.rb#L56-L60 
versus the new gem ffi_win32-extensions 
https://github.com/djberg96/ffi-win32-extensions/blob/master/lib/ffi/win32/extensions.rb#L21-L25 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6445) Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6445 
 
 
 
  Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/27 9:45 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

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

Jira (PUP-6424) Passenger failing on Ubuntu 12.04 (precise)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte commented on  PUP-6424 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Passenger failing on Ubuntu 12.04 (precise)  
 
 
 
 
 
 
 
 
 
 
Running with rake ci:test:git passes where rake ci:test:packages fails. 
Given an isolated test (tests/environments/static.rb at SHA 5e4da09), here are the results: 
Git 
 
 
 
 
 
 
 $ bundle exec rake ci:test:git CONFIG=config/nodes/precise.yaml  SHA=5e4da09f3320e3c0109dc3108cd5ff4bbabf9997  FORK=puppetlabs TESTS=tests/environment/static.rb 
 
 
 
 
  
 
 
 
 
  - Test Case Summary for suite 'tests' - 
 
 
 
 
   Total Suite Time: 30.65 seconds 
 
 
 
 
  Average Test Time: 30.65 seconds 
 
 
 
 
  Attempted: 1 
 
 
 
 
 Passed: 1 
 
 
 
 
 Failed: 0 
 
 
 
 
Errored: 0

Jira (PUP-1927) Yum Package Provider Ignores Source Parameter

2016-06-27 Thread Marco Rodrigues (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Marco Rodrigues commented on  PUP-1927 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Yum Package Provider Ignores Source Parameter  
 
 
 
 
 
 
 
 
 
 
We are in the version 4 of Puppet and this is still not supported. 
 package { "puppet-agent": provider => 'yum', ensure => 'latest', source => "puppet:///modules/$ {module_name} 
/puppet-agent-1.5.2-1.el7.x86_64.rpm" } 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6361) Validate and error if a class or define is given a name starting with ::

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6361 
 
 
 
  Validate and error if a class or define is given a name starting with ::  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Henrik Lindberg 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.

Jira (PUP-6272) CI failure in acceptance tests: acceptance/tests/environment/{environment_scenario-bad.rb,environment_scenario-non_existent.rb}

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6272 
 
 
 
  CI failure in acceptance tests: acceptance/tests/environment/{environment_scenario-bad.rb,environment_scenario-non_existent.rb}   
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6272) CI failure in acceptance tests: acceptance/tests/environment/{environment_scenario-bad.rb,environment_scenario-non_existent.rb}

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6272 
 
 
 
  CI failure in acceptance tests: acceptance/tests/environment/{environment_scenario-bad.rb,environment_scenario-non_existent.rb}   
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

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 (FACT-1422) Facter should detect PhotonOS

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1422 
 
 
 
  Facter should detect PhotonOS  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment Reason:
 
 Not yet a supported OS 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1422) Facter should detect PhotonOS

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1422 
 
 
 
  Facter should detect PhotonOS  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1422) Facter should detect PhotonOS

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1422 
 
 
 
  Facter should detect PhotonOS  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2843) Exceptions when using functions

2016-06-27 Thread Wyatt Alt (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-2843 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Exceptions when using functions  
 
 
 
 
 
 
 
 
 
 
The input and output schemas for the fact-contents munge function need to be wrapped with query/wrap-with-supported-fns. While we're at it we should double check that other endpoints didn't slip through the cracks. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6409) "integer too big to convert to `int' at" with lookupvar

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6409 
 
 
 
  "integer  too big to convert to `int' at" with lookupvar  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 The lookupvar function started failing after some time without any reason with a error message "Puppet Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, integer 2181729414 too big to convert to `int' at "this occured on 2 puppetserver at the same time (were restarted at the same time) and also only occur if the name to look up does not exist.I found someone with the same problem in the irc logs of #puppet and there it couldn't be debugged, because a restart fixed it. I still have them running as I could workaround this problem and so they still can be used for debugging. (User: Spec, logs at https://botbot.me/freenode/puppet/2016-05-31/)Stacktrace from puppetserver log is attached. Interesting is that the number which couldn't be converted is increasing over time UPDATEThis cause of this problem was found to be in JRuby  - see link "JRuby issue 3980". 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6409) "integer too big to convert to `int' at" with lookupvar