date:20160104

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1276 
 
 
 
  Module level external facts not resolved when using the Vagrant Puppet provider  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Fix Version/s:
 
 FACT 3.1.4 
 
 
 

Fix Version/s:
 
 FACT 3.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2267) puppetdb-access.log does not log access requests to a hostname/IP it is not listening to

2016-01-04 Thread Rob Nelson (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Nelson commented on  PDB-2267 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb-access.log does not log access requests to a hostname/IP it is not listening to  
 
 
 
 
 
 
 
 
 
 
Ken, I really should have caught the first issue (rejected by OS, not application), whoops! 
On the second, I guess the question is, where are the debug/error logs for puppetdb? If someone tries to connect and has issues or is malicious and it results in a flood on port 8081, would I currently be able to see this in any log? I haven't found that so far. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-1157) puppet should support data in modules

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-1157 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet should support data in modules  
 
 
 
 
 
 
 
 
 
 
Jo Rhett, yes, thanks - I will close this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5143) Add node definition for Ubuntu 15.10 (i386, x86_64) to Puppet

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5143 
 
 
 
  Add node definition for Ubuntu 15.10 (i386, x86_64) to Puppet  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Fix Version/s:
 
 PUP 4.3.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (FACT-1195) Add node definition for Ubuntu 15.10 (i386, x86_64) to Facter

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1195 
 
 
 
  Add node definition for Ubuntu 15.10 (i386, x86_64) to Facter  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Fix Version/s:
 
 FACT 3.1.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5143) Add node definition for Ubuntu 15.10 (i386, x86_64) to Puppet

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-5143 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add node definition for Ubuntu 15.10 (i386, x86_64) to Puppet  
 
 
 
 
 
 
 
 
 
 
This is obviated by the use of beaker-hostgenerator. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (HI-440) Add node definition for Ubuntu 15.10 (i386, x86_64) to Hiera

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-440 
 
 
 
  Add node definition for Ubuntu 15.10 (i386, x86_64) to Hiera  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Fix Version/s:
 
 HI 3.0.6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5612) Error message for declaring resource without title is confusing

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5612 
 
 
 
  Error message for declaring resource without title is confusing  
 
 
 
 
 
 
 
 
 
 
Merged to stable at: 4ef4424 
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Release Notes Summary:
 
 Error message for "resource without title" has been improved and is now specifically pointing this out instead of presenting a generic message. 
 
 
 

Release Notes:
 
 Bug Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5589) Type without namevar causes failures with no error

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5589 
 
 
 
  Type without namevar causes failures with no error  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP 4.3.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2132) Add a `resources-graph` view for CM folks

2016-01-04 Thread Andrew Roetker (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Roetker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2132 
 
 
 
  Add a `resources-graph` view for CM folks  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Roetker 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 

Scope Change Reason:
 
 Holiday planning meeting was weird, this should have been in the sprint and is mostly done 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2284) add error handling for from when issued against specific endpoints

2016-01-04 Thread Wyatt Alt (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2284 
 
 
 
  add error handling for from when issued against specific endpoints  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/01/04 1:10 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
Currently we do this: 
 
 
 
 
 
 
[~/work/puppetdb] (ticket/master/pdb-1925-pql-translation-to-ast) $ curl -X GET http://localhost:8080/pdb/query/v4/facts -d 'query=["from","facts",["~","certname",".*"]]'

Jira (PUP-5589) Type without namevar causes failures with no error

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5589 
 
 
 
  Type without namevar causes failures with no error  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Release Notes Summary:
 
 Faulty implementation of a resource type could lead to compilation/apply that failed without presenting a reason. Such problems are now logged. 
 
 
 

Release Notes:
 
 Bug Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (FACT-1282) networking.ip should fall back to default route 'src' if networking.primary has no IP address

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1282 
 
 
 
  networking.ip should fall back to default route 'src' if networking.primary has no IP address  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Fix Version/s:
 
 FACT 3.1.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5589) Type without namevar causes failures with no error

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5589 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Type without namevar causes failures with no error  
 
 
 
 
 
 
 
 
 
 
merged to stable at: 68cfc9e 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2267) puppetdb-access.log does not log access requests to a hostname/IP it is not listening to

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2267 
 
 
 
  puppetdb-access.log does not log access requests to a hostname/IP it is not listening to  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Sprint:
 
 PuppetDB 2016-01-27 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2267) puppetdb-access.log does not log access requests to a hostname/IP it is not listening to

Title: Message Title

Kenneth Barber commented on PDB-2267

Re: puppetdb-access.log does not log access requests to a hostname/IP it is not listening to

