Jira (FACT-1007) facter should return Number instead of String for lsbmajdistrelease (among others)

2015-05-18 Thread c sights (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 c sights created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1007 
 
 
 
  facter should return Number instead of String for lsbmajdistrelease (among others)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 FACT 2.4.3 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/05/18 7:57 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 c sights 
 
 
 
 
 
 
 
 
 
 
Debian with puppet 3.7.5 
Facter (or puppet) returns lsbmajdistrelease as a String instead of a Number. This causes puppet to either break (=, , etc) or silently return unexpected true values ( 7==7, false). 
Facter should return values which are numbers as Numbers. 
Thanks! Chad. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 
   

Jira (FACT-628) facter returns incorrect value for `facter virtual` for Solaris Ldoms

2015-05-18 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley assigned an issue to Branan Riley 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-628 
 
 
 
  facter returns incorrect value for `facter virtual` for Solaris Ldoms  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Assignee:
 
 BrananRiley 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4363) Support splay in apply as well

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall assigned an issue to Kurt Wall 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4363 
 
 
 
  Support splay in apply as well  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

Assignee:
 
 QA KurtWall 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4363) Support splay in apply as well

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4363 
 
 
 
  Support splay in apply as well  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

Assignee:
 
 KurtWall 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-2080) Support functions written in pp

2015-05-18 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-2080 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Support functions written in pp  
 
 
 
 
 
 
 
 
 
 
Example 1: This https://github.com/puppetlabs/puppetlabs-apache/blob/master/lib/puppet/parser/functions/validate_apache_log_level.rb validation function in apache, can be implemented like this with a puppet function: 
 
 
 
 
 
 
function apache::validate_log_level($log_level) { 
 
 
 
 
  unless log_level =~ /(emerg|alert|crit|error|warn|notice|info|debug|trace[1-8])/ { 
 
 
 
 
fail(Log level '${log_level}' is not one of the supported Apache HTTP Server log levels.) 
 
 
 
 
  } 
 
 
 
 
}
 
 
 
 
 
 
 
This function: https://github.com/puppetlabs/puppetlabs-apache/blob/master/lib/puppet/parser/functions/bool2httpd.rb Can be written like this in Puppet. 
 
 
 
 
 
 
function apache::bool2http($arg) { 
 
 
 
 
  case $arg { 
 
 
 
 
false, undef, /(?i:false)/ : { 'Off' } 
 
 
  

Jira (PUP-4193) Add ability to use a lambda as case option for advanced matching

2015-05-18 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4193 
 
 
 
  Add ability to use a lambda as case option for advanced matching  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Fix Version/s:
 
 PUP4.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (FACT-892) load_average resolver is not really posix

2015-05-18 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene assigned an issue to Peter Huene 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-892 
 
 
 
  load_average resolver is not really posix  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 

Assignee:
 
 PeterHuene 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-585) Run spec tests for opened PR on Windows

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-585 
 
 
 
  Run spec tests for opened PR on Windows   
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Risk Assessment Reason:
 
 N/Afortestingtickets 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4371) Smoke test mcollective on Puppet 4.0 AIO

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4371 
 
 
 
  Smoke test mcollective on Puppet 4.0 AIO  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Risk Assessment Reason:
 
 N/Afortestingtickets 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-585) Run spec tests for opened PR on Windows

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-585 
 
 
 
  Run spec tests for opened PR on Windows   
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4371) Smoke test mcollective on Puppet 4.0 AIO

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4371 
 
 
 
  Smoke test mcollective on Puppet 4.0 AIO  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4552) Resource parameter validation uses TypeCalculator.infer instead of infer_set

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4552 
 
 
 
  Resource parameter validation uses TypeCalculator.infer instead of infer_set  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

Assignee:
 
 KurtWall 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-1487) Add producer_timestamp to store-report

2015-05-18 Thread Russell Mull (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull assigned an issue to Russell Mull 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1487 
 
 
 
  Add producer_timestamp to store-report  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Mull 
 
 
 

Assignee:
 
 RussellMull 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4193) Add ability to use a lambda as case option for advanced matching

2015-05-18 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-4193 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Add ability to use a lambda as case option for advanced matching  
 
 
 
 
 
 
 
 
 
 
The PR to revert is merged. I set the fix version to 4.x (and we can revisit if needed as the Puppet RFC process works its way). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-2748) require = Exec does not work

2015-05-18 Thread c sights (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 c sights updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-2748 
 
 
 
  require = Exec does not work  
 
 
 
 
 
 
 
 
 

Change By:
 
 c sights 
 
 
 

Fix Version/s:
 
 PUP3.5.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4363) Support splay in apply as well

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall commented on  PUP-4363 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Support splay in apply as well  
 
 
 
 
 
 
 
 
 
 
Neither puppet help agent nor puppet help apply emit anything about the --splay option. Should it? 
 
 
 
 
 
 
$ puppet help apply 
 
 
 
 
puppet-apply(8) -- Apply Puppet manifests locally 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
SYNOPSIS 
 
 
 
 
 
 
 
 
 
Applies a standalone Puppet manifest to the local system. 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
USAGE 
 
 
 
 
- 
 
  

