Jira (PUP-8231) Group resource - unable to add new member if there is existing IIS AppPool\user

2017-12-06 Thread Halim Wijaya (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Halim Wijaya created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8231 
 
 
 
  Group resource - unable to add new member if there is existing IIS AppPool\user  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/12/06 5:38 PM 
 
 
 

Environment:
 
 
Reproduce in Win 2012 R2, but should affect most windows platform 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Halim Wijaya 
 
 
 
 
 
 
 
 
 
 
Steps to reproduce 
1. Create Group "TestGroup" with "IIS AppPool\DefaultAppPool" as a member 
 
 
 
 
 
 
group { 'TestGroup': 
 
 
 
 
name=> 'TestGroup', 
 
 
 
 
ensure  => present, 
 
 
  

Jira (FACT-1796) OSX puppet facts run in japanese with facter errors returns "invalid byte sequence in US-ASCII"

2017-12-06 Thread Maggie Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer commented on  FACT-1796 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: OSX puppet facts run in japanese with facter errors returns "invalid byte sequence in US-ASCII"  
 
 
 
 
 
 
 
 
 
 
Eric Delaney I am unable to reproduce this on a clean pooler VM by just installing the Agent package. Do you have more details on what environment caused it to show up? Is it specifically when beaker is involved? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3778) Add puppetdb release steps to winston

2017-12-06 Thread Molly Waggett (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Molly Waggett created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3778 
 
 
 
  Add puppetdb release steps to winston  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/12/06 4:20 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Molly Waggett 
 
 
 
 
 
 
 
 
 
 
Open a PR against winston to fill in ticket details for puppetdb-specific tasks of a platform release. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 

Jira (PDB-3684) PDB performance issues with large structured facts

2017-12-06 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3684 
 
 
 
  PDB performance issues with large structured facts  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
  As outlined in PDB-2631, PuppetDB encounters severe performance degradation in the presence of large structured facts.  In support, we have seen this impact with mountpoint or partitions facts of only 20-30 KiB, which is not terribly uncommon.  As noted in that ticket, the expectation is that PDB will be able to handle anything Facter might throw at it.This issue was resolved in PDB-3249, but the fix was removed by PDB-3611.  We need a solution that will allow large structured facts to be stored in PDB without causing causing query performance issues. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3684) PDB performance issues with large structured facts

2017-12-06 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-3684 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PDB performance issues with large structured facts  
 
 
 
 
 
 
 
 
 
 
We believe these issues will be resolved with https://github.com/puppetlabs/puppetdb/pull/2410 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8230) Puppet Platform Release Process Improvements

2017-12-06 Thread Molly Waggett (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Molly Waggett created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8230 
 
 
 
  Puppet Platform Release Process Improvements  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Epic 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/12/06 4:10 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Molly Waggett 
 
 
 
 
 
 
 
 
 
 
Making https://docs.google.com/a/puppet.com/spreadsheets/d/1WlxG0-pVDK3LqlPHhzI8yuZFmwlioTvEEtIL3EBEhRI/edit?usp=sharing a reality. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 

Jira (PUP-7630) "Successful" puppet agent reports hide provider errors

2017-12-06 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7630 
 
 
 
  "Successful" puppet agent reports hide provider errors  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.10.z 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-156) implement powershell input method

2017-12-06 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette commented on  BOLT-156 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: implement powershell input method  
 
 
 
 
 
 
 
 
 
 
Okay. I removed that line. Thank you. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-156) implement powershell input method

2017-12-06 Thread Nick Lewis (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Lewis commented on  BOLT-156 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: implement powershell input method  
 
 
 
 
 
 
 
 
 
 
Michelle Fredette This change basically corresponds to this section of the docs, making it now apply to Bolt and not just PE. I don't think there's anywhere else in the bolt docs that we need to mention this, but we should remove the note that says it's PE-only. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-81) Error message regarding ssh-agent on successful run

2017-12-06 Thread Nick Lewis (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Lewis commented on  BOLT-81 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Error message regarding ssh-agent on successful run   
 
 
 
 
 
 
 
 
 
 
Annoyingly, this message comes at the error level directly from net-ssh, without any way to directly avoid it beyond telling it not to use an agent... 
We could configure net-ssh log level to 'fatal' unless bolt's verbosity has been turned up. It's a little weird that we would hide all net-ssh errors by default, but at the same time, anything truly impactful should also be surfaced by bolt. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-156) implement powershell input method

2017-12-06 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette commented on  BOLT-156 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: implement powershell input method  
 
 
 
 
 
 
 
 
 
 
Nick Lewis - does this need documentation? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-156) implement powershell input method

