Bug#509566:

2009-01-08 Thread Thijs Kinkhorst
severity 509566 normal thanks > found 509566 0.24.5-3 > found 509566 0.24.6-1 > thanks > Setting waitforcert to "5" helps a bit, but it is still a problem IMO. Your suggestions are all very valid in my opinion, but I think that the uploaded fix has made the issue not grave anymore. I hope the Pu

Bug#509566: Puppet: setting timeout to 0 causes puppet to try requesting a certificate infinitely often

2009-01-07 Thread Faidon Liambotis
found 509566 0.24.5-3 found 509566 0.24.6-1 thanks Hi, Setting waitforcert to "5" helps a bit, but it is still a problem IMO. Actually, I think the bug lies in the code, and not in the configuration. The manpage mentions "You can turn off waiting for certificates by specifying a time of 0." a

Bug#509566: marked as done (Puppet: setting timeout to 0 causes puppet to try requesting a certificate infinitely often)

2009-01-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Jan 2009 20:32:17 + with message-id and subject line Bug#509566: fixed in puppet 0.24.5-3 has caused the Debian Bug report #509566, regarding Puppet: setting timeout to 0 causes puppet to try requesting a certificate infinitely often to be marked as done. This

Bug#509566: Puppet: setting timeout to 0 causes puppet to try requesting a certificate infinitely often

2009-01-07 Thread Faidon Liambotis
severity 509566 grave thanks Besides having autosign disabled on the master or not having network at all, the problem can be manifested with installing the package on a random on a random network. Let me repeat this: executing apt-get install puppet on *any* random system, without any pri