This really describes 2 issues I think.
So in regards to your first problem in the description Rob, your curl against localhost should log, because its listening on localhost. But host = localhost won't necessarily accept connections on your 10.0.0.134 address, the tcpdump you've sent doesn't prove the server is listening on this port, it seems to me like the packets are being rejected by the OS, not accepted. Anyway, if you've set host = localhost, it should only listen on the hostname that resolves to (and by the way, you should really set this to an IP address not a hostname fwiw). You can prove this with a netstat -anp | grep java, to see where its listening to. So I'm not convinced the first problem curling localhost v 10.0.0.134 on clear text is valid ... it just looks like we don't listen, so therefore no - we don't log. Perhaps I'm wrong, provide more info if you think so. Also btw, if you look at your first tcpdump, the R responses from 10.0.0.134 indicate a reset - not a successful TCP handshake, which is needed (as well as the HTTP request) for us to log I guess .
Now as far as the second problem and SSL, I don't think its that surprising that a failed SSL negotiation won't log. If an SSL negotiation failed, no actually HTTP request was sent. As we know, SSL is a wrapper around HTTP really, so SSL negotiation has to succeed first ... if SSL fails, what can we log? That is, we never see the GET request, the URL, nor the hostname or query params if SSL fails, so its not at all surprising an access log wasn't dropped. I'm pretty sure we can't just 'fix this', its endemic to the protocol ... I mean, what would we log exactly anyway? Be mindful, the access log HTTP requests only, to me, it just didn't get this far up the network stack to do this. Instead, SSL negotiation errors usually get logged as debug or errors in the main log, not in the access log - I think you'll find Apache is the same here when you're using client SSL authentication.

Add Comment

This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

Jira (PUP-5626) empty dependencies in a module break puppet module tool for unrelated modules

2016-01-04 Thread Heidi Pio (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Heidi Pio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5626 
 
 
 
  empty dependencies in a module break puppet module tool for unrelated modules  
 
 
 
 
 
 
 
 
 

Change By:
 
 Heidi Pio 
 
 
 

Scrum Team:
 
 Modules Code Management 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5626) empty dependencies in a module break puppet module tool for unrelated modules

2016-01-04 Thread Heidi Pio (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Heidi Pio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5626 
 
 
 
  empty dependencies in a module break puppet module tool for unrelated modules  
 
 
 
 
 
 
 
 
 

Change By:
 
 Heidi Pio 
 
 
 

Sprint:
 
 CODEMGMT 2016-01-13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-5461 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output  
 
 
 
 
 
 
 
 
 
 
Another idea would be to make 

-manifest  mutually exclusive to using 
-evaluate . 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output

Title: Message Title

Henrik Lindberg commented on PUP-5461

Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output

Not sure what apply does there - it should work the same way; with apply using a path to a file and puppet code on the command line is mutually exclusive, but I think it still honors manifest, and possibly also code - but I am not sure. This command should work the same way, or it will be confusing.
It is also separate from the issue if you want any manifest code at all to be evaluated or not. (Naturally, if you state that "hey, no evaluation please" and specifying manually that code should be evaluated (with --manifest, or --execute/--evaluate or --code or whatever) at the same time then that is an error since you asked for something that does not make sense (giving more specific values to what you are also saying should be ignored)).

Add Comment

This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

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

Jira (PUP-5593) Update Cumulus Node config to use VM from VMpooler

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-5593 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update Cumulus Node config to use VM from VMpooler  
 
 
 
 
 
 
 
 
 
 
Stan Duffy, puppet-agent CI has moved to using beaker-hostgenerator. Given that, is this ticket still actionable? Or do we need a ci-job-configs Pull Request to add cumulus? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2285) an empty field list behaves like * in an extract statement