2017-12-06 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-156 
 
 
 
  implement powershell input method  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michelle Fredette 
 
 
 

Labels:
 
 docs_reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-156) implement powershell input method

2017-12-06 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette commented on  BOLT-156 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: implement powershell input method  
 
 
 
 
 
 
 
 
 
 
I added a release note for this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-125) Support WinRM over SSL

2017-12-06 Thread Nick Lewis (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Lewis updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-125 
 
 
 
  Support WinRM over SSL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nick Lewis 
 
 
 

Sprint:
 
 Bolt  Kanban  One Point Oh 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-125) Support WinRM over SSL

2017-12-06 Thread Nick Lewis (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Lewis assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-125 
 
 
 
  Support WinRM over SSL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nick Lewis 
 
 
 

Assignee:
 
 Nick Lewis 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3770) anonymization via the "puppet db export" command not working

2017-12-06 Thread Jeff Yarnell (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeff Yarnell updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3770 
 
 
 
  anonymization via the "puppet db export" command not working  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jeff Yarnell 
 
 
 

Sprint:
 
 DISC Data Platform  2017-12-13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7432) Improve Beaker Workflow

2017-12-06 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7432 
 
 
 
  Improve Beaker Workflow  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sub-team:
 
 Coremunity 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7542) Puppet Config

2017-12-06 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7542 
 
 
 
  Puppet Config  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sub-team:
 
 Coremunity 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8144) Merge Strategy 'first|unique|hash' documentation is unclear

2017-12-06 Thread Kari Halsted (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kari Halsted commented on  PUP-8144 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Merge Strategy 'first|unique|hash' documentation is unclear  
 
 
 
 
 
 
 
 
 
 
Ah, yeah, I see what's going on in the docs. The behavior of  {strategy=>first}, {strategy=>hash}, {strategy=>unique}, and {strategy=>deep...} is already described in the sections higher up in the page, and we should just remove this section which is causing confusion (and also the one below it about deep).   The phrase "Same as the string versions of these merge behaviors" is trying (and failing) to say that saying "first" is the same as saying {strategy=>first} 
. 
Claire, can you take out the two sections " {'strategy' => 'first|unique|hash'} 
" and " {'strategy' => 'deep',  => , ...} 
"? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3699) allow PQL queries to be stored and executed by name

2017-12-06 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-3699 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: allow PQL queries to be stored and executed by name  
 
 
 
 
 
 
 
 
 
 
Would it make sense to make this a feature of the CLI tool itself? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6823) Puppet filebucket command does not pick up proper server address from server_list config property

2017-12-06 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-6823 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet filebucket command does not pick up proper server address from server_list config property  
 
 
 
 
 
 
 
 
 
 
Merged to master in https://github.com/puppetlabs/puppet/commit/b8d86e43110f3d84815053f840925db82c397f91 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3956) Puppet master doesn't free file descriptor after USR2

2017-12-06 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-3956 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet master doesn't free file descriptor after USR2  
 
 
 
 
 
 
 
 
 
 
Paul Raines I used puppet 4.8 or later. Puppet 3.x is no longer supported. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-156) implement powershell input method

2017-12-06 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-156 
 
 
 
  implement powershell input method  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Release Notes Summary:
 
 This allows bolt to call powershell tasks with the native powershell input method. It changes the default input method for .ps1 tasks any tasks that rely on environment variables will need to include that in metadata to continue working with Bolt. 
 
 
 

Release Notes:
 
 New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-241) Load config options from a file

2017-12-06 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-241 
 
 
 
  Load config options from a file  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Release Notes Summary:
 
 Bolt will now load config options from a file '~/.puppetlabs/bolt.yml' or the path specified on the commandline with --configfile 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-156) implement powershell input method

