date:20150126

Jira (PDB-1124) PuppetDB high CPU usage

2015-01-26 Thread Anton Fomenko (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anton Fomenko commented on  PDB-1124 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PuppetDB high CPU usage  
 
 
 
 
 
 
 
 
 
 
Wyatt Alt, thanks for your response. 
We already ran these requests and have responce only from the first one. 
 
 
 
 
 
 
puppetdb=# select count(*) from fact_values where id not in (select distinct fact_value_id from facts); 
 
 
 
 
 count 
 
 
 
 
--- 
 
 
 
 
 42765 
 
 
 
 
(1 row)
 
 
 
 
 
 
 
 
 
 
 
 
 
puppetdb=# select count(*) from fact_paths where id not in (select path_id from fact_values); 
 
 
 
 
 count 
 
 
 
 
--- 
 
 
 
 
 0

Jira (PDB-1124) PuppetDB high CPU usage

2015-01-26 Thread Anton Fomenko (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anton Fomenko commented on  PDB-1124 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PuppetDB high CPU usage  
 
 
 
 
 
 
 
 
 
 
When we tried to solve this issue last time we fully removed KahaDB and scheduler directories (i think it was 19.01) and now we have no discarded directories at all (there was no of them as well). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-1120) PR (163): Allow puppetdb to be configure for masterless conf - Spredzy

2015-01-26 Thread gepetto-bot (JIRA)

Title: Message Title

gepetto-bot commented on PDB-1120

Re: PR (163): Allow puppetdb to be configure for masterless conf - Spredzy

kbarber commented:
@ajroetker we can't change the API on a non-major boundary. We'd need to create new classes or something and find some way to proxy from the old ones to the new ones to keep backwards compatibility. Having said that, we could almost start considering a 5.0 release at this point ... since we probably will need this for PDB 3.0.0 later on, however there is some complexity in just doing that right now - my concern is about the package naming really for the terminus, since that might introduce some lack of backwards compatibility with PDB 2.2.x. Maybe if this all gets too nasty we should cut a stable & master branch. This needs some more thought, and to be truly honest with you - introducing complexity like this right now is somewhat bad timing, due to the pressures we are under .
But I get what you are trying to say about naming, it does make some sense to create some differently named classes. Not sure if I like the term 'consumer' however, seems very generic, I'd just say 'puppet' or something like that, since thats what its trying to manage really.

Add Comment

This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)

--
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-1120) PR (163): Allow puppetdb to be configure for masterless conf - Spredzy

2015-01-26 Thread gepetto-bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1120 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PR (163): Allow puppetdb to be configure for masterless conf - Spredzy  
 
 
 
 
 
 
 
 
 
 
kbarber commented: 
@ajroetker so ... I'd shelve your idea in a ticket. I like it, its nice, but lets try and do it for a major release and when we have the time. Mark it as a 'fix for 5.0.0' or something like that, so we know exactly when it can be worked on. I think the naming problem here isn't terrible, and most people would be forgiving if they saw it. At least we know about it . 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-1130) mechanism to apply non-migration database operations across subsequent upgrades

2015-01-26 Thread Kenneth Barber (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1130 
 
 
 
  mechanism to apply non-migration database operations across subsequent upgrades  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Affects Version/s:
 
 PDB 2.2.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-1132) the events endpoint should not require a query

