Installing RVM breaks puppet on target system

[joerx]

After installing RVM and creating a gemset provisioning my Vagrant box won't work anymore for the relatively obvious reason that the new system ruby won't have the puppet gem installed. Simple workaround is to add puppet as a gem to any gemset on the box.

Haven't found anything about this in the docs or FAQ so I'm not sure if this is an issue or not. Given the nature of the problem, I'd expect that to be a pretty common problem. Shouldn't it at least be mentioned in the FAQ or something?

[brettporter]

How are you running puppet - via vagrant provision, or at the command line?

[joerx]

Vagrant provisioning. Not sure why this breaks, as Vagrant is explicitely using a different version of Ruby/Gems than the one installed by RVM. Probably should go upstream with this?

[brettporter]

Yes, that'd make sense. FWIW, I haven't had the same problem.

[mikebell]

I'm having a similar problem here:

/opt/ruby/lib/ruby/1.9.1/rubygems/dependency.rb:247:in `to_specs': Could not find puppet (>= 0) amongst [bigdecimal-1.1.0, bundler-1.3.5, bundler-unload-1.0.2, executable-hooks-1.2.6, gem-wrappers-1.2.1, io-console-0.3, json-1.5.5, minitest-2.5.1, rake-0.9.2.2, rdoc-3.9.5, rubygems-bundler-1.4.2, rvm-1.11.3.8] (Gem::LoadError)

My manifest looks like:

class { 'rvm': version => '1.25.7' }

rvm::system_user { vagrant: }

rvm_system_ruby {
  'ruby-1.9.3-p484':
  ensure => 'present',
  default_use => true;
}

rvm_gemset {
  "ruby-1.9.3-p484@drupal":
  ensure => present,
  require => Rvm_system_ruby['ruby-1.9.3-p484'];
}

rvm_gem {
  'ruby-1.9.3-p484@drupal/compass':
  ensure => '0.12.2',
  require => Rvm_gemset['ruby-1.9.3-p484@drupal'];
}

rvm_gem {
  'ruby-1.9.3-p484@drupal/bundler':
  ensure => '1.5.1',
  require => Rvm_gemset['ruby-1.9.3-p484@drupal'];
}

rvm_gem {
  'ruby-1.9.3-p484@drupal/puppet':
  ensure => '3.1.1',
  require => Rvm_gemset['ruby-1.9.3-p484@drupal'];
}

If I ssh into the box and set the vagrant user to use the drupal gemset I can see that puppet is installed but using vagrant provision outside of the box fails with the above message.