SSL works fine, I'm just having real issues with Foreman reports at the moment. The ruby file exists, the rack server is running, foreman works fine (apart from reporting) and so does puppet but the puppet reporting into Foreman is broken and it appears to be an issues with Puppet rather than Foreman.
The issue that we had was that the manifest that ensures puppet is centrally configured had "ensure => latest" and therefore the client updated on all nodes, the server didn't and everything broke. It's taken me the best part of a day to make sure that it is all working again correctly. We've learnt a lesson from this: * Don't use ensure=>latest unless you have complete control over the packages that will be installed. I am concerned that Epel jumped a major version that enforced so many major changes, but I guess that's our fault for trusting that things would stay the same! :P Kind regards, Matt On 4 March 2010 19:55, Douglas Garstang <[email protected]> wrote: > All I can is Ugh. > > I'm avoiding 0.25 like the plague. The last time I tried to use it, I > simply couldn't the SSL keys to work, and from what I read, others did > too. Were those problems fixed? > > Doug. > > On Thu, Mar 4, 2010 at 11:36 AM, Nigel Kersten <[email protected]> wrote: >> On Thu, Mar 4, 2010 at 11:27 AM, Douglas Garstang >> <[email protected]> wrote: >>> Does anyone know where I can get the puppet 0.24.8 RPM? We had been >>> getting it from the public EPEL Repo, but it looks like they just >>> decided to upgrade the version in their repository to 0.25.4. >>> >>> So... since our server is running 0.24.8, any other systems we install >>> from this point on end up getting 0.25 and then fail to talk to the >>> server. >>> >>> The clients come up with... >>> Could not retrieve catalog from remote server: Error 405 on SERVER: >>> Method Not Allowed >>> >>> I researched, and found out that this happens when the client is newer >>> than the server (or to be more specific the server is running 0.24.8 >>> and the client is running 0.25.4) >>> >>> To whoever decided not to make the client backward compatible, good one! >> >> Puppet clients are *never* backwards compatible across major versions. >> You always upgrade the server first. >> >> >> >> -- >> nigel >> >> -- >> 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. >> >> > > > > -- > Regards, > > Douglas Garstang > http://www.linkedin.com/in/garstang > Email: [email protected] > Cell: +1-805-340-5627 > > -- > 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. > > -- 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.