2016-01-04 Thread Wyatt Alt (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2285 
 
 
 
  an empty field list behaves like * in an extract statement  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/01/04 1:13 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
Currently 
 
 
 
 
 
 
curl -X GET http://localhost:8080/pdb/query/v4/facts -d 'query=["extract", [], ["~", "certname", ".*"]]'
 
 
 
 
 
 
 
will return all facts. I'm not sure that makes sense. We should figure out what we want it to do and make sure behavior is consistent with the corresponding PQL case. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

Jira (PUP-5644) puppet lookup command creates new SSL hierarchy with self-signed CA

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

 
 
 
 
 
 
 
 Puppet /  PUP-5644 
 
 
 
  puppet lookup command creates new SSL hierarchy with self-signed CA  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 

Scope Change Category:
 
 Found 
 
 
 

Scope Change Reason:
 
 Annoying and easy to fix. 
 
 
 

Story Points:
 
 1 
 
 
 

Sprint:
 
 Language 2016-01-13 
 
 
 

Fix Version/s:
 
 PUP 4.3.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

Jira (PUP-5623) Callable type should be able to describe return type

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene commented on  PUP-5623 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Callable type should be able to describe return type  
 
 
 
 
 
 
 
 
 
 
The spec calls for an optional Callable that comes after the min/max to specify the signature of the block, correct? 
It seems strange to me to have to pass an array like this (taking a hash in the future makes complete sense, though). Is this simply to save users that want to specify a return type, but use default min/max/block from having to type ..., default, default, default, ReturnType (i.e. default min, max, and block types)? 
In the array syntax, can users still specify a min/max/block? Would it be ArgTypeArray, ReturnType, min, max, BlockType? 
To me, it's more consistent to just add the return type as an optional (as stated, defaulted to Any) last parameter rather than using an array. 
The future hash format could then also be a consistent ArgsHash, min, max, BlockType, ReturnType to match. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-5461 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output  
 
 
 
 
 
 
 
 
 
 
Puppet apply treats the non-option argument as the manifest file name. There can only be one. Puppet lookup treats such arguments as the keys to lookup. So it's not possible to make them work the same way. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-1072) support HTTP(S) URL as the file 'source'

2016-01-04 Thread John Duarte (JIRA)

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

 
 
 
 
 
 
 
 Puppet /  PUP-1072 
 
 
 
  support HTTP(S) URL as the file 'source'  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Assignee:
 
 qa John Duarte 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5209) call_function and metadata.json: call a function from a different module, very strange behavior

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

 
 
 
 
 
 
 
 Puppet /  PUP-5209 
 
 
 
  call_function and metadata.json: call a function from a different module, very strange behavior  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-5461 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output  
 
 
 
 
 
 
 
 
 
 
So, you don't think it's valuable to be able to run a lookup "exactly as things are configured" ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5648) Descending range sematics are broken

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5648 
 
 
 
  Descending range sematics are broken  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.3.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/01/04 3:53 PM 
 
 
 

Fix Versions:
 

 PUP 4.3.2 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Peter Huene 
 
 
 
 
 
 
 
 
 
 
Commit 3a9db247c432d469e625d4abf7bee8e747178af9 regressed support for "descending" ranges, where the "max" is less than the "min": 
 
 
 
 
 
 
notice Integer[5, 1] 
 
 
 
 
Integer[5, 1].each |$x| {

Jira (PUP-5648) Descending range semantics are broken in the compiler

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5648 
 
 
 
  Descending range semantics are broken in the compiler  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 

Summary:
 
 Descending range  sematics  semantics  are broken  in the compiler 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5648) Descending range semantics are broken in the compiler

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5648 
 
 
 
  Descending range semantics are broken in the compiler  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 
 
 
 
 
 
 
 Commit 3a9db247c432d469e625d4abf7bee8e747178af9 regressed support for "descending" ranges, where the "max" is less than the "min":{code}notice Integer[5, 1]Integer[5, 1].each |$x| {  notice $x}{code}This is expected to output:{code}Notice: Scope(Class[main]): Integer[5, 1]Notice: Scope(Class[main]): 5Notice: Scope(Class[main]): 4Notice: Scope(Class[main]): 3Notice: Scope(Class[main]): 2Notice: Scope(Class[main]): 1{code}This is because having a maximum less than a minimum treats the range as being in "descending" order.Instead, this is the actual output:{code}Notice: Scope(Class[main]): Integer[1, 5]Notice: Scope(Class[main]): 1Notice: Scope(Class[main]): 2Notice: Scope(Class[main]): 3Notice: Scope(Class[main]): 4Notice: Scope(Class[main]): 5{code}It appears the min and max are silently being swapped when the max < min.Related: I believe the compiler should error if a type is given a max argument less than a min argument when the type does not support a "descending" semantic, e.g. {{Callable[1, 0]}} should error rather than silently swapping the min and max  (I really dislike magic in compilers) . 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email

Jira (PDB-997) Add Ubuntu 14.04/trusty to acceptance testing

