We’re on RedHat 5.5, and using release 0.10.4 of the chef client. It’s possible that with further fooling around we could have gotten chef to work with the 1.8.7 version of ruby, but our patience for that was limited given that we had other reasons for wanting ruby 1.9.
From: Kyle Bader [mailto:email@example.com]
Sent: Thursday, February 23, 2012 7:43 AM
Subject: [chef] Re: RE: Ruby for Chef
I’m curious about the debain ssh issue your bumping into. Squeeze works for us, as does knife ssh. What release are you running?
On Feb 22, 2012 7:31 AM, “Stroomer, Jeff” <Jeff.Stroomer@disney.commailto:Jeff.Stroomer@disney.com> wrote:
We’re running chef using ruby 1.9.2p290, though I myself didn’t compile ruby from source. Works well. In fact, we found we couldn’t get chef to work with ruby 1.8.7 because of ssh bugs. Don’t know what would happen if you used an even newer ruby.
From: Van Fossan,Randy [mailto:firstname.lastname@example.org:email@example.com]
Sent: Wednesday, February 22, 2012 7:59 AM
Subject: [chef] Ruby for Chef
Two questions for my fellow chef’s…
Has anyone used Ruby 1.9.3-pxxx ? We have a requirement of at least 1.9.2-p290.
Also, in compiling ruby from source, I find a lot of conflicting information on the web. What do I actually need to support Chef Server and Chef clients?
Currently, I am running a mix of SuSe 10, 11 and CentOS 5.x, 6.x and some RedHat 5.x. I am concentrating on CentOS 5.x and 6.x. I found the following on web and am trying it. However, I don’t want to discover any gotchas’ down the road.
I have tried the RBEL repo version of Ruby-1.9.2-p290 RPM but it doesn’t install correctly. I have compiled Ruby-1.9.2-p290 from source several times and it seems to work, but, I’ve been bitten before.
Anyone have any recommendations. Remember, I have to run at least 1.9.2-p290.