Jira (PUP-4363) Support splay in apply as well

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall commented on  PUP-4363 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Support splay in apply as well  
 
 
 
 
 
 
 
 
 
 
Validate at master at SHA=NN. The --splay option also works for the apply face: 
 
 
 
 
 
 
$ be puppet apply -e 'notice(world domination fast)' --splay --splaylimit 15s --verbose 
 
 
 
 
Info: Sleeping for 11 seconds (splay is enabled) 
 
 
 
 
Notice: Scope(Class[main]): world domination fast 
 
 
 
 
Notice: Compiled catalog for breve.local in environment production in 0.33 seconds 
 
 
 
 
Info: Applying configuration version '1431959438' 
 
 
 
 
Notice: Applied catalog in 0.03 seconds
 
 
 
 
 
 
 
But not if --test is also specified: 
 
 
 
 
 
 
$ be puppet apply -e 'notice(world domination fast)' --splay --splaylimit 15s --verbose --test 
 
 
 
 
Notice: Scope(Class[main]): world domination fast 
 
 
 
  

Jira (PUP-4193) Add ability to use a lambda as case option for advanced matching

2015-05-18 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4193 
 
 
 
  Add ability to use a lambda as case option for advanced matching  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Fix Version/s:
 
 PUP4.1.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-1530) Upgrade to latest clojure.java.jdbc

2015-05-18 Thread Kenneth Barber (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1530 
 
 
 
  Upgrade to latest clojure.java.jdbc  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/05/18 6:07 AM 
 
 
 

Fix Versions:
 

 PDB 3.0.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Kenneth Barber 
 
 
 
 
 
 
 
 
 
 
We're running a very old version of clojure.java.jdbc, and we should upgrade to the latest version. 
There are two major strategies I see us following here: 
 

We could cut to the latest revision, but use the deprecated namespace - that gets us the latest jar, but means we don't get the new API.
 

We could cut to the latest revision, and change our code to use the new API. This involves thread an equivalent to the db var instead of using a global-like binded var like it does today.
 
 
 
 
 
 
 
 
 
 
 
 
 
 


Jira (FACT-96) Deprecate 'facter --puppet'

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-96 
 
 
 
  Deprecate 'facter --puppet'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

Assignee:
 
 KurtWall 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4193) Add ability to use a lambda as case option for advanced matching

2015-05-18 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4193 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Add ability to use a lambda as case option for advanced matching  
 
 
 
 
 
 
 
 
 
 
Revert PR is up for review and merge. (Note that after a merge from stable to master, the eparser must be generated because of the grammar change). When merge has been done, change the Fix version to 4.x. 
A request for a PRFC (a.k.a ARM) has been made. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (FACT-1005) Facter master spec test failed on Linux

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1005 
 
 
 
  Facter master spec test failed on Linux  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (FACT-1004) Facter master build failed on windows

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1004 
 
 
 
  Facter master build failed on windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-1344) Build and release PE packages via the puppetdb-sync (pe-puppetdb-extensions repo)

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1344 
 
 
 
  Build and release PE packages via the puppetdb-sync (pe-puppetdb-extensions repo)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Risk Assessment Reason:
 
 N/Aforbuild/releasetickets 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-1344) Build and release PE packages via the puppetdb-sync (pe-puppetdb-extensions repo)

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1344 
 
 
 
  Build and release PE packages via the puppetdb-sync (pe-puppetdb-extensions repo)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-1479) Mark aggregate-event-counts event-counts API docs as experimental for the future

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1479 
 
 
 
  Mark aggregate-event-counts  event-counts API docs as experimental for the future  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Risk Assessment Reason:
 
 N/Afordocstickets 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-1479) Mark aggregate-event-counts event-counts API docs as experimental for the future

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1479 
 
 
 
  Mark aggregate-event-counts  event-counts API docs as experimental for the future  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4552) Resource parameter validation uses TypeCalculator.infer instead of infer_set

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall assigned an issue to Kurt Wall 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4552 
 
 
 
  Resource parameter validation uses TypeCalculator.infer instead of infer_set  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

Assignee:
 
 QA KurtWall 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-1492) PuppetDB 2.3.4 Release

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1492 
 
 
 
  PuppetDB 2.3.4 Release  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Risk Assessment Reason:
 
 N/Aforreleasetickets 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-1518) PR (1390): (maint) Do not build stable or testing - melissa

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1518 
 
 
 
  PR (1390): (maint) Do not build stable or testing - melissa  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Risk Assessment Reason:
 
 N/Afortestingtickets 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-1492) PuppetDB 2.3.4 Release

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1492 
 
 
 
  PuppetDB 2.3.4 Release  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-1518) PR (1390): (maint) Do not build stable or testing - melissa

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1518 
 
 
 
  PR (1390): (maint) Do not build stable or testing - melissa  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-1531) Upgrade to latest metrics-clojure (= v2.5.1)

2015-05-18 Thread Kenneth Barber (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1531 
 
 
 
  Upgrade to latest metrics-clojure (= v2.5.1)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/05/18 6:10 AM 
 
 
 

Fix Versions:
 

 PDB 3.0.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Kenneth Barber 
 
 
 
 
 
 
 
 
 
 
We should upgrade to the latest revision of metrics-clojure, right now we are running a very old alpha 0.x release. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was 

Jira (FACT-96) Deprecate 'facter --puppet'

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall assigned an issue to Kurt Wall 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-96 
 
 
 
  Deprecate 'facter --puppet'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

Assignee:
 
 QA KurtWall 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4621) Add a list command in Puppet filebucket

