- From: JD Harrington <
- Subject: [chef] Re: Re: Re: Omnibus and RVM
- Date: Mon, 4 Mar 2013 13:36:37 -0500
Vagrant is packaged similarly to Chef and seems to get around these
issues by making sure to explicitly set GEM_HOME, GEM_PATH, etc in its
executable wrapper script.
On Mon, Mar 4, 2013 at 12:37 PM, Joseph Bowman
> 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
>> 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,
>>> 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
>>> RVM's gems everything worked again.
>>> Is this a known issue or does anyone know how to make Omnibus and RVM
>>> We are running on RHEL 6.3 with Chef 10.16.0.
Archive powered by MHonArc 2.6.16.