Jira (FACT-1600) Update the last of the options tests for facter with TestRail numbers, risk tags, code style

2017-04-07 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney assigned an issue to Eric Delaney 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1600 
 
 
 
  Update the last of the options tests for facter with TestRail numbers, risk tags, code style  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

Assignee:
 
 Eric Delaney 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1600) Update the last of the options tests for facter with TestRail numbers, risk tags, code style

2017-04-07 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1600 
 
 
 
  Update the last of the options tests for facter with TestRail numbers, risk tags, code style  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Affects Versions:
 

 FACT 3.6.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/04/07 4:32 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Eric Delaney 
 
 
 
 
 
 
 
 
 
 
Test updates for 
 

move "-p" test into the options folder
 

Update the the last of the options tests with TestRail Numbers, risk tags, and code style
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
   

Jira (PDB-3434) fix configure_postgres link

2017-04-07 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3434 
 
 
 
  fix configure_postgres link  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/04/07 1:54 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
Switch from: https://github.com/puppetlabs/puppetdb/blob/master/documentation/configure.html#using-postgresql to: https://github.com/puppetlabs/puppetdb/blob/master/documentation/configure.markdown#using-postgresql 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 

Jira (PUP-7438) Lookup knockout prefix behaviour affected by seemingly unrelated changes in hierarchy

2017-04-07 Thread Jarkko Oranen (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jarkko Oranen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7438 
 
 
 
  Lookup knockout prefix behaviour affected by seemingly unrelated changes in hierarchy  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.10.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 AIO 
 
 
 

Created:
 

 2017/04/07 12:20 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Jarkko Oranen 
 
 
 
 
 
 
 
 
 
 
Hiera 5 lookups seem affected by hierarchy changes in unexpected ways. 
I've tried to formulate a minimal testcase here:  
 https://github.com/oranenj/hiera-testcase 
Commenting out parts of the hierarchy changes the lookup behaviour in ways I can't explain. In particular, adding a path to one hierarchy breaks a knockout that previously worked, which might lead to unpleasant surprises. 
I've put the priority as major, because this prevents me from using knockout prefixes altogether, since I can't trust them to behave predictably. 
In addition, the explain output for knockouts should be much more explicit about what is happening. If you only have knockouts in your YAML file, puppet lookup will claim to find an empty array in some cases 
The expected behaviour here is for knockout 

Jira (PUP-7436) regression: epp parameter with default expression = undef does not take

2017-04-07 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7436 
 
 
 
  regression: epp parameter with default _expression_ = undef does not take  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenn Hussey 
 
 
 

Team:
 
 Puppet Developer Experience 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7436) regression: epp parameter with default expression = undef does not take

2017-04-07 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7436 
 
 
 
  regression: epp parameter with default _expression_ = undef does not take  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenn Hussey 
 
 
 

Labels:
 
 regression 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-04-07 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3432 
 
 
 
  Backport elapsed command processing logging to LTS  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Browning 
 
 
 

Story Points:
 
 1 
 
 
 

Team:
 
 Systems Engineering 
 
 
 

Sprint:
 
 Hopper Server 2017-04-19 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-04-07 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning assigned an issue to Rob Browning 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3432 
 
 
 
  Backport elapsed command processing logging to LTS  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Browning 
 
 
 

Assignee:
 
 Rob Browning 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7402) handle trailing slashes in references between file resources

2017-04-07 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-7402 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: handle trailing slashes in references between file resources  
 
 
 
 
 
 
 
 
 
 
I fixed a similar test in the PR. The reason for the change is that the !defined part will now find the resource where it earlier did not. Therefore the test will never add the second conflicting file resource. I.e the test is based on the assumption that it would not find the resource when the endings were different. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7436) regression: epp parameter with default expression = undef does not take

2017-04-07 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7436 
 
 
 
  regression: epp parameter with default _expression_ = undef does not take  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 PDE 2017-04-19 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7436) regression: epp parameter with default expression = undef does not take

2017-04-07 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7436 
 
 
 
  regression: epp parameter with default _expression_ = undef does not take  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP 4.10.z 
 
 
 

Fix Version/s:
 
 PUP 4.10.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7436) regression: epp parameter with default expression = undef does not take

2017-04-07 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7436 
 
 
 
  regression: epp parameter with default _expression_ = undef does not take  
 
 
 
 
 
 
 
 
 
 
Verified, if the value is changed from undef to a non undef value, that value is assigned to the variable. The name of the variable does not matter. 
The problem seems to be that the assignment of undef in this case is not registered as an assignment to the parameter and it instead continues trying to find the variable in an outer scope (which it does in the example showing the problem). 
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Story Points:
 
 1 
 
 
 

