date:20150506

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1485 
 
 
 
  Align url-prefix in foss to align with pe-puppetdb  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/05/06 3:08 AM 
 
 
 

Fix Versions:
 

 PDB 3.0.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Kenneth Barber 
 
 
 
 
 
 
 
 
 
 
We need to figure out what we want to do with the main url-prefix, right now pe-puppetdb uses /pdb for our API, and foss uses / ... this breaks the dashboard in PE by using this, I figure we should do one (or more) of the following: 
a) Make the dashboard follow the URL-prefix properly b) Change the default url-prefix to align for both shipped packages c) Consider using web-routing for these decisions in config for say FOSS, in favour of the old url-prefix potentially? This way there is one place to configure each service. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

Jira (PDB-1486) Rename /pe /sync endpoints to something more puppetdb specific

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1486 
 
 
 
  Rename /pe  /sync endpoints to something more puppetdb specific  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/05/06 3:13 AM 
 
 
 

Fix Versions:
 

 PDB 3.0.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Kenneth Barber 
 
 
 
 
 
 
 
 
 
 
The /pe  /sync endpoint could probably do with some uniqueness across applications in case we wish to later host other applications in the same JVM. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

Jira (PDB-1472) [Performance] Improvements for paged results

2015-05-06 Thread Karel Brezina (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karel Brezina commented on  PDB-1472 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: [Performance] Improvements for paged results  
 
 
 
 
 
 
 
 
 
 
Thanks Wyatt Alt for taking your time.  I'm glad that you found the strange behavior even on your machine.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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

Jira (PDB-1484) Memory leak when 'replace facts' failing

2015-05-06 Thread Simon Oxwell (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Simon Oxwell created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1484 
 
 
 
  Memory leak when 'replace facts' failing  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PDB 2.3.3 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/05/05 11:51 PM 
 
 
 

Environment:
 
 
CentOS 7, Postgres 9.2.7 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Simon Oxwell 
 
 
 
 
 
 
 
 
 
 
Hi, 
Just as an aside to 

PDB-1448
, we're also seeing PuppetDB run out of heap. 
Looking at the memory dumps, we see a very large number of Postgres Prepared Statements, taking up huge amounts of memory. 
For example, from today we had: 4,881 instances of org.postgresql.jdbc4.Jdbc4PreparedStatement with retained size of 500,866,312 bytes 
and one from a month ago: 4,614 instances of org.postgresql.jdbc4.Jdbc4PreparedStatement with retained size of 617,294,101 bytes. 
Our heap size is 750M, and 109 puppet agents. 
My guess is that when the 'replace facts' fails with the foreign key constraint violation, it doesn't clean up the prepared statement objects.

Jira (PUP-4530) FreeBSD specific Service provider fix

2015-05-06 Thread Matthew Seaman (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew Seaman created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4530 
 
 
 
  FreeBSD specific Service provider fix  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.5, PUP 3.6.2 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 puppet-3.7.5.patch 
 
 
 

Components:
 

 Platform 
 
 
 

Created:
 

 2015/05/06 4:38 AM 
 
 
 

Environment:
 
 
FreeBSD sys-puppet-1.adestra.com 10.1-RELEASE-p5 FreeBSD 10.1-RELEASE-p5 #0: Tue Jan 27 08:55:07 UTC 2015 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Matthew Seaman 
 
 
 
 
 
 
 
 
 
 
The Service provider for FreeBSD parses the output of 'service foo rcvar' to work out what the service name is. However for some services – only a very few – the output contains an optional

Jira (PUP-4045) Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket

2015-05-06 Thread Peter Souter (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Souter updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4045 
 
 
 
  Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Souter 
 
 
 
 
 
 
 
 
 
 UsingaslightlymodifiedversionofthecodefromProPuppetIamgettingthefollowingerror: {code} Jun1301:36:33mediapuppet-agent[18196]:(/Stage[main]/Mysql::Config/File[mysql_data_dir])Failedtogenerateadditionalresourcesusing'eval_generate':Cannotmanagefilesoftypesocket {code}   Thefileresourceinmysql/manifests/config.ppisasfollows: {code} file{mysql_data_dir:path=$mysql::params::data_directory,group=mysql,owner=mysql,recurse=true,require=File[my.cnf],} {code} Andforthisparticular$operatingsystem(Fedora)thevaluefor$data_directoryinmysql/manifests/params.ppis: {code} $data_directory=/var/lib/mysql {code}   BydefaultmysqlonaFedorasystemplacesitsmysql.sockfileinthedatadirectorybutitappearswhenayoutryandchangethepermissionsrecursively,puppetdoesn'tknowwhattodowiththesocketfile.IcanplacethesocketfileelsewhereasaworkaroundbutIbelievethatpuppetneedstoignoresocketfileswhenchangingpermissions. {code} [root@mediamodules]#puppet--version2.6.8[root@mediamodules]#puppetmaster--version2.6.8 {code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-4045) Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket

2015-05-06 Thread Peter Souter (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Souter commented on  PUP-4045 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket  
 
 
 
 
 
 
 
 
 
 
As someone who encountered this recently, and needed to use the workaround of adding the socket files to the `ignore` parameter, you can find out what files are sockets with `tree` easy enough: 
 
 
 
 
 
 
$ tree --inodes -F | grep = 
 
 
 
 
│ │ ├── [2458821]  S_TCP=
 
 
 
 
 
 
 
So I needed to add this to my code: 
 
 
 
 
 
 
ignore= ['S_TCP']
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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

Jira (PDB-949) Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilati

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber commented on  PDB-949 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilation.  
 
 
 
 
 
 
 
 
 
 
Charlie Sharpsteen I think perhaps you're missing the subtlety of this larger problem, or I'm not describing it very well. Ping me if you want when you're not busy, we can have a chat. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-4528) Chaining arrows do not work as expected with empty resources

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4528 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Chaining arrows do not work as expected with empty resources  
 
 
 
 
 
 
 
 
 
 
This is a known issue - IIRC there should be a warning when this happens and using the future parser.  
On the one hand it does exactly what is expected - the statement becomes depends on nothing, and nothing depends on. Not sure if we want to change that. It could be made an error, or it could short circuit (just skip the empty part). The later could lead to other hard to detect problems. An error is probably preferable as there is really no real practical use of an empty set in the middle of a chain (nor at the beginning or end of a chain). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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

Jira (FACT-956) Update puppet-agent#master to build facter#master, remove cfacter

2015-05-06 Thread Rob Reynolds (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Reynolds commented on  FACT-956 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Update puppet-agent#master to build facter#master, remove cfacter  
 
 
 
 
 
 
 
 
 
 
Puppet-Agent merged into master at 80ca92e 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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

Jira (PDB-1315) Add sync information to metrics

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1315 
 
 
 
  Add sync information to metrics  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Sprint:
 
 PuppetDB2015-05-20 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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

Jira (PDB-1313) Clojure network/node failure tests for single datacenter HA topology

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1313 
 
 
 
  Clojure network/node failure tests for single datacenter HA topology  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Sprint:
 
 PuppetDB2015-05-20 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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

Jira (PDB-949) Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilati

Title: Message Title

Kenneth Barber commented on PDB-949

Re: Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilation.

And to add more to this, by disabling trusted you're just masking the cache miss. If the master gets a cache miss, it will try to query PuppetDB for facts instead which is not desirable, so even if we fix this, we're then left with a gaping problem that users won't see until they are hours deep into an investigation. So while our use of trusted creates a confusing error message, its really surfacing a deeper issue, in that cache misses create unpredictable outcomes and do not warn the user properly.
Just to be clear in case my previous points on this are vague, we have no set of actions on this today ... nor is a real next set of steps set out. Its been suggested to us to change this behaviour and to not use 'trusted' which is certainly possible, but still - there is a bigger bug behind it and I don't think thats necessarily the full correct answer (although its a cheap way to get rid of the error I suppose . I'd be happy to have a chat to people about this if we have the time, it feels like we need a cross-team solution rather than 'just fix it on the pdb side' ... perhaps I haven't been clear on making my point - happy to clarify via a chat if required.

Add Comment

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

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

Jira (PDB-949) Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilati

2015-05-06 Thread Charlie Sharpsteen (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Charlie Sharpsteen commented on  PDB-949 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilation.  
 
 
 
 
 
 
 
 
 
 
I think the correct answer is to separate the trusted data from the fact data on the PDB side. The reason being is that these two datasets are separate attributes of the Node object, are never mixed by the compiler and always exist as distinct entities. During compilation, there are two top-scope datasets: $::trusted and $::facts, and $::facts['trusted'] is undefined. 
Now, this does also lead to a question for the Puppet side: if trusted data is coming from PDB or a cached Node object, instead of a live Node request, is it still trusted? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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

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

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


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

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 HenrikLindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-4489) Add data_provider to module metadata

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4489 
 
 
 
  Add data_provider to module metadata  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP4.2.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-355) how to run rspec-puppet with data in modules

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-355 
 
 
 
  how to run rspec-puppet with data in modules  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 Language2015-06-10 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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

Jira (PDB-1312) When starting PDB, don’t service requests until after an initial sync completes

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1312 
 
 
 
  When starting PDB, don’t service requests until after an initial sync completes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Sprint:
 
 PuppetDB2015-05-20 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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

Jira (PDB-1469) puppetdb-terminus-2.3.3-1.el6 cannot find rubygems-json package

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1469 
 
 
 
  puppetdb-terminus-2.3.3-1.el6 cannot find rubygems-json package  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Sprint:
 
 PuppetDB2015-05-20 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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

Jira (PDB-1484) Memory leak when 'replace facts' failing

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber commented on  PDB-1484 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Memory leak when 'replace facts' failing  
 
 
 
 
 
 
 
 
 
 
Simon Oxwell we can control the prepared-statement cache by adding a configuration option. I believe now its hard-coded to 1000 items, but since we have quite a few dynamic queries this can quickly get large. 
I wouldn't have expected 500 MB though, I've seen 50 MB before. Do you have a hprof dump that we can look at for this? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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

Jira (PDB-1472) [Performance] Improvements for paged results

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1472 
 
 
 
  [Performance] Improvements for paged results  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Sprint:
 
 PuppetDB2015-05-20 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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

Jira (FACT-956) Update puppet-agent#master to build facter#master, remove cfacter

2015-05-06 Thread Rob Reynolds (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Reynolds commented on  FACT-956 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Update puppet-agent#master to build facter#master, remove cfacter  
 
 
 
 
 
 
 
 
 
 
Merged into master at a32d7ecd 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





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

Jira (PDB-1467) puppetdb module has ordering problem with read_database.ini

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1467 
 
 
 
  puppetdb module has ordering problem with read_database.ini  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Component/s:
 
 Module 
 
 
 

Affects Version/s:
 
 PDBmodule-4.2.1 
 
 
 

Sprint:
 
 PuppetDB2015-05-06 
 
 
 

Story Points:
 
 0 
 
 
 

Scope Change Reason:
 
 ModulePR 
 
 
 

Scope Change Category:
 
 Found 
 
 
 

Fix Version/s:
 
 PDBmodule-4.3.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

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