2017-12-06 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-156 
 
 
 
  implement powershell input method  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Fix Version/s:
 
 BOLT 0.10.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3757) Convert select_facts to work with jsonb

2017-12-06 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3757 
 
 
 
  Convert select_facts to work with jsonb  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Browning 
 
 
 

Assignee:
 
 Rob Browning 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3777) (maint) Fix artifactory url

2017-12-06 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3777 
 
 
 
  (maint) Fix artifactory url  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/12/06 10:07 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
Both resolve to the same place, this one is better 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
  

Jira (PDB-3776) (maint) Fix artifactory url

2017-12-06 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3776 
 
 
 
  (maint) Fix artifactory url  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/12/06 10:03 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
Both resolve to the same place, this one is better 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
  

Jira (PDB-3775) (maint) Fix artifactory url

2017-12-06 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3775 
 
 
 
  (maint) Fix artifactory url  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/12/06 10:02 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
Both resolve to the same place, this one is better 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
  

Jira (BOLT-245) predocs for config file

2017-12-06 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-245 
 
 
 
  predocs for config file  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 
 
 
 
 
 
 
 PR: https://github.com/puppetlabs/bolt/pull/182 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-245) predocs for config file

2017-12-06 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer assigned an issue to Michelle Fredette 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-245 
 
 
 
  predocs for config file  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Assignee:
 
 Michelle Fredette 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-245) predocs for config file

2017-12-06 Thread Jonathan Newman (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jonathan Newman updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-245 
 
 
 
  predocs for config file  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jonathan Newman 
 
 
 

Sub-team:
 
 Bolt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3757) Convert select_facts to work with jsonb

2017-12-06 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning assigned an issue to Rob Browning 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3757 
 
 
 
  Convert select_facts to work with jsonb  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Browning 
 
 
 

Assignee:
 
 Rob Browning 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-245) predocs for config file

2017-12-06 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-245 
 
 
 
  predocs for config file  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/12/06 9:04 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Alex Dreyer 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-241) Load config options from a file

2017-12-06 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-241 
 
 
 
  Load config options from a file  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Fix Version/s:
 
 BOLT 0.10.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-5402) systemd: Puppet agent starts before network-online.target is reached

2017-12-06 Thread Christian Lecherbauer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Lecherbauer commented on  PUP-5402 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: systemd: Puppet agent starts before network-online.target is reached  
 
 
 
 
 
 
 
 
 
 
The issue also exists with Ubuntu 17.10. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8177) Older server version errors when an agent tries to download from the locales mountpoint

2017-12-06 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8177 
 
 
 
  Older server version errors when an agent tries to download from the locales mountpoint  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

QA Risk Assessment Reason:
 
 we are adding unit tests 
 
 
 

QA Risk Assessment:
 
 Needs Assessment No Action 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3770) anonymization via the "puppet db export" command not working

2017-12-06 Thread Jeff Yarnell (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeff Yarnell updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3770 
 
 
 
  anonymization via the "puppet db export" command not working  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jeff Yarnell 
 
 
 

Sprint:
 
 Hopper/Triage DISC 2017-12-13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3770) anonymization via the "puppet db export" command not working

2017-12-06 Thread Jeff Yarnell (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeff Yarnell assigned an issue to AJ Roetker 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3770 
 
 
 
  anonymization via the "puppet db export" command not working  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jeff Yarnell 
 
 
 

Assignee:
 
 AJ Roetker 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1797) Amazon EC2 C5 Instances not detected as is_virtual causing ec2_metadata fact data not to resolve

2017-12-06 Thread Josef Hartmann (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josef Hartmann commented on  FACT-1797 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Amazon EC2 C5 Instances not detected as is_virtual causing ec2_metadata fact data not to resolve  
 
 
 
 
 
 
 
 
 
 
I just verified RHEL7.4 Linux @C5 and it does show ec2_* facts using facter 3.6.6. Linux does provide facts as virt-what (virt-what-1.13-10.el7.x86_64) provides "kvm" as hypervisor. It is ahead of Windows but WIN facts and LX facts are not consistent. 
Win2016@C5 is reporting "physical". 
As Mark Bentley wrote Amazon does set a new manufacturer. That's what the Windows code should deal with. Linux just uses virt-what. I would create a merge request however I wasn't yet able to build facter on Windows (neither mingw, nor vcsc) due to compilation issues within dependencies. [off-topic] Does anybody know a "ready-to-use setup" to compile facter on Windows (e.g. which mingw version)? 
LX- M1.medium: 
 

virt-what xen xen-hvm #
 
 
WIN t2.medium C:\Windows\system32>facter|findstr /i manu manufacturer => "Xen", C:\Windows\system32>facter -v 3.6.6 C:\Windows\system32>facter virtual xen 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8229) Regression in Puppet system loader

