The difference in ruby-libs is my guess as well. However, and I forgot to mention this in my previous posts, if I remove about 5 files from the template (just comment lines) then it is just fine. The ruby code in the template executes correctly from the output I see (in the failed config), and running erb against the original 106 line template on the RHEL4 machine produces the expected results.
It seems the length of the template has an effect on the results for some reason... Rob Evan Hisey wrote: > On Wed, Oct 8, 2008 at 12:42 PM, Robert Rati <[EMAIL PROTECTED]> wrote: >> I have puppetmaster running on RHEL4, and 2 puppet clients running on >> RHEL5. All machines are running puppet version is 24.4 installed from >> EPEL. The issue is that some configurations seem to be unusable by the >> RHEL5 clients when the puppetmaster is running on RHEL4. However, if I >> put those same configs on the RHEL5 system (serving a RHEL5 client) or >> an F8 setup (client/server) there is no problem. In the logs on the >> client, I see: >> >> puppetd[10104]: Facts have changed; recompiling >> puppetd[10104]: Configuration could not be translated from yaml; using >> cached catalog >> >> Every time the client talks to the RHEL4 server, it thinks the facts >> have changed and need to be recompiled, and the configuration isn't >> usable by the client. >> >> Some of the configuration being pulled down are flat configuration >> files, whereas some are templates. Most of the templates seem to be >> fine as do the flat files, but I have one template that I know causes >> this issue. Is there a way to preserve the configuration the client is >> receiving from the server? I've tried running puppet -vdto, but it >> didn't give me any information I didn't already have. Any other debug tips? >> > Just off the top of my head, I would start by looking at the versions > of ruby and ruby ERB. Both FC8 and RHEL5 use newer versions of a lot > of libraries than RHEL4. This may very well cause the templates to be > parsed different enough between version to cause problems like this, > i.e: working when parsed by the newer libs, but not when parsed by the > older libs. > > Evan > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