2015-05-18 Thread Romain Fihue (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Romain Fihue created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4621 
 
 
 
  Add a list command in Puppet filebucket  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Romain Fihue 
 
 
 

Created:
 

 2015/05/18 12:37 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Romain Fihue 
 
 
 
 
 
 
 
 
 
 
Being able to list all files present in a filebucket is pretty convienient. You would be able to do the following. 
 
 
 
 
 
 
List Example 
 
 
 
 
 
 
$ puppet filebucket -l  list 
 
 
 
 
d43a6ecaa892a1962398ac9170ea9bf2 2015-05-11 09:27:56 /tmp/TestFile 
 
 
 
 
7ae322f5791217e031dc60188f4521ef 2015-05-11 09:52:15 /tmp/TestFile 
 
 
  

Jira (PUP-4621) Add a list command in Puppet filebucket

2015-05-18 Thread Romain Fihue (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Romain Fihue updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4621 
 
 
 
  Add a list command in Puppet filebucket  
 
 
 
 
 
 
 
 
 

Change By:
 
 Romain Fihue 
 
 
 
 
 
 
 
 
 
 Beingabletolistallfilespresentinafilebucketisprettyconvienient.Youwouldbeabletodothefollowing.{code:title=ListExample|borderStyle=solid}$puppetfilebucket-llistd43a6ecaa892a1962398ac9170ea9bf22015-05-1109:27:56/tmp/TestFile7ae322f5791217e031dc60188f4521ef2015-05-1109:52:15/tmp/TestFile$puppetfilebucket-l-f2015-01-01-t2015-01-11listEmptyOutput$puppetfilebucket-l-f2015-05-10listd43a6ecaa892a1962398ac9170ea9bf22015-05-1109:27:56/tmp/TestFile7ae322f5791217e031dc60188f4521ef2015-05-1109:52:15/tmp/TestFile$puppetfilebucket-l-f2015-05-1109:30:00list7ae322f5791217e031dc60188f4521ef2015-05-1109:52:15/tmp/TestFile$puppetfilebucket-l-t2015-05-1109:30:00listd43a6ecaa892a1962398ac9170ea9bf22015-05-1109:27:56/tmp/TestFile{code}Codeandtestsarereadytoreceive feeback feedback . 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-1529) PuppetDB accepts newlines in resource titles but not relationship titles

2015-05-18 Thread Kenneth Barber (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1529 
 
 
 
  PuppetDB accepts newlines in resource titles but not relationship titles  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Sprint:
 
 PuppetDB2015-06-03 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4613) Unclear language in the spec around types being assignable from types

2015-05-18 Thread Nicholas Fagerlund (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicholas Fagerlund commented on  PUP-4613 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Unclear language in the spec around types being assignable from types  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg Okay, so it sounds to me like Type T is assignable from type T2 means the exact same thing as Type T is a superset of type T2. Is that accurate, or am I missing a subtlety?  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-3512) Require metric id in Puppet Profiler API

2015-05-18 Thread Nicholas Fagerlund (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicholas Fagerlund commented on  PUP-3512 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Require metric id in Puppet Profiler API  
 
 
 
 
 
 
 
 
 
 
Christopher Price Thank you! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4373) Windows ADSI User groups property should behave similarly to Groups members property

2015-05-18 Thread Rob Reynolds (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Reynolds assigned an issue to Ryan Gard 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4373 
 
 
 
  Windows ADSI User groups property should behave similarly to Groups members property  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Reynolds 
 
 
 

Assignee:
 
 QA RyanGard 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4373) Windows ADSI User groups property should behave similarly to Groups members property

2015-05-18 Thread Rob Reynolds (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Reynolds assigned an issue to Kurt Wall 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4373 
 
 
 
  Windows ADSI User groups property should behave similarly to Groups members property  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Reynolds 
 
 
 

Assignee:
 
 RyanGard KurtWall 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4436) With a gem install of puppet, when run as root, 'puppet {agent|apply}' fail

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall assigned an issue to Kurt Wall 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4436 
 
 
 
  With a gem install of puppet, when run as root, 'puppet {agent|apply}' fail  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Assignee:
 
 QA KurtWall 
 
 
 

Status:
 
 ReadyforTest Resolved 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4436) With a gem install of puppet, when run as root, 'puppet {agent|apply}' fail

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall commented on  PUP-4436 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: With a gem install of puppet, when run as root, 'puppet {agent|apply}' fail  
 
 
 
 
 
 
 
 
 
 
Let's try this again. Built my gem, installed, run the previous command, got love: 
 
 
 
 
 
 
# bundle exec rake package:implode package:bootstrap package:gem 
 
 
 
 
# bundle exec rake package:gem 
 
 
 
 
# ls -l pkg 
 
 
 
 
total 7392 
 
 
 
 
-rw-r--r--. 1 root root 2520576 May 18 09:45 puppet-4.0.0.437.gem 
 
 
 
 
-rw-r--r--. 1 root root 2520576 May 18 09:45 puppet-4.0.0.437-x64-mingw32.gem 
 
 
 
 
-rw-r--r--. 1 root root 2520576 May 18 09:45 puppet-4.0.0.437-x86-mingw32.gem 
 
 
 
 
# gem install pkg/puppet-4.0.0.437.gem 
 
 
 
 
Successfully installed puppet-4.0.0.437 
 
 
 
 
Parsing documentation for puppet-4.0.0.437 
 
 

