date:20150130

Jira (PUP-3929) Creating a file called /etc/facter causes an error in facter which makes puppet agent not run

2015-01-30 Thread Nick Walker (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walker created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3929 
 
 
 
  Creating a file called /etc/facter causes an error in facter which makes puppet agent not run  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.3 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/01/30 9:06 AM 
 
 
 

Labels:
 

 tcse support 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Nick Walker 
 
 
 
 
 
 
 
 
 
 
Steps to repro in PE3.7: 
 
 
 
 
 
 
[root@master371-centos ~]# puppet --version 
 
 
 
 
3.7.3 (Puppet Enterprise 3.7.1)

Jira (HI-46) Hiera should support alternate environments

2015-01-30 Thread Brett Swift (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brett Swift commented on  HI-46 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Hiera should support alternate environments  
 
 
 
 
 
 
 
 
 
 
I thought I'd mention this is a dependency of an r10k feature as well:  https://github.com/puppetlabs/r10k/issues/195 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1200) Investigate f20 acceptance test failures

2015-01-30 Thread Kenneth Barber (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1200 
 
 
 
  Investigate f20 acceptance test failures  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Fix Version/s:
 
 PDB2.3.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (PUP-1191) Puppet should not reset locale

2015-01-30 Thread Mike Arnold (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mike Arnold commented on  PUP-1191 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Puppet should not reset locale  
 
 
 
 
 
 
 
 
 
 
Ubuntu 14.04 seems to be immune to this issue. I did not need to use this hack to get an initial UTF-8 encoding. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (PUP-3453) Allow to debug yum installation

2015-01-30 Thread Frederic Conrotte (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frederic Conrotte commented on  PUP-3453 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Allow to debug yum installation   
 
 
 
 
 
 
 
 
 
 
This is exactly what I want as well. 
When you do puppet apply --debug, you expect the run command to enable full debug logging: yum -d 10 -e 10 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-298) Update FS layout for hiera

2015-01-30 Thread Kurt Wall (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall assigned an issue to Kurt Wall 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Hiera /  HI-298 
 
 
 
  Update FS layout for hiera  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

Assignee:
 
 KurtWall 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (PUP-3932) If you name a class with ttyS or tty_S in the name, then you get Error: Could not find class

2015-01-30 Thread Henrik Lindberg (JIRA)

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


 
 
 
 
 
 
 Puppet /  PUP-3932 
 
 
 
  If you name a class with ttyS or tty_S in the name, then you get Error: Could not find class  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 EricSorenson DuncanMcNaught 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (PUP-3932) If you name a class with ttyS or tty_S in the name, then you get Error: Could not find class

2015-01-30 Thread Henrik Lindberg (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-3932 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: If you name a class with ttyS or tty_S in the name, then you get Error: Could not find class  
 
 
 
 
 
 
 
 
 
 
Can you describe how to reproduce? Just doing this: 
 
 
 
 
 
 
class tty_S { 
 
 
 
 
} 
 
 
 
 
include tty_S
 
 
 
 
 
 
 
Works on both master (i.e. 4.0.0) and stable (i.e. 3.7.5) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1210) PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger

2015-01-30 Thread Wyatt Alt (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1210 
 
 
 
  PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/01/30 2:29 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
This is encountered by the PE-7392 folks in a number of places, notably on host 202, though not during the timeperiod that the ticket itself is concerned with. 
 
 
 
 
 
 
2014-11-20 11:09:06,169 ERROR [c.p.p.command] [b8922a1d-46ff-4272-a53d-26737001d968] [replace facts] Retrying after attempt 4, due to: org.postgresql.util.PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger. Use setObject() with an explicit Types value to specify the type to use. 
 
 
 
 
org.postgresql.util.PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger. Use setObject() with an explicit Types value to specify the type to use.

Jira (PDB-1211) slow processing of reports

2015-01-30 Thread Wyatt Alt (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1211 
 
 
 
  slow processing of reports  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 ThePE-7392customerhadreportsenabledforapproximatelyanhour,andduringthathourmorecatalogsandfactswereprocessedthanreports.Forhost203thefirstreportwasprocessedat10:52:14on1/5andthelastat11:57:55onthesameday.Reportswereenabledatapproximately10:50,sothedelaytothefirstprocessedisnotsuperlong.Duringthistimeperiodthereweresignificantlyfewerreportsprocessedthancatalogsandfacts:{code}[~/nextdrive/bookings/logs203]$grepstorereport203-reports-enabled.log|wc-l2693[~/nextdrive/bookings/logs203]$grepreplacecatalog203-reports-enabled.log|wc-l3814[~/nextdrive/bookings/logs203]$grepreplacefacts203-reports-enabled.log|wc-l4065[~/nextdrive/bookings/logs203]$grepstorereport203-reports-enabled.log|wc-l2693{code}Thesameistrueofhost202:{code}[~/nextdrive/bookings/ logs203 logs202 ]$grep storereport replacefacts  203 202 -reports-enabled.log|wc-l 2693 4599 [~/nextdrive/bookings/ logs203 logs202 ]$grepreplacecatalog 203 202 -reports-enabled.log|wc-l 3814 4140 [~/nextdrive/bookings/ logs203 logs202 ]$grep replacefacts203-reports-enabled.log|wc-l4065[~/nextdrive/bookings/logs203]$grep storereport 203 202 -reports-enabled.log|wc-l 2693 2703 {code}andacrosstheotherhosts.Weshouldreplicatethisandunderstandwhyithappens. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

Jira (PDB-1211) slow processing of reports

2015-01-30 Thread Wyatt Alt (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1211 
 
 
 
  slow processing of reports  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 ThePE-7392customerhadreportsenabledforapproximatelyanhour,andduringthathourmorecatalogsandfactswereprocessedthanreports.Forhost203thefirstreportwasprocessedat10:52:14on1/5andthelastat11:57:55onthesameday.Reportswereenabledatapproximately10:50,sothedelaytothefirstprocessedisnotsuperlong.Duringthistimeperiodthereweresignificantlyfewerreportsprocessedthancatalogsandfacts:{code}[~/nextdrive/bookings/logs203]$grep storereport203-reports-enabled.log|wc-l2693[~/nextdrive/bookings/logs203]$grep replacecatalog203-reports-enabled.log|wc-l3814[~/nextdrive/bookings/logs203]$grepreplacefacts203-reports-enabled.log|wc-l4065[~/nextdrive/bookings/logs203]$grepstorereport203-reports-enabled.log|wc-l2693{code}Thesameistrueofhost202:{code}[~/nextdrive/bookings/logs202]$grepreplacefacts202-reports-enabled.log|wc-l4599[~/nextdrive/bookings/logs202]$grepreplacecatalog202-reports-enabled.log|wc-l4140[~/nextdrive/bookings/logs202]$grepstorereport202-reports-enabled.log|wc-l2703{code}andacrosstheotherhosts.Weshouldreplicatethisandunderstandwhyithappens. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

Jira (PUP-3548) 4x function API's call_function cannot call a 3x function

2015-01-30 Thread Eric Thompson (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson commented on  PUP-3548 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: 4x function API's call_function cannot call a 3x function  
 
 
 
 
 
 
 
 
 
 
yeah, the absolute paths were confusing to me. with Henrik's help i verified on rhel7 at SHA: with: 
 
 
 
 
 
 
[root@eq8ntygsty42ut3 mymodule]# pwd 
 
 
 
 
/etc/puppet/environments/production/modules/mymodule 
 
 
 
 
[root@eq8ntygsty42ut3 mymodule]# tree 
 
 
 
 
. 
 
 
 
 
└── lib 
 
 
 
 
└── puppet 
 
 
 
 
├── functions 
 
 
 
 
│ ├── puts_useless4.rb 
 
 
 
 
│ ├── test_call_function3.rb 
 
 
 
 
│ └── test_call_function4.rb

Jira (PUP-3548) 4x function API's call_function cannot call a 3x function

2015-01-30 Thread Eric Thompson (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson commented on  PUP-3548 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: 4x function API's call_function cannot call a 3x function  
 
 
 
 
 
 
 
 
 
 
verified on ubuntu14.04 at SHA: 0f551b3 with: 
 
 
 
 
 
 
root@gchhjqakb4s5ewj:/etc/puppet/environments/production/modules/mymodule/lib/puppet#  puppet apply -e 'notice(test_call_function4(yargh))' 
 
 
 
 
in puppet4 function: yargh 
 
 
 
 
Notice: Scope(Class[main]): 
 
 
 
 
Notice: Compiled catalog for gchhjqakb4s5ewj.delivery.puppetlabs.net in environment production in 0.41 seconds 
 
 
 
 
Notice: Applied catalog in 0.02 seconds 
 
 
 
 
 
 
 
 
 
root@gchhjqakb4s5ewj:/etc/puppet/environments/production/modules/mymodule/lib/puppet# puppet apply -e 'notice(test_call_function3(yargh))' 
 
 
 
 
in a puppet3 function: yargh 
 
 
 
 
Notice: Scope(Class[main]): 
 
 
 
 
Notice: Compiled catalog for

Jira (PUP-3855) auth.conf no longer restricting based on environment

2015-01-30 Thread Christopher Price (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Price assigned an issue to Jeremy Barlow 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3855 
 
 
 
  auth.conf no longer restricting based on environment  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Price 
 
 
 

Assignee:
 
 JeremyBarlow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1124) PuppetDB high CPU usage

2015-01-30 Thread Wyatt Alt (JIRA)

Title: Message Title

Wyatt Alt commented on PDB-1124

Re: PuppetDB high CPU usage

Anton Fomenko Sorry for the delay. You might try disabling garbage collection on the slaves as a first action; they're all writing to the same database so they don't all need to be doing it. You can make this happening by setting gc-interval to a very long timeperiod.
For the puppetdb logs you sent it looks like the hosts numbered 2 and 6 have constant issues with ActiveMQ for most of duration of the logs provided. That's not normal and may be impeding performance; we'll have to look into what's causing it.
What kind of disks are your databases running on? Can you explain the reasoning behind your settings for random_page_cost and cpu_tuple_cost? Those can affect the queries chosen by the optimizer.
You may also experiment with raising work_mem, effective_cache_size, and shared_buffers. I have a general sense from your postgresql.conf that you're using less memory than you could be. Check out the advice https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server or see what pgtune says. Seems like it would be conservative to raise each those settings by a few multiples.
Those tweaks may help, but I doubt they'll resolve this issue. I think the problem is probably with the query you're pointing at. Would you be willing to share an export of your database, possibly anonymized? That would be super useful for getting this replicated and figuring out a fix. We have export and anonymization tools documented here:
https://docs.puppetlabs.com/puppetdb/latest/migrate.html https://docs.puppetlabs.com/puppetdb/latest/anonymization.html
Wyatt
P.S if you decide to give us data please share it with me via my company email, rather than in this ticket, which is visible to the public. My email is wy...@puppetlabs.com.

1 2 >

1 - 100 of 145 matches

Mail list logo