2016-01-04 Thread Kurt Wall (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall commented on  PDB-997 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add Ubuntu 14.04/trusty to acceptance testing  
 
 
 
 
 
 
 
 
 
 
Kenneth Barber Kindly recommend someone who can help me understand what to do and it will be get this done. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output

Title: Message Title

Henrik Lindberg commented on PUP-5461

Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output

Jo Rhett a problem in the past with the hiera command line is that it does not do it quite the same way as lookups are made when compiling a catalog - this meant users had to use puppet apply and write a notify with a call to hira to see the actual real result. The results are different as real code can define things that affects the lookup - naturally that option needs to be available. Most do however not rely on that, and the execution of lookup command line will be speeded up by not loading and evaluating everything (all of the time). We have that figured out, it is many a question of UX regarding the command line options. I don't think we need to come up with a new special way of doing the actual searches for values - that is complex, and already implemented. What we are talking about is just compile or not, and what the flags should be.
I think it is as simple as having one flag that turns on "full catalog" and that the rest is controlled with the settings and options already available in puppet. I can imagine calling this flag --compile and the default being --no-compile.

Add Comment

This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5461 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output  
 
 
 
 
 
 
 
 
 
 
Well, it really does not have to do all the various things apply can do. You have an option to set variables that is probably what you want to do ayway. If you want something else, you can always use the --manifest setting to point to a file of your choice, or set -- code. I think that is good enough. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (FACT-959) Incorrect processor counts on Windows

2016-01-04 Thread John Duarte (JIRA)

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

 
 
 
 
 
 
 
 Facter /  FACT-959 
 
 
 
  Incorrect processor counts on Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Assignee:
 
 qa John Duarte 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-1072) support HTTP(S) URL as the file 'source'

2016-01-04 Thread John Duarte (JIRA)

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

 
 
 
 
 
 
 
 Puppet /  PUP-1072 
 
 
 
  support HTTP(S) URL as the file 'source'  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Assignee:
 
 John Duarte Kylo Ginsberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output

2016-01-04 Thread Jo Rhett (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jo Rhett commented on  PUP-5461 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output  
 
 
 
 
 
 
 
 
 
 
While I personally would enjoy flexibility, I believe that most users tend to assume "with the same config I'm already using" unless overridden. Some of the less intuitive parts of Puppet were due to things that made no assumptions, which is good for the coder but confusing for the user. 
I think the expected and reasonable response is for puppet lookup this.that to use exactly the same context that "puppet agent" or "puppet apply noop.pp" would have with no other options. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5593) Update Cumulus Node config to use VM from VMpooler

2016-01-04 Thread Rick Sherman (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rick Sherman commented on  PUP-5593 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update Cumulus Node config to use VM from VMpooler  
 
 
 
 
 
 
 
 
 
 
FYI system is now in vmpooler. cumulus-vx-25-x86_64 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2230) Include header information in the command POST

2016-01-04 Thread Wyatt Alt (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt assigned an issue to Wyatt Alt 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2230 
 
 
 
  Include header information in the command POST  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Assignee:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5626) empty dependencies in a module break puppet module tool for unrelated modules

2016-01-04 Thread Alexander Johnson (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexander Johnson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5626 
 
 
 
  empty dependencies in a module break puppet module tool for unrelated modules  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alexander Johnson 
 
 
 

Sprint:
 
 CODEMGMT 2016-01-13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-5461 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output  
 
 
 
 
 
 
 
 
 
 
Well, puppet agent will run manifests/site.pp and puppet apply noop.pp will run noop.pp. The former might contain a whole slew of things. So which one would you consider to be best when lookup runs without options? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-997) Add Ubuntu 14.04/trusty to acceptance testing

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber commented on  PDB-997 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add Ubuntu 14.04/trusty to acceptance testing  
 
 
 
 
 
 
 
 
 
 
@kurt most of the work is done, we already have the Ubuntu 14.04 images in: https://github.com/puppetlabs/puppetdb/blob/master/acceptance/config/ec2-west-ubuntu1404-64mda.cfg 
All we need to do really, is to have these added to the testing pipeline (jenkins JJB), and fix any test failures we see on Ubuntu 14.04. 
For JJB, I think this might be the list that needs a PR: 
https://github.com/puppetlabs/ci-job-configs/blob/master/enterprise/projects/puppetdb.yaml#L85 
But before we do any of that, we probably just want to attempt to run these tests using beaker from the command line perhaps using these new Ubuntu 14.04 images, otherwise trying to change the job and fix as we go will be too disruptive to our production pipeline. The other alternative we used to take was clone a job, but in a JJB world this seems that will require QENG now - not sure, it would be a real shame if we've lost this ability. 
I know that when we briefly tested this before, there was some errors about ruby packages and such, probably spawned by some of this magic: https://github.com/puppetlabs/puppetdb/tree/master/acceptance/setup/pre_suite, but I can't recall the details. 
I honestly don't expect a massive amount of problems in changing the setup to make this work however, beyond package variations but you never know. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-5461 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output  
 
 
 
 
 
 
 
 
 
 
Jo Rhett, yes of course. All files under manifests. The reason we care about code in general is that Hiera interpolation can use scope variables. Any code can declare global variables in the top scope and may hence impact a lookup, both values and the actual lookup configuration. 
Henrik Lindberg, I like keeping it simple, but isn't ---no-compile a bit confusing. I think we will still compile things like function data providers. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2267) puppetdb-access.log does not log access requests to a hostname/IP it is not listening to