Jira (PUP-4623) Port package tests to be able to test against MSIs

2015-05-18 Thread Justin Stoller (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Justin Stoller created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4623 
 
 
 
  Port package tests to be able to test against MSIs  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/05/18 9:19 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Justin Stoller 
 
 
 
 
 
 
 
 
 
 
Currently the 3.x pipeline is testing Windows installations from source. For many reasons we would like to test from built MSIs hosted at builds.delivery.puppetlabs.net. It seems as if the simplest approach would be to amend the pre-suite used by the ci:test:packages rake task to install MSIs if the task was given a config file with windows hosts. 
This work would be similar to the AIO installation steps. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA 

Jira (FACT-1006) Add Cisco NXOS support

2015-05-18 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  FACT-1006 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Add Cisco NXOS support  
 
 
 
 
 
 
 
 
 
 
Just chatted with Scott Garman and confirmed that this is not needed in ruby facter (facter 2.x) but only in native facter (facter 3.x) so the PR linked can be used as a reference implementation. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4436) With a gem install of puppet, when run as root, 'puppet {agent|apply}' fail

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4436 
 
 
 
  With a gem install of puppet, when run as root, 'puppet {agent|apply}' fail  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

Assignee:
 
 KurtWall 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (FACT-1006) Add Cisco NXOS support

2015-05-18 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1006 
 
 
 
  Add Cisco NXOS support  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Fix Version/s:
 
 FACT3.1.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts

2015-05-18 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney commented on  PUP-2630 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Server-set global variables like $::environment get overwritten by client facts  
 
 
 
 
 
 
 
 
 
 
As pointed out by Nicholas Fagerlund, only populating the $server_facts variable on an agent run poses an issue. If module authors want to use $server_facts[environment] in their code, then they will not longer be able to run with `puppet apply`. 
In order to fix this, I've opened a PR that will add environment to the $server_facts hash during a puppet apply if trusted_server_facts is true: https://github.com/puppetlabs/puppet/pull/3942 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts

2015-05-18 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson commented on  PUP-2630 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Server-set global variables like $::environment get overwritten by client facts  
 
 
 
 
 
 
 
 
 
 
for posterity... this is covered well by the spec test addition. no need to update the acceptance test. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4626) Puppet should exit when comparing Number == String

2015-05-18 Thread c sights (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 c sights created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4626 
 
 
 
  Puppet should exit when comparing Number == String  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/05/18 11:45 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 c sights 
 
 
 
 
 
 
 
 
 
 
Recently (3.7.4 or 3.7.5) puppet stopped converting strings to numbers when comparing them with ,,=,=, and == (possibly others). 
For all but == Puppet gives a warning that a String is not comparable to a Number. 
Puppet should do this for == also because otherwise comparisons such as: lsbmajdistrelease = 7 if ($::lsbmajdistrelease == 7) {} silently change their truth value from True to False. 
This can cause all sorts fo breakage! 
It would be better to abort compilation with a message and have the user explicitly convert from String to Number (or visa versa). 
Thanks! Chad. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
   

Jira (PUP-4624) Misleading output from puppet cert sign

2015-05-18 Thread Lindsey Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lindsey Smith updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4624 
 
 
 
  Misleading output from puppet cert sign  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lindsey Smith 
 
 
 

Affects Version/s:
 
 PUP3.7.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4624) Misleading output from puppet cert sign

2015-05-18 Thread Lindsey Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lindsey Smith created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4624 
 
 
 
  Misleading output from puppet cert sign  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/05/18 11:06 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Lindsey Smith 
 
 
 
 
 
 
 
 
 
 
If I run puppet cert sign myagent and there's no outstanding CSR for myagent, then I get Error: Could not find certificate request for myagent. If I naively run puppet cert sign * thinking that it will sign all of the outstanding CSRs, then I get Error: Could not find certificate request for install_log.lastrun.localhost.log.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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

Jira (PUP-4625) Improve puppet node purge messaging

2015-05-18 Thread Lindsey Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lindsey Smith created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4625 
 
 
 
  Improve puppet node purge messaging  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Story 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/05/18 11:18 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Lindsey Smith 
 
 
 
 
 
 
 
 
 
 
Currently (PE = SG), puppet server has to be restarted before a purged node is truly gone but the command output doesn't tell you this.  
Recommend changing the puppet node purge output from: 

Node myagent was purged. If you want to add this node back to your Puppet infrastructure, remove old certificates from the agent node first.
 
To: 

Node myagent was purged. You may need to restart Puppet server to complete this operation. If you want to add this node back to your Puppet infrastructure, remove old certificates from the agent node first.
 
cc: Larissa Lane 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 

Jira (PUP-1295) Yum provider purge target runs irrespective of package installation status

2015-05-18 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  PUP-1295 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Yum provider purge target runs irrespective of package installation status  
 
 
 
 
 
 
 
 
 
 
Review plans: 
 

gem supports uninstall but not purge
 

yum supports purge but not uninstall
 

apt/dpkg supports both purge and uninstall
 