2015-01-26 Thread Kenneth Barber (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1132 
 
 
 
  the events endpoint should not require a query  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Affects Version/s:
 
 PDB 2.2.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (HI-328) Hiera does not detect interpolation recursion

2015-01-26 Thread Thomas Hallgren (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-328 
 
 
 
  Hiera does not detect interpolation recursion  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/01/26 3:31 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
Hiera data that contains this: 
 
 
 
 
 
 
foo: '%{hiera("bar")}' 
 
 
 
 
  
 
 
 
 
bar: '%{hiera("foo")}'
 
 
 
 
 
 
 
will result in:

Jira (PUP-3910) puppet agent: RUNTIME_ERROR during certificate creation

2015-01-26 Thread Wolfgang Hotwagner (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wolfgang Hotwagner created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3910 
 
 
 
  puppet agent: RUNTIME_ERROR during certificate creation  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.3 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Client 
 
 
 

Created:
 

 2015/01/26 3:53 AM 
 
 
 

Environment:
 
 
Linux: Debian Stable(Wheezy) amd64  Used Repository:  
 

Puppetlabs products deb http://apt.puppetlabs.com wheezy main deb-src http://apt.puppetlabs.com wheezy main
 
 
 

Puppetlabs dependencies deb http://apt.puppetlabs.com wheezy dependencies deb-src http://apt.puppetlabs.com wheezy dependencies
 
 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wolfgang Hotwagner

Jira (PUP-3911) Ignored included dependencies due to interpretation order

2015-01-26 Thread David Barbion (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Barbion created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3911 
 
 
 
  Ignored included dependencies due to interpretation order   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.6.2 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Language 
 
 
 

Created:
 

 2015/01/26 5:41 AM 
 
 
 

Environment:
 
 
RHEL6, 7 MacOs X 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 David Barbion 
 
 
 
 
 
 
 
 
 
 
Hello, 
We are massively using tags to provision servers (production and development) to restrict catalog to a sub-part. 
We found a strange behaviour when mixing the use of tags, include directive and definitions: 
 
 
 
 
 
 
  class do_not_ignore_me {

Jira (PUP-3911) Ignored included dependencies due to interpretation order

2015-01-26 Thread Mathieu BONIFACE (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mathieu BONIFACE updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3911 
 
 
 
  Ignored included dependencies due to interpretation order   
 
 
 
 
 
 
 
 
 

Change By:
 
 Mathieu BONIFACE 
 
 
 
 
 
 
 
 
 
 Hello,We are massively using tags to provision servers (production and development) to restrict catalog to a sub-part.We found a strange behaviour when mixing the use of tags, include directive and definitions:{code :puppet }  class do_not_ignore_me {notify { 'This message should always be displayed' :}  }  define foobar($message = '') {notify { $message :}include do_not_ignore_me  }  class foo {foobar { 'from_foo' : message => $name}  }  class bar {foobar { 'from_bar' : message => $name}  }  include foo  include bar{code}When we try to apply this catalog, using the following command:{code}puppet apply  foobar.pp --tags foo{code}we get this output:{code}Notice: Compiled catalog for my-wks in environment production in 0.03 secondsNotice: fooNotice: /Stage[main]/Foo/Foobar[from_foo]/Notify[foo]/message: defined 'message' as 'foo'Notice: This message should always be displayedNotice: /Stage[main]/Do_not_ignore_me/Notify[This message should always be displayed]/message: defined 'message' as 'This message should always be displayed'Notice: Finished catalog run in 0.05 seconds{code}And when we switch the last 2 lines, we get a different result, still with the same command:{code}Notice: Compiled catalog for my-wks in environment production in 0.03 secondsNotice: fooNotice: /Stage[main]/Foo/Foobar[from_foo]/Notify[foo]/message: defined 'message' as 'foo'Notice: Finished catalog run in 0.05 seconds{code}This bug is embarassing as only a little part of the large catalog is applied.Regards. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)

Jira (PUP-3911) Ignored included dependencies due to interpretation order

2015-01-26 Thread Mathieu BONIFACE (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mathieu BONIFACE updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3911 
 
 
 
  Ignored included dependencies due to interpretation order   
 
 
 
 
 
 
 
 
 

Change By:
 
 Mathieu BONIFACE 
 
 
 
 
 
 
 
 
 
 Hello,We are massively using tags to provision servers (production and development) to restrict catalog to a sub-part.We found a strange behaviour when mixing the use of tags, include directive and definitions:{code:puppet}  class do_not_ignore_me {notify { 'This message should always be displayed' :}  }  define foobar($message = '') {notify { $message :}include do_not_ignore_me  }  class foo {foobar { 'from_foo' : message => $name}  }  class bar {foobar { 'from_bar' : message => $name}  }  include foo  include bar{code}When we try to apply this catalog, using the following command:{code :shell }puppet apply  foobar.pp --tags foo{code}we get this output:{code}Notice: Compiled catalog for my-wks in environment production in 0.03 secondsNotice: fooNotice: /Stage[main]/Foo/Foobar[from_foo]/Notify[foo]/message: defined 'message' as 'foo'Notice: This message should always be displayedNotice: /Stage[main]/Do_not_ignore_me/Notify[This message should always be displayed]/message: defined 'message' as 'This message should always be displayed'Notice: Finished catalog run in 0.05 seconds{code}And when we switch the last 2 lines, we get a different result, still with the same command:{code}Notice: Compiled catalog for my-wks in environment production in 0.03 secondsNotice: fooNotice: /Stage[main]/Foo/Foobar[from_foo]/Notify[foo]/message: defined 'message' as 'foo'Notice: Finished catalog run in 0.05 seconds{code}This bug is embarassing as only a little part of the large catalog is applied.Regards. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)

Jira (PUP-2689) A node can't always collect its own exported resources

2015-01-26 Thread Iain Buclaw (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Iain Buclaw commented on  PUP-2689 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: A node can't always collect its own exported resources  
 
 
 
 
 
 
 
 
 
 
This seems to have caused a regression in my environment when upgrading from 3.5.1 to 3.6.2. 
 
 
 
 
 
 
node arthur { 
 
 
 
 
@notify { "I feel very depressed": 
 
 
 
 
tag => 'marvin' 
 
 
 
 
} 
 
 
 
 
Notify <| tag == 'arthur' |> 
 
 
 
 
}
 
 
 
 
 
 
 
Before upgrade, Arthur never saw the notification, now Arthur does. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

Jira (HI-328) Hiera does not detect interpolation recursion

2015-01-26 Thread Thomas Hallgren (JIRA)

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

 
 
 
 
 
 
 
 Hiera /  HI-328 
 
 
 
  Hiera does not detect interpolation recursion  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (HI-328) Hiera does not detect interpolation recursion

2015-01-26 Thread Thomas Hallgren (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-328 
 
 
 
  Hiera does not detect interpolation recursion  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Sprint:
 
 Language 2015-02-04 
 
 
 

Scrum Team:
 
 Language 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (HI-14) Allow access to structured data

2015-01-26 Thread Thomas Hallgren (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-14 
 
 
 
  Allow access to structured data  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Sprint:
 
 Language 2015-02-04 
 
 
 

Scrum Team:
 
 Language 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

1 2 >

1 - 100 of 184 matches

Mail list logo