Title: Message Title

Kenneth Barber commented on PDB-2267

Re: puppetdb-access.log does not log access requests to a hostname/IP it is not listening to

So this stuff doesn't log by default, seems Jetty logs this at a debug level. One way to solve this, would be to modify your logback.xml to log the correct class & DEBUG level to file.
So `puppetdb foreground --debug` gives you the flood gates btw, and if you do a curl with a -k, you get an exception: https://gist.github.com/kbarber/ca45d596bbdb4d8b1d70
So what you want here, is to modify logback.xml to raise that up just for anything in `org.eclipse.jetty.server.HttpConnection`, this rule applies to anything interesting in that debug log btw, so you can adapt these instructions for other logging namespaces etc.
Anyway, your logback.xml should be modified kind of like this:
{{ ... snip ...
... snip ... }}
Its going to drop other noise, I have no idea how much though on average . For me its about 3-4 lines per connection, but at least you'll see the exceptions.
I think jetty by default doesn't show these at say info or error, because for most cases, a public website certainly doesn't care all that much about the dozens and dozens of SSL attempts they get per second - they'd simply get inundated with bad messages just due to automated scripts from bots and such.

Add Comment

This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

Jira (PUP-5649) "syncversion" maybe obsolete for selmodule type in Fedora >= 23

2016-01-04 Thread Martin Jackson (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Jackson created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5649 
 
 
 
  "syncversion" maybe obsolete for selmodule type in Fedora >= 23  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.3.1 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Types and Providers 
 
 
 

Created:
 

 2016/01/04 6:31 PM 
 
 
 

Environment:
 
 
Fedora F22 packages/Puppet 4.3.1 code running on Fedora 23 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Martin Jackson 
 
 
 
 
 
 
 
 
 
 
Under CentOS 7, semodule -l (which the selmodule provider uses to check the loaded module version) returns a version number, e.g. (from CentOS 7): 
root@srv-cfgmgt ~ 
 

semodule -l abrt 1.4.1  accountsd 1.1.0  acct 1.6.0  afs 1.9.0  aiccu 1.1.0  aide 1.7.1  ajaxterm 1.0.0  alsa 1.12.2 
 
 
Under Fedora 23, the output looks like this (e.g. no version specified):

Jira (PUP-5623) Callable type should be able to describe return type

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5623 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Callable type should be able to describe return type  
 
 
 
 
 
 
 
 
 
 
Yes, the design was proposed to avoid specifying several defaults, but also to make it possible to present a Callable without having to always show all of the defaults (you cannot leave them out if there is a return type). 
Yes, with the proposed syntax, you can still specify min and max - i.e. 
 
 
 
 
 
 
Callable[[T1, T2, min, max, BlockType], ReturnType]
 
 
 
 
 
 
 
Remember that min/max is not really applicable if using a hash to describe "argument by name" as it would need to also state which one of the keys it is for. 
I did consider using a hash like so: 
 
 
 
 
 
 
Callable[ { params => [T1, T2, min, max, BlockType], returns => ReturnType}]
 
 
 
 
 
 
 
Then, when using a "argumens by name", the params would then refer to a Hash with param name to type associations. I have not thought about some kind of "key x captures excess args" as that gets complicated quickly. 
I also considered using parentheses around either the parameters part, or the returns part (this is sometimes used in ruby to group parameters). That would essentially be the same as the array example only using () instead of [] (It would be somewhat trickier to parse as parentheses lose their original meaning in that context). 
I basically like the separation as it indicates "this is for the parameters", and "this is for the return". I have nothing against having to spell out min, max, etc, but it starts to look ugly when presented - not sure how much that actually matters. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

Jira (PDB-997) Add Ubuntu 14.04/trusty to acceptance testing

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber commented on  PDB-997 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add Ubuntu 14.04/trusty to acceptance testing  
 
 
 
 
 
 
 
 
 
 
Actually, there is another way to do this. 
You could create a PR for the purposes of using that for testing, hand-modify the jenkins job (yes it will revert in 6 hours, but its a small cost) and then run a PR test that way with Ubuntu 14.04 manually added for confirmation. This avoids the need to clone a job, if there are acceptance changes you'll need a PR anyway and you can iterate that way. 
Otherwise launching manually is one option also, either way should work, I just suggest the PR methodology because you can rely on the jenkins box to do most of the work for you instead of having to fiddle with beaker + ec2 from your laptop. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5623) Callable type should be able to describe return type

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene commented on  PUP-5623 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Callable type should be able to describe return type  
 
 
 
 
 
 
 
 
 
 
I see, the separation between the parameter information and return type makes sense. Thanks for the clarification. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5267) puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host