apple supports neither
 
 
Review how the behavior changes under each provider. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4627) Storeconfigs unusable with Puppetserver

2015-05-18 Thread Christopher Barbour (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Barbour created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4627 
 
 
 
  Storeconfigs unusable with Puppetserver  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.8.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/05/18 11:58 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Christopher Barbour 
 
 
 
 
 
 
 
 
 
 
The MySQL ruby gem will not compile for Jruby. As a result, current users of Active Record storeconfigs cannot upgrade to Puppetserver. 
The fix for this appears to be relatively straightforward; add jdbcmysql to the list of mysql connectors in the Puppet Rails library, and update the spec tests. The Active Record ORM should handle most of the complexity of using JDBC drivers, and the change poses no risk to users of the mysql and mysql2 connectors. 
https://github.com/puppetlabs/puppet/blob/3.x/lib/puppet/rails.rb https://github.com/puppetlabs/puppet/blob/3.x/lib/puppet/rails/database/schema.rb 
While storeconfigs are deprecated, this issue does block current users from moving away from Apache/Passenger/Rails. The requested change is simple, and extremely low risk. 
 
 
 
 
 
 
 
 
 
 
 
 

  

Jira (PUP-4627) Storeconfigs unusable with Puppetserver

2015-05-18 Thread Christopher Barbour (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Barbour commented on  PUP-4627 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Storeconfigs unusable with Puppetserver  
 
 
 
 
 
 
 
 
 
 
We'd be more than happy to supply a PR and update spec tests for the change, but before investing the effort I'd like to see if Puppet Labs is receptive to accepting a PR for Active Record against the 3.x or 3.8 branch. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-1521) PR (1395): (maint) Lint with `eastwood` and improve syntax in services.clj - ajroetker

2015-05-18 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1521 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (1395): (maint) Lint with `eastwood` and improve syntax in services.clj - ajroetker  
 
 
 
 
 
 
 
 
 
 
pljenkinsro commented: 
Test FAILed. Refer to this link for build results (access rights to CI server needed):  https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1242/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4483) Add NotUndef type to the set of Puppet types

2015-05-18 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-4483 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Add NotUndef type to the set of Puppet types  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg who should review this? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-1532) Create module stable branch for 4.x and master branch for 5.x

2015-05-18 Thread AJ Roetker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 AJ Roetker created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1532 
 
 
 
  Create module stable branch for 4.x and master branch for 5.x  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 PDB module-5.0.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Module 
 
 
 

Created:
 

 2015/05/18 2:04 PM 
 
 
 

Fix Versions:
 

 PDB module-5.0.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 AJ Roetker 
 
 
 
 
 
 
 
 
 
 
We need to make a stable branch for module 4.x fixes and put breaking changes to the module in the master branch which will target 5.x. An announcement should be sent out that the modules master branch will target the master PDB branch. 
 
 
 
 
 
 
 
 
 
 
 
 
 

Jira (PUP-4568) Puppet agent does not resend certificate request to master

2015-05-18 Thread Jeremy Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeremy Barlow commented on  PUP-4568 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Puppet agent does not resend certificate request to master  
 
 
 
 
 
 
 
 
 
 
Kylo Ginsberg I talked with Christopher Price about this one. 
I think this work would be a function of the agent and not the CA right? If the agent were to try to get the certificate request back from the master but the master didn't have it anymore, the agent could presumably PUT a new one up to the master. Although from reading the Redmine ticket, I'm not sure if part of the expectation here is that if the CA sees a certificate request for a second or additional time that had been previously rejected that there should be some way on the CA to reject a duplicate submission? 
Presuming the latter isn't part of what's being requested and there is just agent work here, I'm thinking the CA epic Christopher Price mentioned probably may not be a good fit for this since that's largely about server-side work (new persistence store) and associated changes to the CLI tools that would be needed to support that work. Is this something which would ultimately be owned by the Client team and not the Puppet Server team? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-2894) Assign multiple variables from an array

2015-05-18 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-2894 
 
 
 
  Assign multiple variables from an array  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Release Notes:
 
 NewFeature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-3429) Weekly tasks always notify 'trigger changed'

2015-05-18 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3429 
 
 
 
  Weekly tasks always notify 'trigger changed'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Release Notes:
 
 BugFix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-3388) Issue Creating Multiple Mirrors in Zpool Resource

2015-05-18 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3388 
 
 
 
  Issue Creating Multiple Mirrors in Zpool Resource  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Release Notes:
 
 BugFix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-3908) Tidy type is too verbose when working of directories containing lot of files

2015-05-18 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3908 
 
 
 
  Tidy type is too verbose when working of directories containing lot of files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Release Notes:
 
 BugFix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-3814) Duplicated error output

2015-05-18 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3814 
 
 
 
  Duplicated error output  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Release Notes:
 
 BugFix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4483) Add NotUndef type to the set of Puppet types

2015-05-18 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-4483 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Add NotUndef type to the set of Puppet types  
 
 
 
 
 
 
 
 
 
 
Assigning to Nicholas Fagerlund. Please resolve this ticket if the conversation above is sorted out. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4483) Add NotUndef type to the set of Puppet types

2015-05-18 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg assigned an issue to Nicholas Fagerlund 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4483 
 
 
 
  Add NotUndef type to the set of Puppet types  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Assignee:
 
 NicholasFagerlund 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts

