[chef] Re: Re: Omnibus and RVM

Chronological Thread 
  • From: Joseph Bowman < >
  • To:
  • Subject: [chef] Re: Re: Omnibus and RVM
  • Date: Mon, 4 Mar 2013 12:37:45 -0500

To be specific, rvm installs an rvm.sh in /etc/profile.d which is likely your culprit. You may be able to do something as simple as set up an alias for chef-client to null out that environment variable. 

On Mon, Mar 4, 2013 at 12:34 PM, Ranjib Dey < " target="_blank"> > wrote:

Check your GEM-PATH environment variable. Various systems rvm/rbenv/vagrant sets it explicitly. So even the omnibus che-client picks up the wrong gems. Check your /etc/profile.d

On Mar 4, 2013 6:34 AM, < " target="_blank"> > wrote:
Hi everyone,

We have several chef-clients setup using the omnibus installer and after
installing RVM onto the system all of the chef clients began to fail. They all
mentioned that they could not find the chef gem. We soon realized they were all
looking in RVM's gem set rather then their own. After installing chef into
RVM's gems everything worked again.

Is this a known issue or does anyone know how to make Omnibus and RVM work

We are running on RHEL 6.3 with Chef 10.16.0.

Archive powered by MHonArc 2.6.16.