Puppet users - Jul 2012 - Puppet not "refreshing" its session (from Vagrant maybe)?

So I have added a config in Puppet to replace my OS''s old Ruby version
with
a newer one. Unfortunately, it seems that if I run vagrant provision again 
(which essentially does a puppet apply), Vagrant (or Puppet) reuses the 
same ssh session or bash shell or whatever it is. As such, for my 
configurations at least, Puppet keeps on trying to "re-install" the
newer
Ruby. How do I make it so that if I do "vagrant provision" it creates
a new
ssh session or bash shell (or whatever it is)? Because at the first run, 
Puppet will have completely and correctly installed the newer Ruby, and if 
I run puppet apply or vagrant provision, it should not rerun the install 
for the new Ruby.

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/nXDyqXCq4CwJ.
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.

This is also a big problem because I want to also install Rails and the 
default Ruby version on the OS won''t allow me to install that gem... as
such once thew newer version of Ruby is installed and Puppet tries to 
install Rails, it still complains about Rails requiring a higher Ruby 
version (>=1.8.7).

On Friday, July 6, 2012 12:26:06 AM UTC-7, Benjamin Lei
wrote:
>
> So I have added a config in Puppet to replace my OS''s old Ruby
version
> with a newer one. Unfortunately, it seems that if I run vagrant provision 
> again (which essentially does a puppet apply), Vagrant (or Puppet) reuses 
> the same ssh session or bash shell or whatever it is. As such, for my 
> configurations at least, Puppet keeps on trying to "re-install"
the newer
> Ruby. How do I make it so that if I do "vagrant provision" it
creates a new
> ssh session or bash shell (or whatever it is)? Because at the first run, 
> Puppet will have completely and correctly installed the newer Ruby, and if 
> I run puppet apply or vagrant provision, it should not rerun the install 
> for the new Ruby.
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/oog82o5hx0kJ.
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.

Hi,

On 07/06/2012 09:26 AM, Benjamin Lei wrote:
> So I have added a config in Puppet to replace my OS''s old Ruby
version
> with a newer one. Unfortunately, it seems that if I run vagrant
> provision again (which essentially does a puppet apply), Vagrant (or
> Puppet) reuses the same ssh session or bash shell or whatever it is. As
> such, for my configurations at least, Puppet keeps on trying to
> "re-install" the newer Ruby. How do I make it so that if I do
"vagrant
> provision" it creates a new ssh session or bash shell (or whatever it
> is)? Because at the first run, Puppet will have completely and correctly
> installed the newer Ruby, and if I run puppet apply or vagrant
> provision, it should not rerun the install for the new Ruby.
you shouldn''t be so dismissive about your process hierarchy.
It''s not a
"bash shell or whatever", but a succinct problem specific to your
software setup. Point in fact, without knowing your whole setup, I can
only guess what''s going on. The only one who can make sure is yourself.

I''m just going to assume that you use puppet with its "agent"
model,
i.e. regular puppet runs are not done via cronjob. That implies that
there is one ruby process that performs regular puppet runs. In order to
make puppet switch to a newly installed ruby version, you''d have to
restart this ruby process.

There has been a thread on the dos and don''ts of restarting puppet via
puppet on the list recently, that should get you going.
If this doesn''t help at all, more details on your puppet installation
would be appreciated.

HTH,
Felix

-- 
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.