2015-05-18 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-2630 
 
 
 
  Server-set global variables like $::environment get overwritten by client facts  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 REPORTEDPROBLEM---Asperthedocs(http://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#variables-set-by-the-puppet-master)thepuppetmastersetstheglobal$::environmentvariabletocontainthenameofthenode'senvironment.However,ifanodeprovidesafactwiththename'environment'thatfact'svalueoverridestheserver-setenvironment.Thesamehappenswithotherserver-setglobalvariables,like$::servernameand$::serverip.Asaresult,modulescan'treliablyusethesevariablesforwhatevertheirintendedpurposeis.Ifthisistheintendedbehavior,thenthedocsshouldclarifythisanddiscourageuseoftheserver-setvariables,becauseamisbehavingnodecanoverridethem.SOLUTION---AfterdiscussionwithEricSoerenson,wedecidedthatitwasbesttomakethisanopt-inandthatwearenotaddingafunction-thisforthesakeofconsistencybetween$facts,$trusted_facts,and$server_facts.Thismeans:Atthesameplacewherewecurrentlyset$trusted_factsweshouldalsoset$server_factsifusershaveoptedinThevaluessetin$server_factsarethe@server_factssetinthenodebythecompilerindirection+thecurrentenvironmentnameTheuseroptsinbyusingthesetting:trusted_server_factsThesettingisfalsebydefaultWeissueawarningifanynodeparameterisoverwrittenWeneedatickettoaddadeprecationfortheopt-inbeingsettofalseWeneedaticketfor5.0.0toremovetheoptinandmake$server_factsdefault,andtostopmergingtheserver_factsintothenode'sparameters Whenusingpuppetapplyand{{trusted_server_facts}}istrue,the$server_factswillbeahashwithonlythekey{{environment}}set.Thevalueforthiskeyistheenvironmentthatwasconfiguredlocallyontheagent,orgivenonthecommandline(i.e.inthiscasethereisnocalltothemastertocomputewhatthemasterthinkstheenvironmentshouldbeforthenode). h3.anexample$server_factshash{serverversion=4.0.0,servername=v85ix8blah.delivery.puppetlabs.net,serverip=10.32.115.182,environment=production}QA---risk:highprobability:mediumseverity:high(hardtodebug,somewhatofasecurityissue,canspoofenvironment)testlayer:acceptance 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

Jira (PUP-3618) Include pkgng provider for FreeBSD

2015-05-18 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3618 
 
 
 
  Include pkgng provider for FreeBSD  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Release Notes:
 
 NewFeature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4373) Windows ADSI User groups property should behave similarly to Groups members property

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall commented on  PUP-4373 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Windows ADSI User groups property should behave similarly to Groups members property  
 
 
 
 
 
 
 
 
 
 
Validated in master against puppet-3.8.0-66.msi. Before the fix (puppet-3.8.0-43.msi), the following manifest causes an error. After the fix, it doesn't. 
 
 
 
 
 
 
C:\type x.pp 
 
 
 
 
user { 'timmy': 
 
 
 
 
  ensure = present, 
 
 
 
 
  groups = ['BUILTIN\Administrators', 'users'], 
 
 
 
 
} 
 
 
 
 
 
 
 
 
 