2016-01-04 Thread John Simpson (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Simpson commented on  PUP-5267 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host  
 
 
 
 
 
 
 
 
 
 
With puppet-agent-1.3.2-1.osx10.11.dmg, the installer finishes and both pxp-agent and mcollectived are running, but after adding /opt/puppetlabs/puppet/bin to my PATH, any puppet commands (including both puppet agent -t and puppet agent --fingerprint) both die with the "Illegal instruction: 4" message. 
This is on a Mac Mini (Mid 2010) running OSX 10.11.2. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5461 
 
 
 
  puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Scope Change Category:
 
 Found 
 
 
 

Affects Version/s:
 
 PUP 4.3.0 
 
 
 

Affects Version/s:
 
 PUP 4.3.1 
 
 
 

Scope Change Reason:
 
 Design flaw. Must be resolved A.S.A.P. 
 
 
 

Story Points:
 
 1 
 
 
 

Sprint:
 
 Language 2016-01-13 
 
 
 

Scrum Team:
 
 Language 
 
 
 

Fix Version/s:
 
 PUP 4.3.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-5461 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output  
 
 
 
 
 
 
 
 
 
 
I think a user will find it rather surprising that a lookup invocation actually evaluates the catalog. I therefore suggest that we change this and make the default evaluation evaluate something that is harmless and silent like: 
 
 
 
 
 
 
class noop{}
 
 
 
 
 
 
 
We could then equip the lookup command with an additional option to enforce the normal default evaluation such as --evaluate to make it perform the default evaluation (i.e. site.pp). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output

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

 
 
 
 
 
 
 
 Puppet /  PUP-5461 
 
 
 
  puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-997) Add Ubuntu 14.04/trusty to acceptance testing

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-997 
 
 
 
  Add Ubuntu 14.04/trusty to acceptance testing  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Fix Version/s:
 
 PDB 3.2.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5646) fqdn_rand in real world - only 336 of possible 1440 daily cron slots ever used.

2016-01-04 Thread Steve Traylen (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Traylen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5646 
 
 
 
  fqdn_rand in real world - only 336 of possible 1440 daily cron slots ever used.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 newresults.dat, newresults.png, results.dat, results.png, test_fqdn.rb 
 
 
 

Created:
 

 2016/01/04 7:15 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Steve Traylen 
 
 
 
 
 
 
 
 
 
 
Take the very typical code for once per day cron on 5 hosts named 1.example.org, 2.example.org , ... 
 
 
 
 
 
 
cron{'/bin/true': 
 
 
 
 
   minute => fqdn_rand(60), 
 
 
 
 
   hour=> fqdn_rand(24)

Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output

Title: Message Title

Henrik Lindberg commented on PUP-5461

Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output

I agree with Thomas (only evaluating something like class noop {}, and also avoiding calls that populates the catalog with classes to include from an ENC etc. I think that is a default that suits most users.
I think it would be better to say something other that default to get "no evaluation" since the word "default" is ambiguous, is it the default production env, the default manifest (site.pp) or something else? The flags should also correspond to what is already in use for other puppet commands (i.e

e/evaluat is for evaluating what is given on the command line,
-manifest is for referencing the site.pp/manifest to evaluate etc. Have no immediate suggestion on name of flag though.

Add Comment

This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

Jira (PDB-1927) PQL: Tighten up prototype ready for review and merging (code, tests & docs)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1927 
 
 
 
  PQL: Tighten up prototype ready for review and merging (code, tests & docs)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Fix Version/s:
 
 PDB 4.0.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2242) Replace moustache with compojure or comidi entirely

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2242 
 
 
 
  Replace moustache with compojure or comidi entirely  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Fix Version/s:
 
 PDB 4.0.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2126) Add the `catalog_uuid` field to catalogs and `reports`

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2126 
 
 
 
  Add the `catalog_uuid` field to catalogs and `reports`  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Fix Version/s:
 
 PDB 4.0.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2230) Include header information in the command POST

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2230 
 
 
 
  Include header information in the command POST  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Fix Version/s:
 
 PDB 4.0.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2131) Use the FOSS mechanisms to turn on historical catalogs in PE.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2131 
 
 
 
  Use the FOSS mechanisms to turn on historical catalogs in PE.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Fix Version/s:
 
 PDB 4.0.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2132) Add a `resources-graph` view for CM folks

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2132 
 
 
 
  Add a `resources-graph` view for CM folks  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Fix Version/s:
 
 PDB 4.0.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2277) (maint) Improve memory usage in benchmark tool

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2277 
 
 
 
  (maint) Improve memory usage in benchmark tool  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Fix Version/s:
 
 PDB 4.0.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-1927) PQL: Tighten up prototype ready for review and merging (code, tests & docs)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber assigned an issue to Kenneth Barber 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1927 
 
 
 
  PQL: Tighten up prototype ready for review and merging (code, tests & docs)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Assignee:
 
 Kenneth Barber 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2276) Remove usage of robert.hooke for tk-config

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2276 
 
 
 
  Remove usage of robert.hooke for tk-config  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Fix Version/s:
 
 PDB 4.0.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5378) acceptance: backport call all parser functions test to 3.x

