http://projects.puppetlabs.com/issues/3238 is the issue I was thinking of, but 3693 is probably a duplicate of that.
These bugs have been open a really long time. Outside of lowering the MySQL timeout value, are there any workarounds for this problem? I can't really understand how Zynga can be managing as many hosts via Puppet as they do without being affected by a bug like this, unless they're not using stored configs (which would surprise me). -- Nathan Clemons http://www.livemocha.com The worlds largest online language learning community On Tue, May 24, 2011 at 2:42 PM, Todd Zullinger <t...@pobox.com> wrote: > treydock wrote: > > What is the current issue number? The only one I could find that > > mentions the same problem is this , > http://projects.puppetlabs.com/issues/7203. > > https://bugzilla.redhat.com/show_bug.cgi?id=572722 and > http://projects.puppetlabs.com/issues/3693 are both relevant here. > > I'd love to see a fix in either the rails activerecord component or in > puppet. Seeing that older puppet versions worked with the rails stack > in EPEL, it seems like it should be possible to make that work again > with some changes to puppet. > > -- > Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > It is strangely absurd to suppose that a million human beings > collected together are not under the same moral laws which bind them > separately. > -- Thomas Jefferson > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