2017-12-06 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8229 
 
 
 
  Regression in Puppet system loader  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 

Created:
 

 2017/12/06 5:09 AM 
 
 
 

Fix Versions:
 

 PUP 5.4.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
One of the commits for PUP-7864 caused a regression in the puppet system loader because it assumed that 'puppet/lib' would always be reachable using 'lib'. The regression was caught in acceptance tests where the 'puppet/lib' folder is renamed to 'site_ruby'. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
  

Jira (PDB-3774) Puppetserver not restarted if termini gem is upgraded

2017-12-06 Thread JIRA
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jan Örnstedt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3774 
 
 
 
  Puppetserver not restarted if termini gem is upgraded  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/12/06 5:00 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Jan Örnstedt 
 
 
 
 
 
 
 
 
 
 
If the puppet module puppetdb upgrades the termini package puppetserver will not be refreshed. 
https://github.com/puppetlabs/puppetlabs-puppetdb/blob/78b9df2f20d623ad59259ad8b507cb322484473a/manifests/master/config.pp#L167 Only takes config changes into consideration not gem updates. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 

Jira (PUP-6162) Type errors for type annotations used in v4 functions can use some user friendliness

2017-12-06 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6162 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Type errors for type annotations used in v4 functions can use some user friendliness  
 
 
 
 
 
 
 
 
 
 
We should do two things: 
 

When function loading fails, it should say that is the problem and identify the function
 

When a local type fails, it should indicate where the problem is
 

When parsing of an argument type fails it should indicate where the problem is
 
 
The original reported issue does not use the feature local_types which it should use instead of just defining it as a string - it should still get a better error message though. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6162) Type errors for type annotations used in v4 functions can use some user friendliness

2017-12-06 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6162 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Type errors for type annotations used in v4 functions can use some user friendliness  
 
 
 
 
 
 
 
 
 
 
The current error message is: 
 
 
 
 
 
 
Error: Evaluation Error: Error while evaluating a Function Call, 'nameless::discover' expects one of: 
 
 
 
 
  (String service, Array pods, Struct[{'protocol' => Optional[String], 'type' => Optional[Enum['a', 'srv']], 'min_records' => Optional[Integer]}] options?) 
 
 
 
 
rejected: parameter 'pods' expects an Array value, got String 
 
 
 
 
  (String service, String pod, Struct[{'protocol' => Optional[String], 'type' => Optional[Enum['a', 'srv']], 'min_records' => Optional[Integer]}] options?) 
 
 
 
 
rejected: parameter 'options' entry 'type' expects an undef value or a match for Enum['a', 'srv'], got 'cname'  at line 1:1 on node laptop
 
 
 
 
 
 
 
The error message no longer says anything about a type mismatch. 
Also see PUP-7792 which also requests improved error message. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
  

Jira (PUP-7792) argument type mismatch message could be clearer

2017-12-06 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Adam Buxton 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7792 
 
 
 
  argument type mismatch message could be clearer  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Henrik Lindberg Adam Buxton 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7792) argument type mismatch message could be clearer

2017-12-06 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-7792 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: argument type mismatch message could be clearer  
 
 
 
 
 
 
 
 
 
 
Looking at this again - I think the error message is missing one fundamental piece of information that leaves the reader guessing. It says: 
 
 
 
 
 
 
Error while evaluating a Function Call, 'lookup' expects one of:
 
 
 
 
 
 
 
and goes on telling what the function expects and why what was given was rejected for each of the options. While those require some mental parsing to actually be helpful that is for the next level when you are trying to fix the problem. What the error should have indicated was that there was an attempt to call the function with arguments that did not match. A short term fix (ignoring that the rest of the message could be made more readable) is perhaps to start the error with: 
 
 
 
 
 
 
The function 'lookup' was called with arguments it does not accept. It expects one of:
 
 
 
 
 
 
 