2016-01-04 Thread Josh Cooper (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-5378 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: acceptance: backport call all parser functions test to 3.x  
 
 
 
 
 
 
 
 
 
 
Eric Thompson The test is failing in CI for most, but not all linux platforms, not sure why that is: https://jenkins.puppetlabs.com/job/legacy_puppet_integration-system_linux_3.x/8/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2282) (maint) Enable sudo again to allow workaround for java bug

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2282 
 
 
 
  (maint) Enable sudo again to allow workaround for java bug  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/01/04 9:09 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
The bug described here: https://github.com/travis-ci/travis-ci/issues/5227 
... and its work-around requires sudo, so we need to remove the sudo:false setting for this to work. This is temporary until the bug is fixed upstream. 
Signed-off-by: Ken Barber  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

Jira (PDB-2282) (maint) Enable sudo again to allow workaround for java bug

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2282 
 
 
 
  (maint) Enable sudo again to allow workaround for java bug  
 
 
 
 
 
 
 
 
 

Change By:
 
 gepetto-bot 
 
 
 

Sprint:
 
 PuppetDB 2016-01-13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2282) (maint) Enable sudo again to allow workaround for java bug

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber assigned an issue to Kenneth Barber 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2282 
 
 
 
  (maint) Enable sudo again to allow workaround for java bug  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Assignee:
 
 Kenneth Barber 
 
 
 

Fix Version/s:
 
 PDB 4.0.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2282) (maint) Enable sudo again to allow workaround for java bug

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2282 
 
 
 
  (maint) Enable sudo again to allow workaround for java bug  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Scope Change Category:
 
 Found 
 
 
 

Scope Change Reason:
 
 Bug in travis tests after rollup 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2283) Full copy edit of PuppetDB docs

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2283 
 
 
 
  Full copy edit of PuppetDB docs  
 
 
 
 
 
 
 
 
 

Change By:
 
 gepetto-bot 
 
 
 

Sprint:
 
 PuppetDB 2016-01-13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2283) Full copy edit of PuppetDB docs

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2283 
 
 
 
  Full copy edit of PuppetDB docs  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/01/04 9:29 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
Copy edit of full docs set, with a focus on: 
 

Sentence casing all headings
 

Ensuring adherence to Puppet's documentation style guide
 

Consistency of formatting/usage/etc. across the docs set
 
 
Please let me know if you have any questions or problems! Thanks.   
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

Jira (PDB-2286) Keep jsonb column storage even when historical catalogs is off

2016-01-04 Thread Andrew Roetker (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Roetker created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2286 
 
 
 
  Keep jsonb column storage even when historical catalogs is off  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/01/04 1:44 PM 
 
 
 

Fix Versions:
 

 PDB 4.0.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Andrew Roetker 
 
 
 
 
 
 
 
 
 
 
Currently we allow users to turn off historical catalogs but also stop storing the resources and edges blobs which means the new views won't work with the latest catalog when historical catalogs is turned off. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output

2016-01-04 Thread Jo Rhett (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jo Rhett commented on  PUP-5461 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output  
 
 
 
 
 
 
 
 
 
 
Actually agent defaults to --manifestdir manifests/ now doesn't it?  
(probably due to ignorance) I'm having trouble imagining why we'd care about code that isn't a data provider. So I think that would mean: 
1. Read the global data (Hiera v3) for the lookup key 2. Read the environment.conf for an environment_data_source. Look for key if available. 3. Identify the classes to run, check each module for a data_provider and query that. 
Hm. Seems like a lot of work. Why not just grab the looked up values from the last catalog stored? 
tricky tricky stuff. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5443) Arithmetic expressions don't work in selectors

2016-01-04 Thread Gareth Humphries (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Gareth Humphries updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5443 
 
 
 
  Arithmetic expressions don't work in selectors  
 
 
 
 
 
 
 
 
 

Change By:
 
 Gareth Humphries 
 
 
 

Component/s:
 
 Language 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5443) Arithmetic expressions don't work in selectors

2016-01-04 Thread Gareth Humphries (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Gareth Humphries updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5443 
 
 
 
  Arithmetic expressions don't work in selectors  
 
 
 
 
 
 
 
 
 

Change By:
 
 Gareth Humphries 
 
 
 

Labels:
 
 arithmetic_expression selector 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2283) Full copy edit of PuppetDB docs

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2283 
 
 
 
  Full copy edit of PuppetDB docs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 

Scope Change Reason:
 
 PR raised from docs 
 
 
 

Issue Type:
 
 Bug Improvement 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5626) empty dependencies in a module break puppet module tool for unrelated modules

