search

blt04 / puppet-rvm

A puppet module for installing and using RVM (Ruby Version Manager)
Other
242 stars 280 forks source link

rvm_gem isn't working #53

Closed EslamElHusseiny closed 11 years ago

EslamElHusseiny commented 11 years ago

Hi, i'm testing puppet-rvm module using vagrant

i added "puppet.options = [ "--pluginsync" ] " in Vagrantfile i'm using rvm module as following : include rvm

rvm_system_ruby {'ruby-1.9.3-p194': ensure => present, default_use => false, }

rvm_gemset { 'ruby-1.9.3-p194@labsweb': ensure => present, ruby_version => 'ruby-1.9.3-p194', require => Rvm_system_ruby['ruby-1.9.3-p194'], }

rvm_gem{'ruby-1.9.3-p194@labsweb/bundler': ensure => latest, require => Rvm_gemset['ruby-1.9.3-p194@labsweb'], ruby_version => 'ruby-1.9.3-p194@labsweb', }

vagrant output : notice: /Stage[rvm-install]/Rvm::Dependencies::Ubuntu/Package[build-essential]/ensure: ensure changed 'purged' to 'present' notice: /Stage[rvm-install]/Rvm::Dependencies::Ubuntu/Package[libxslt1-dev]/ensure: ensure changed 'purged' to 'present' notice: /Stage[rvm-install]/Rvm::Dependencies::Ubuntu/Package[libsqlite3-dev]/ensure: ensure changed 'purged' to 'present' notice: /Stage[rvm-install]/Rvm::Dependencies::Ubuntu/Package[sqlite3]/ensure: ensure changed 'purged' to 'present' notice: /Stage[rvm-install]/Rvm::Dependencies::Ubuntu/Package[libyaml-dev]/ensure: ensure changed 'purged' to 'present' notice: /Stage[rvm-install]/Rvm::Dependencies::Ubuntu/Package[curl]/ensure: ensure changed 'purged' to 'present' notice: /Stage[rvm-install]/Rvm::Dependencies::Ubuntu/Package[git-core]/ensure: ensure changed 'purged' to 'present' notice: /Stage[rvm-install]/Rvm::Dependencies::Ubuntu/Package[autoconf]/ensure: ensure changed 'purged' to 'present' notice: /Stage[rvm-install]/Rvm::Dependencies::Ubuntu/Package[bison]/ensure: ensure changed 'purged' to 'present' notice: /Stage[rvm-install]/Rvm::System/Exec[system-rvm]/returns: executed successfully notice: /Stage[main]//Node[precise64]/Rvm_system_ruby[ruby-1.9.3-p194]/ensure: created notice: /Stage[main]//Node[precise64]/Rvm_gemset[ruby-1.9.3-p194@labsweb]/ensure: created notice: Finished catalog run in 282.39 seconds

inside vagrant box : vagrant@precise64:~$ ls /usr/local/rvm/gems/ruby-1.9.3-p194@labsweb/ bin vagrant@precise64:~$ ls /usr/local/rvm/gems/ruby-1.9.3-p194@global/ bin cache doc gems specifications vagrant@precise64:~$ ls /usr/local/rvm/gems/ruby-1.9.3-p194 specifications

any ideas why this happens ?

Thanks in advance

blt04 commented 11 years ago

I'm not sure I understand the question.

Are you are asking why bundler is installed in the global gemset rather than the labsweb gemset? If so: RVM now automatically installs certain gems in the global gemset for each ruby. These gems are controlled via rvm/gemsets/global.gems. Bundler is one of these gems. Since bundler is installed in the global gemset, it is available in the labsweb gemset and thus not explicitly installed in that gemset.

Does this help?

EslamElHusseiny commented 11 years ago

problem fixed by running puppet twice instead of once