Marcin Deranek

  • Email:
  • Registered on: 07/23/2008
  • Last connection: 12/07/2011

Projects

  • Puppet (Reporter, 12/07/2011)

Activity

Reported issues: 3

11/29/2011

06:21 am Puppet Bug #9084: Mixing and matching ruby versions for puppetmasterd and puppetd causes a "certificate ...
Try:...

09/05/2011

12:37 am Puppet Feature #6104: Client reports should be filterable at the client
More details are in https://support.puppetlabs.com/requests/236 As far as I can see measurements were done with Puppe...

09/30/2010

01:09 pm Puppet Bug #4532: agent doesn't open it's listen socket before finishing the first run
As far as I can see (I'm using 0.25.5) this also affects currently supported 0.25.x branch. Can this be fixed for 0.2...

08/24/2010

09:20 am Puppet Bug #4589: puppet 0.25.5 slower on 2+ run
Just to be clear. I've seen this problem on a production recipe (mixed resources). After running puppet with summariz...
09:02 am Puppet Bug #4589: puppet 0.25.5 slower on 2+ run
This is with stored config turned off:
Tue Aug 24 09:52:13 +0200 2010 Puppet (notice): Starting Puppet client ...

08/23/2010

03:53 pm Puppet Bug #4589 (Needs More Information): puppet 0.25.5 slower on 2+ run
While migrating to puppet 0.25.5 we discovered that puppet is getting slower on every 2+ run by ~30%. All that extra ...

07/15/2010

02:45 pm Puppet Bug #4139: 'autoflush' ... doesn't
I see similar behavior on CentOS5 x86_64 / puppet 0.25.5 / passenger 2.2.15 / REE 1.8.7 2010.02 although not exactly ...

06/03/2010

10:18 am Puppet Bug #3938 (Rejected): cron resource unreliable
Currently we had an accident with cron resource object. One night non-puppet maintained cronjobs (puppet maintained "...

05/18/2010

02:30 pm Puppet Bug #2462: cron resources default behaviour with no periods seems potentially dangerous
I believe this is more about documenting default behavior when user does not specify any schedule. There are some got...

05/04/2009

02:13 pm Puppet Bug #1056: Pluginsync/factsync checksums are getting stored in the state file
> This has been fixed since, apparently, at least 0.24.6. I don't know why the ticket's still open.
Had spoken to...

Also available in: Atom