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
together?
We are running on RHEL 6.3 with Chef 10.16.0.
I don't understand the question, sorry.
Omnibus is a full-stack installation - it brings ruby, and everything else
above libc, along for the ride in the package itself. So it's completely
incompatible with RVM by definition.
If you want to try using Chef and RVM, the way to do that is to just
install the Chef gem inside of RVM - at which point, you don't need the
omnibus installer at all, perhaps.
Best,
Adam
On 3/4/13 6:34 AM, "bryan.baugher@cerner.com" bryan.baugher@cerner.com
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
together?We are running on RHEL 6.3 with Chef 10.16.0.
On Monday, March 4, 2013 at 9:10 AM, Adam Jacob wrote:
I don't understand the question, sorry.
Omnibus is a full-stack installation - it brings ruby, and everything else
above libc, along for the ride in the package itself. So it's completely
incompatible with RVM by definition.If you want to try using Chef and RVM, the way to do that is to just
install the Chef gem inside of RVM - at which point, you don't need the
omnibus installer at all, perhaps.Best,
Adam
I think he wants omnibus for chef things and RVM for other stuff. What happens in that case is the environment variables from rvm point omnibus' ruby at the rvm install. There's an open bug about this.
--
Daniel DeLeo
rbenv is messing up pathing/environment settings and chef is getting confused.
I'd try the rbenv cookbook for now until this bug gets squished.
-s
On Mon, Mar 4, 2013 at 9:34 AM, bryan.baugher@cerner.com 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
together?We are running on RHEL 6.3 with Chef 10.16.0.
Yes this is what we are trying to do. I should have looked in your JIRA first. I think I found the issue here[1].
[1] - http://tickets.opscode.com/browse/CHEF-3581
From: Daniel DeLeo <dan@kallistec.commailto:dan@kallistec.com>
Reply-To: "chef@lists.opscode.commailto:chef@lists.opscode.com" <chef@lists.opscode.commailto:chef@lists.opscode.com>
Date: Monday, March 4, 2013 11:12 AM
To: "chef@lists.opscode.commailto:chef@lists.opscode.com" <chef@lists.opscode.commailto:chef@lists.opscode.com>
Subject: [chef] Re: Re: Omnibus and RVM
On Monday, March 4, 2013 at 9:10 AM, Adam Jacob wrote:
I don’t understand the question, sorry.
Omnibus is a full-stack installation - it brings ruby, and everything else
above libc, along for the ride in the package itself. So it’s completely
incompatible with RVM by definition.
If you want to try using Chef and RVM, the way to do that is to just
install the Chef gem inside of RVM - at which point, you don’t need the
omnibus installer at all, perhaps.
Best,
Adam
I think he wants omnibus for chef things and RVM for other stuff. What happens in that case is the environment variables from rvm point omnibus’ ruby at the rvm install. There’s an open bug about this.
–
Daniel DeLeo
CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner’s corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
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, bryan.baugher@cerner.com 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
together?We are running on RHEL 6.3 with Chef 10.16.0.
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 dey.ranjib@gmail.com 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, bryan.baugher@cerner.com 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
together?We are running on RHEL 6.3 with Chef 10.16.0.
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 bowman.joseph@gmail.com wrote:
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 dey.ranjib@gmail.com 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.dOn Mar 4, 2013 6:34 AM, bryan.baugher@cerner.com 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
together?We are running on RHEL 6.3 with Chef 10.16.0.