Release Notes Summary:
 
 A default value _expression_ for an EPP parameter of {{undef}} did not take effect and the parameter was instead resolved against an outer scope.This is now fixed. 
 
 
 

Summary:
 
 regression:  lookup of fact values for  epp  parameters  parameter with default _expression_ = undef  does not take 
 
 
 

Release Notes:
 
 Bug Fix 
 
 
 

Fix Version/s:
 
 PUP 4.10.1 
 
 
 

Fix Version/s:
 
 PUP 4.10.z 
 
 
 
 
 
 
 
 
 
 
 
 

  

Jira (PUP-7436) regression: lookup of fact values for epp parameters

2017-04-07 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7436 
 
 
 
  regression: lookup of fact values for epp parameters  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP 4.10.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7402) handle trailing slashes in references between file resources

2017-04-07 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-7402 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: handle trailing slashes in references between file resources  
 
 
 
 
 
 
 
 
 
 
Failed CI in https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent/view/master/view/puppet-agent/job/platform_puppet-agent_intn-van-sys_suite-daily-puppet-master/45/ 
Looks like the test is looking for already declared error message, which I would still expect when running puppet apply. Except that we're using noop, so maybe we don't trigger the message any more. Not sure if the code or test needs updating. 
 
 
 
 
 
 
[root@i62nkbk8ue3rc9q puppet]# cat /tmp/dir-resource.5L4vvL 
 
 
 
 
$dir='/tmp/create-dir.EBKZab' 
 
 
 
 
$same_dir='/tmp/create-dir.EBKZab/' 
 
 
 
 
file {$dir: 
 
 
 
 
  ensure => directory, 
 
 
 
 
} 
 
 
 
 
if !defined(File["${same_dir}"]) { 
 
 
 
 
  file { $same_dir: 
 
 
 
 
ensure => directory, 
 
 
 

Jira (PDB-3432) Backport elapsed command processing logging to LTS

2017-04-07 Thread Susan McNerney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Susan McNerney commented on  PDB-3432 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Backport elapsed command processing logging to LTS  
 
 
 
 
 
 
 
 
 
 
Approved for 2016.4.4/ PDB 4.2.3.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-04-07 Thread Adam Bottchen (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adam Bottchen commented on  PDB-3096 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: log time elapsed for command processing  
 
 
 
 
 
 
 
 
 
 
Created https://tickets.puppetlabs.com/browse/PE-20261 to track the potential backport effort, since this ticket is closed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-04-07 Thread Russell Mull (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull assigned an issue to Russell Mull 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3374 
 
 
 
  Collapse / shrink integration tests  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Mull 
 
 
 

Assignee:
 
 Russell Mull 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-04-07 Thread Russell Mull (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3432 
 
 
 
  Backport elapsed command processing logging to LTS  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Mull 
 
 
 

Fix Version/s:
 
 PDB 4.2.3.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7437) Make `pkgng` default package provider for dragonfly bsd

2017-04-07 Thread Moses Mendoza (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7437 
 
 
 
  Make `pkgng` default package provider for dragonfly bsd  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/04/07 9:19 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Moses Mendoza 
 
 
 
 
 
 
 
 
 
 
Since version 3.4 (2013) Dragonfly BSD has shipped with pkgng as its default packaging system. Puppet currently has it as `pkgin`.  
Update default provider in Puppet to reflect the correct packaging system. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  

Jira (PUP-7108) Create pseudo-localized PO file for CI

2017-04-07 Thread Maggie Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer commented on  PUP-7108 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Create pseudo-localized PO file for CI  
 
 
 
 
 
 
 
 
 
 
Probably not... but I'd like to leave it until we have talked with QA about how they want to handle testing translations. If they want to use e.g. real Japanese on the Japanese boxes we have in CI, this shouldn't be needed. But if they'd rather "stub out" the translations, we might still want this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3433) (maint) Run lein test all in jenkins

2017-04-07 Thread Russell Mull (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3433 
 
 
 
  (maint) Run lein test all in jenkins  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Mull 
 
 
 

Fix Version/s:
 
 PDB 5.0.0 
 
 
 

Fix Version/s:
 
 PDB 4.4.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3395) bypass certname_packages join on aggregate queries against packages

2017-04-07 Thread Russell Mull (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3395 
 
 
 
  bypass certname_packages join on aggregate queries against packages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Mull 
 
 
 

Sprint:
 
 PuppetDB 2017-04-19 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3395) bypass certname_packages join on aggregate queries against packages

2017-04-07 Thread Russell Mull (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3395 
 
 
 
  bypass certname_packages join on aggregate queries against packages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Mull 
 
 
 

Story Points:
 
 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-04-07 Thread Russell Mull (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3429 
 
 
 
  Drop testing on EL 5  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Mull 
 
 
 

Fix Version/s:
 
 PDB 5.0.0 
 
 
 

Fix Version/s:
 
 PDB 4.4.1 
 
 
 

Fix Version/s:
 
 PDB 4.2.3.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-04-07 Thread Russell Mull (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3428 
 
 
 
  Drop testing on the 4.2.x branch  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Mull 
 
 
 

Fix Version/s:
 
 PDB 4.2.z 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7436) regression: lookup of fact values for epp parameters

2017-04-07 Thread Reinhard Vicinus (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Reinhard Vicinus created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7436 
 
 
 
  regression: lookup of fact values for epp parameters  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.10.0, PUP 4.9.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/04/07 8:34 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Reinhard Vicinus 
 
 
 
 
 
 
 
 
 
 
with puppet 4.8.3 and older versions the following code generated an empty notice: 
 
 
 
 
 
 
notice(inline_epp('<%- | Optional[String] $path = undef, | -%><%= $path %>', {}))
 
 
 
 
 
 
 
with 4.10.0 and at least 4.9.4 the value of the fact 'path' is returned. 
 
 
 
 
 
 
 
 
 
 
 
 

Jira (PDB-2614) update module docs to reflect lack of support for HSQL

2017-04-07 Thread Russell Mull (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2614 
 
 
 
  update module docs to reflect lack of support for HSQL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Mull 
 
 
 

Team:
 
 Systems Engineering 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1968) Duplicate resources can make re-usable Forge modules difficult

2017-04-07 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1968 
 
 
 
  Duplicate resources can make re-usable Forge modules difficult  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP 4.y 
 
 
 

Fix Version/s:
 
 PUP 5.y 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7336) Interpolation behavior in hiera.yaml changed between Puppet version 4.9.3 and 4.9.4

2017-04-07 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7336 
 
 
 
  Interpolation behavior in hiera.yaml changed between Puppet version 4.9.3 and 4.9.4  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Release Notes Summary:
 
 This  is  was  a regression  in 4.9.4  from 4.9.3 , but it affects a feature  that  hasn't previously shipped with PE.In  in  some very rare cases ,  could cause  a v5 hiera.yaml file  can  to  ignore certain hierarchy levels. This only  happens  happened  for hierarchy levels that  interpolate  interpolated  a top-scope variable whose value was set after the _first_ Hiera lookup. Even then, it only  occurs  occurred  if the variable  is  was  an array or hash, the hierarchy level accesses one of its members with key.subkey notation, _and_ the variable  is  was  referenced with the top-scope namespace (`::attributes.role`). If this affects you, you can remove the top-scope namespace (`attributes.role`) to work around it until this bug This problem  is  now  fixed. However, we strongly recommend against making your hierarchy self-configuring like this. You should only interpolate the `$facts`, `$trusted`, and `$server_facts` variables in your hierarchy. (Dirty details: In the lookup that initially sets the offending variable, that variable doesn't exist yet. Hiera remembers that it doesn't exist, so in subsequent lookups it won't use the new value. This is part of an optimization for top-scope variables that don't change, which is why removing the top namespace works around it.) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-7336) Interpolation behavior in hiera.yaml changed between Puppet version 4.9.3 and 4.9.4

2017-04-07 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-7336 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Interpolation behavior in hiera.yaml changed between Puppet version 4.9.3 and 4.9.4  
 
 
 
 
 
 
 
 
 
 
The "known issue note" was for Puppet 4.9.4. It is fixed in 4.10.0. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7336) Interpolation behavior in hiera.yaml changed between Puppet version 4.9.3 and 4.9.4

2017-04-07 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7336 
 
 
 
  Interpolation behavior in hiera.yaml changed between Puppet version 4.9.3 and 4.9.4  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Release Notes:
 
 Known Issue Bug Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-04-07 Thread Matthias Baur (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthias Baur created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7435 
 
 
 
  Add support for snap packages  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/04/07 1:49 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Matthias Baur 
 
 
 
 
 
 
 
 
 
 
Could we get support for snap package? https://snapcraft.io/ 
This should probably implemented as package provider. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 

Jira (PUP-7108) Create pseudo-localized PO file for CI

2017-04-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols commented on  PUP-7108 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Create pseudo-localized PO file for CI  
 
 
 
 
 
 
 
 
 
 
Maggie Dreyer, given the current state of things, is this still needed? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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