Is that more helpful? Does it point the user in the right direction? ping Adam Buxton 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
  

Jira (FACT-1797) Amazon EC2 C5 Instances not detected as is_virtual causing ec2_metadata fact data not to resolve

2017-12-06 Thread Maksym Melnychok (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maksym Melnychok commented on  FACT-1797 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Amazon EC2 C5 Instances not detected as is_virtual causing ec2_metadata fact data not to resolve  
 
 
 
 
 
 
 
 
 
 
is there a corresponding ticket for Linux? because linux c5 instances are also missing ec2_* facts. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-578) Symbolized facts causes "ignore bad definition" error in hierarchy

2017-12-06 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  HI-578 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Symbolized facts causes "ignore bad definition" error in hierarchy  
 
 
 
 
 
 
 
 
 
 
Dan Dunckel What I want to know is how facts ended up being encoded with symbols as keys - they are not supposed to be in that form. I therefore think that the problem is in how tests are set up. That is - something brought in by these: 
 
 
 
 
 
 
require "puppetlabs_spec_helper/module_spec_helper" 
 
 
 
 
require "rspec-puppet-facts" 
 
 
 
 
include RspecPuppetFacts
 
 
 
 
 
 
 
We do not want $facts to be populated with symbol keys. While that may have worked in the past because there was string/symbol monkey patching in place that equated symbols with strings - that monkeypatch is gone in puppet 5 because of all the problems it created. We do not want that back and the correct thing to do here is to ensure that tests feed the right data into the rest of the machinery. 
The proposed solution, to search again with the key turned into a symbol has several other problems: 
 

it makes all searches slower since for every key that is not found in a particular backend, there would be an extra lookup.
 

hiera 3 is deprecated in favor of hiera 5, and the change does not carry forward
 
 
I think the real solution is to fix the testing framework. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
  

Jira (PUP-2968) Make it possible to namespace ruby-defined custom types

2017-12-06 Thread David Schmitt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Schmitt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2968 
 
 
 
  Make it possible to namespace ruby-defined custom types  
 
 
 
 
 
 
 
 
 
 
I've added this to the list of long-term improvements in the Resource API. 
 
 
 
 
 
 
 
 
 

Change By:
 
 David Schmitt 
 
 
 

Team:
 
 Platform Core 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-2968) Make it possible to namespace ruby-defined custom types

2017-12-06 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to David Schmitt 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2968 
 
 
 
  Make it possible to namespace ruby-defined custom types  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Henrik Lindberg David Schmitt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7619) Add a `convert_to` function that works like `new` but with type arg as second arg

2017-12-06 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-7619 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add a `convert_to` function that works like `new` but with type arg as second arg  
 
 
 
 
 
 
 
 
 
 
Merged to master at c6eb142. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7619) Add a `convert_to` function that works like `new` but with type arg as second arg

2017-12-06 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7619 
 
 
 
  Add a `convert_to` function that works like `new` but with type arg as second arg  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8190) Move ExecutionResult and Target type into boltlib

2017-12-06 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-8190 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Move ExecutionResult and Target type into boltlib  
 
 
 
 
 
 
 
 
 
 
I think the non-ruby runtimes should have an API similar to PAL for registration of types. Where it obtains the types to register is someone else's problem. (I assume there will be a separate java impl with the bolt types, and that the application using both pcore-java and supporting bolt will need to also include bolt-java with the types). 
If this should be allowed in module's or not is difficult - other runtimes typically have some kind of plugin mechanism already and puppet's modules may not be the best way of delivering content for those. 
In total there is quite a lot of work to enable "moving faster" - I am not so sure it is worth doing all this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6043) puppet apply -e states "syntax error at end of file" when there is no file

2017-12-06 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6043 
 
 
 
  puppet apply -e states "syntax error at end of file" when there is no file  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6043) puppet apply -e states "syntax error at end of file" when there is no file

2017-12-06 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-6043 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet apply -e states "syntax error at end of file" when there is no file  
 
 
 
 
 
 
 
 
 
 
Merged to master at 0728727. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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