2016-01-04 Thread Heidi Pio (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Heidi Pio updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5626 
 
 
 
  empty dependencies in a module break puppet module tool for unrelated modules  
 
 
 
 
 
 
 
 
 

Change By:
 
 Heidi Pio 
 
 
 

Sprint:
 
 PE 2016.1 - Burnside 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5647) Resource is stored by path and not by $name

2016-01-04 Thread Lindsey Smith (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lindsey Smith moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5647 
 
 
 
  Resource is stored by path and not by $name  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lindsey Smith 
 
 
 

Component/s:
 
 Modules 
 
 
 

Key:
 
 ENTERPRISE PUP - 850 5647 
 
 
 

Project:
 
 Puppet  Enterprise 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5538) Puppet fails to convert Windows Unicode group or user names to sids

2016-01-04 Thread Ryan Gard (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Gard updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5538 
 
 
 
  Puppet fails to convert Windows Unicode group or user names to sids  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Gard 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 

QA Status:
 
 Reviewed 
 
 
 

QA Contact:
 
 Ryan Gard 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2283) Full copy edit of PuppetDB docs

2016-01-04 Thread Mindy Moreland (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mindy Moreland commented on  PDB-2283 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Full copy edit of PuppetDB docs  
 
 
 
 
 
 
 
 
 
 
Pull request: https://github.com/puppetlabs/puppetdb/pull/1801 
JIRA cross-reference: DOC-1588 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5443) Arithmetic expressions don't work in selectors

2016-01-04 Thread Gareth Humphries (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Gareth Humphries updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5443 
 
 
 
  Arithmetic expressions don't work in selectors  
 
 
 
 
 
 
 
 
 

Change By:
 
 Gareth Humphries 
 
 
 

Affects Version/s:
 
 PUP 3.7.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2242) Replace moustache with compojure or comidi entirely

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2242 
 
 
 
  Replace moustache with compojure or comidi entirely  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 

Scope Change Reason:
 
 Pulled into sprint 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-997) Add Ubuntu 14.04/trusty to acceptance testing

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-997 
 
 
 
  Add Ubuntu 14.04/trusty to acceptance testing  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 

Scope Change Reason:
 
 QA to work on 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5612) Error message for declaring resource without title is confusing

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5612 
 
 
 
  Error message for declaring resource without title is confusing  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Sprint:
 
 Language  Triage  2016-01-13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5646) fqdn_rand in real world - only 336 of possible 1440 daily cron slots ever used.

2016-01-04 Thread Steve Traylen (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Traylen commented on  PUP-5646 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: fqdn_rand in real world - only 336 of possible 1440 daily cron slots ever used.  
 
 
 
 
 
 
 
 
 
 
https://github.com/puppetlabs/puppet/pull/4543 
implements to the trivial change to include max in the seed input. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-5461 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output  
 
 
 
 
 
 
 
 
 
 
The term "default" was chosen to mean whatever puppet would normally evaluate. The exact meaning must be specified in the config. We could use a term like 'as_configured' but I personally like 'default' better. 
I think there are four cases: 
 

Don't evaluate anything (use the noop class).
 

Evaluate whatever Puppet is configured to evaluate (what I call --evaluate default)
 

Provide a script string to --evaluate

Jira (PUP-5571) Missing API docs for /puppet/v3/environment endpoint

2016-01-04 Thread Nicholas Fagerlund (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicholas Fagerlund commented on  PUP-5571 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Missing API docs for /puppet/v3/environment endpoint  
 
 
 
 
 
 
 
 
 
 
Two minor tweaks, and then I'll be cool to merge this.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (FACT-1282) networking.ip should fall back to default route 'src' if networking.primary has no IP address

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1282 
 
 
 
  networking.ip should fall back to default route 'src' if networking.primary has no IP address  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (FACT-1282) networking.ip should fall back to default route 'src' if networking.primary has no IP address

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1282 
 
 
 
  networking.ip should fall back to default route 'src' if networking.primary has no IP address  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Story Points:
 
 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (FACT-1282) networking.ip should fall back to default route 'src' if networking.primary has no IP address

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1282 
 
 
 
  networking.ip should fall back to default route 'src' if networking.primary has no IP address  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Sprint:
 
 Client Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output