Puppet users - Jul 2010 - Massaging Puppet around parallel ruby installs hackery on CentOS 5.5

I''ve installed Puppet 0.25.5 and ruby-1.8.5 through the usual EPEL and
CentOS channels. However I also have a local built ruby-1.8.7
installed into /usr/local which keeps it somewhat separate from the
system ruby in /usr. It''s not ideal, but it does seem to work. 1.8.7
is for the rails, rack, passenger application running on these
servers.

My question is there a way to have Puppet gem install into 1.8.7 while
running on top 1.8.5? I''m testing with  package { "mysql":
provider =>
gem, ensure => "2.7", } and getting the error " Could not
match ruby
1.8.5 (2006-08-25) [x86_64-linux] Jul 20 15:59:02 webapp01
puppetd[4451]: (//application_rubygems/Package[mysql]) Failed to
retrieve current state of resource: Provider gem is not functional on
this platform"

I''m starting to suspect that I should either exec the gem installs or
remove ruby 1.8.5. I do think figuring out a clean way to do this
would be useful to me when it''s time to move to ruby 1.9.

Ramin K

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Jul 20, 2010, at 4:19 PM, Ramin K wrote:
> My question is there a way to have Puppet gem install into 1.8.7 while
> running on top 1.8.5? I''m testing with  package {
"mysql": provider =>
> gem, ensure => "2.7", } and getting the error " Could not
match ruby
> 1.8.5 (2006-08-25) [x86_64-linux] Jul 20 15:59:02 webapp01
> puppetd[4451]: (//application_rubygems/Package[mysql]) Failed to
> retrieve current state of resource: Provider gem is not functional on
> this platform"
These are determined at runtime by the PATH environment variable inherited by
the puppetd process, so if you manipulate the path in you startup scripts to put
/usr/local/bin/ first, this should work.


 - Eric Sorenson - N37 17.255 W121 55.738  - http://twitter.com/ahpook  -

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Jul 20, 4:25 pm, Eric Sorenson <eric.soren...@me.com>
wrote:
> On Jul 20, 2010, at 4:19 PM, Ramin K wrote:
>
> > My question is there a way to have Puppet gem install into 1.8.7 while
> > running on top 1.8.5? I''m testing with  package {
"mysql": provider =>
> > gem, ensure => "2.7", } and getting the error "
Could not match ruby
> > 1.8.5 (2006-08-25) [x86_64-linux] Jul 20 15:59:02 webapp01
> > puppetd[4451]: (//application_rubygems/Package[mysql]) Failed to
> > retrieve current state of resource: Provider gem is not functional on
> > this platform"
>
> These are determined at runtime by the PATH environment variable inherited
by the puppetd process, so if you manipulate the path in you startup scripts to
put /usr/local/bin/ first, this should work.
>
Thanks, you got me pointed in the right direction. This ticket
http://projects.reductivelabs.com/issues/1893 makes me think that you
need to specify any additions to your path in the puppet.conf. I tried
mucking with PATH variables in other places, but Puppet never picked
up the additions.

Ramin K

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.