C:\puppet apply x.pp --verbose 
 
 
 
 
Notice: Compiled catalog for dd4lxjvwfzaiy1z.delivery.puppetlabs.net in environment production in 0.20 seconds 
 
 
 
 
Info: Applying configuration version '1431980977' 
 
 
 
 
Error: ADSI connection error: failed to parse display name of moniker `WinNT://./BUILTIN\Administrators,group' 
 
 

Jira (PUP-2455) Puppet running as Solaris SMF service needs to run child processes in separate contract

2015-05-18 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-2455 
 
 
 
  Puppet running as Solaris SMF service needs to run child processes in separate contract  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Release Notes:
 
 BugFix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4193) Add ability to use a lambda as case option for advanced matching

2015-05-18 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-4193 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Add ability to use a lambda as case option for advanced matching  
 
 
 
 
 
 
 
 
 
 
Also, the PR is merged up to master. I moved this to Ready for Integration. Once it's passed CI, we should probably move it to Needs Information and pull it out of the sprint until it works through the RFC process. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-1521) PR (1395): (maint) Lint with `eastwood` and improve syntax in services.clj - ajroetker

2015-05-18 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1521 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (1395): (maint) Lint with `eastwood` and improve syntax in services.clj - ajroetker  
 
 
 
 
 
 
 
 
 
 
ajroetker commented: 
@senior transients above, fixed for your comments and removed most of the cond- 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4373) Windows ADSI User groups property should behave similarly to Groups members property

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall commented on  PUP-4373 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Windows ADSI User groups property should behave similarly to Groups members property  
 
 
 
 
 
 
 
 
 
 
It is also possible to use and emtpy group list: 
 
 
 
 
 
 
# x.pp 
 
 
 
 
C:\type x.pp 
 
 
 
 
user { johnny: 
 
 
 
 
  ensure = present, 
 
 
 
 
  groups = [], 
 
 
 
 
} 
 
 
 
 
 
 
 
 
 
C:\puppet apply x.pp --verbose 
 
 
 
 
Notice: Compiled catalog for dd4lxjvwfzaiy1z.delivery.puppetlabs.net in environm 
 
 
 
 
ent production in 0.80 seconds 
 
 
 
 
Info: Applying configuration version '1431983948' 

Jira (PUP-2080) Support functions written in pp

2015-05-18 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-2080 
 
 
 
  Support functions written in pp  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Release Notes:
 
 NewFeature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4604) Port fix for pip provider on more recent RedHat operating systems.

2015-05-18 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4604 
 
 
 
  Port fix for pip provider on more recent RedHat operating systems.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 
 
 
 
 
 
 
 package{'south':ensure='installed',provider='pip',require=Package[python-pip],}RESPONSE:Error:Couldnotset'present'onensure:Couldnotlocate Portcommit6ee0339675e7460073483ebc74d4136b27687ae9to the pipcommand 3 . at13:/etc/puppet/modules/django/manifests/packages xbranch . pp  Wrappedexception:  Couldnotlocatethe Thisfixescalling' pip command.Error:/Stage[main]/Django::Packages/Package[south]/ensure:changefromabsenttopresentfailed:Couldnotset ' present' on ensure:CouldnoMYTEMPFIXes:1)sed-is/pip-python/pip/g/usr/share/ruby/vendor_ruby/puppet/provider/package/pip.rb2)orputsomethinglikethatinthepip.rbdefself.cmdcaseFacter.value(:osfamily)when RedHat ifFacter familyOSes . value(:operatingsystemrelease)=7{pip}else{pip-python}elsepipendend 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-2628) Ability to add a member to a group, instead of specifying the complete list

2015-05-18 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-2628 
 
 
 
  Ability to add a member to a group, instead of specifying the complete list  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Release Notes:
 
 NewFeature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts

2015-05-18 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-2630 
 
 
 
  Server-set global variables like $::environment get overwritten by client facts  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Release Notes:
 
 BugFix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4604) Port fix for pip provider on more recent RedHat operating systems.

2015-05-18 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene commented on  PUP-4604 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Port fix for pip provider on more recent RedHat operating systems.  
 
 
 
 
 
 
 
 
 
 
A new PR has been up to cherry pick the original commit: https://github.com/puppetlabs/puppet/pull/3948. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4373) Windows ADSI User groups property should behave similarly to Groups members property

2015-05-18 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4373 
 
 
 
  Windows ADSI User groups property should behave similarly to Groups members property  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

Assignee:
 
 KurtWall 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts

2015-05-18 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-2630 
 
 
 
  Server-set global variables like $::environment get overwritten by client facts  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 REPORTEDPROBLEM---Asperthedocs(http://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#variables-set-by-the-puppet-master)thepuppetmastersetstheglobal$::environmentvariabletocontainthenameofthenode'senvironment.However,ifanodeprovidesafactwiththename'environment'thatfact'svalueoverridestheserver-setenvironment.Thesamehappenswithotherserver-setglobalvariables,like$::servernameand$::serverip.Asaresult,modulescan'treliablyusethesevariablesforwhatevertheirintendedpurposeis.Ifthisistheintendedbehavior,thenthedocsshouldclarifythisanddiscourageuseoftheserver-setvariables,becauseamisbehavingnodecanoverridethem.SOLUTION---AfterdiscussionwithEricSoerenson,wedecidedthatitwasbesttomakethisanopt-inandthatwearenotaddingafunction-thisforthesakeofconsistencybetween$facts,$trusted_facts,and$server_facts.Thismeans:Atthesameplacewherewecurrentlyset$trusted_factsweshouldalsoset$server_factsifusershaveoptedinThevaluessetin$server_factsarethe@server_factssetinthenodebythecompilerindirection+thecurrentenvironmentnameTheuseroptsinbyusingthesetting:trusted_server_factsThesettingisfalsebydefaultWeissueawarningifanynodeparameterisoverwrittenWeneedatickettoaddadeprecationfortheopt-inbeingsettofalseWeneedaticketfor5.0.0toremovetheoptinandmake$server_factsdefault,andtostopmergingtheserver_factsintothenode'sparametersWhenusingpuppetapplyand{{trusted_server_facts}}istrue,the {{ $server_facts }} willbeahashwithonlythekey{{environment}}set.Thevalueforthiskeyistheenvironmentthatwasconfiguredlocallyontheagent,orgivenonthecommandline(i.e.inthiscasethereisnocalltothemastertocomputewhatthemasterthinkstheenvironmentshouldbeforthenode).h3.anexample$server_factshash{serverversion=4.0.0,servername=v85ix8blah.delivery.puppetlabs.net,serverip=10.32.115.182,environment=production}QA---risk:highprobability:mediumseverity:high(hardtodebug,somewhatofasecurityissue,canspoofenvironment)testlayer:acceptance 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
   

Jira (FACT-628) facter returns incorrect value for `facter virtual` for Solaris Ldoms

2015-05-18 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg assigned an issue to QA 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-628 
 
 
 
  facter returns incorrect value for `facter virtual` for Solaris Ldoms  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Status:
 
 Readyfor CI Test 
 
 
 

Assignee:
 
 QA 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4497) Yum package provider: ensure = latest fails when obsoleted packages are present

2015-05-18 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4497 
 
 
 
  Yum package provider: ensure = latest fails when obsoleted packages are present  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Summary:
 
 Yumpackageprovider:ensure=latestfailswhen obseleted obsoleted packagesarepresent 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4604) pip does not work on CentOS7

2015-05-18 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4604 
 
 
 
  pip does not work on CentOS7  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 

Priority:
 
 Blocker Normal 
 
 
 

Issue Type:
 
 Bug Task 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-735) Status unchanged when Could not apply complete catalog

2015-05-18 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-735 
 
 
 
  Status unchanged when Could not apply complete catalog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Release Notes:
 
 BugFix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4604) Port fix for pip provider on more recent RedHat operating systems.

2015-05-18 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4604 
 
 
 
  Port fix for pip provider on more recent RedHat operating systems.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 

Summary:
 
 Portfixfor pip doesnotwork provider on CentOS7 morerecentRedHatoperatingsystems. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-400) Manage hidden windows packages

2015-05-18 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-400 
 
 
 
  Manage hidden windows packages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Release Notes:
 
 NewFeature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4178) defined() function returns true for undef and empty string, and false for main

2015-05-18 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4178 
 
 
 
  defined() function returns true for undef and empty string, and false for main  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Release Notes:
 
 BugFix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4198) Add install_options feature to pip provider

2015-05-18 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4198 
 
 
 
  Add install_options feature to pip provider  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Release Notes:
 
 NewFeature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4203) Add ':uninstall_options' to gem provider

2015-05-18 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4203 
 
 
 
  Add ':uninstall_options' to gem provider  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Release Notes:
 
 NewFeature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4420) Executable external facts broken in 4.0.0: not executable on agent

2015-05-18 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4420 
 
 
 
  Executable external facts broken in 4.0.0: not executable on agent  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Release Notes:
 
 BugFix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-1842) Backport Gemfile and whatever other spec fixes are needed to the stdlib 3.2.x branch

2015-05-18 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-1842 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Backport Gemfile and whatever other spec fixes are needed to the stdlib 3.2.x branch  
 
 
 
 
 
 
 
 
 
 
Branan Riley I ran across this ticket, and it looks like a stdlib issue that was eventually merged. Could you take a look and move/close as needed? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4613) Unclear language in the spec around types being assignable from types

2015-05-18 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4613 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Unclear language in the spec around types being assignable from types  
 
 
 
 
 
 
 
 
 
 
Nicholas Fagerlund Yes, it is accurate to describe it as sets. Types are basically names of sets of (possible) values. I typically use different terms depending on what I am trying to express. If I have: 
 
 
 
 
 
 
Integer $a
 
 
 
 
 
 
 
And I am discussing possible values, the assignability term feels more intuitive since I am reasoning about what can I assign to $a ?. 
If I OTOH is trying to do some type operation e.g.: 
 
 
 
 
 
 
Numeric = Integer
 
 
 
 
 
 
 
it is more intuitive to think about types as sets of (possible) values, and the _expression_ reads as is Numeric a superset (or the same set as) Integer. So pedantically: T2 assignable to T is the same as T is a superset of T2 (or is the same set) is the same as T = T2. I am not sure if the term superset is applicable when two sets are identical - maybe there is a special term.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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

Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)

2015-05-18 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-3829 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: pip package provider is broken on EL (where osfamily is RedHat)  
 
 
 
 
 
 
 
 
 
 
This is also available in 3.8.1. I update the Fix Version to note that. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4437) Update the puppet-agent Repo for 4.0.1 to Incorporate Fix for PUP-4390

2015-05-18 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4437 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Update the puppet-agent Repo for 4.0.1 to Incorporate Fix for PUP-4390  
 
 
 
 
 
 
 
 
 
 
This fix sems to also be in 3.8.1 (updated the Fix version), but the commit b9c6b9b is tagged with the ticket PUP 4390 which is targeting 3.8.0. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (FACT-993) Tag the release and create packages

2015-05-18 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  FACT-993 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Tag the release and create packages  
 
 
 
 
 
 
 
 
 
 
This sha can be tagged with 2.4.4: 20fb9e43b08bc2692311ff05f2767a365ba904ad 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4571) Is there a JIRA ticket targeted at the release for every commit?

2015-05-18 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4571 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Is there a JIRA ticket targeted at the release for every commit?  
 
 
 
 
 
 
 
 
 
 


PUP-4390
 is fixed in 3.8.0 with a follow up in 

PUP-4437
 for 3.8.1 (originally targeting 4.0.1). The commit (b9c6b9b) is labeled with 

PUP-4390
. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts

2015-05-18 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg assigned an issue to QA 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-2630 
 
 
 
  Server-set global variables like $::environment get overwritten by client facts  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Status:
 
 Readyfor CI Test 
 
 
 

Assignee:
 
 QA 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-4604) Port fix for pip provider on more recent RedHat operating systems.

2015-05-18 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg assigned an issue to QA 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4604 
 
 
 
  Port fix for pip provider on more recent RedHat operating systems.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Status:
 
 Readyfor CI Test 
 
 
 

Assignee:
 
 JoshCooper QA 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-1295) Yum provider purge target runs irrespective of package installation status

2015-05-18 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg assigned an issue to QA 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-1295 
 
 
 
  Yum provider purge target runs irrespective of package installation status  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Status:
 
 Readyfor CI Test 
 
 
 

Assignee:
 
 QA 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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


  1   2   >