Skip to content
This repository has been archived by the owner on Feb 1, 2022. It is now read-only.

Could not find a suitable provider for rvm_system_ruby #2830

Open
Den787 opened this issue Dec 13, 2018 · 21 comments
Open

Could not find a suitable provider for rvm_system_ruby #2830

Den787 opened this issue Dec 13, 2018 · 21 comments

Comments

@Den787
Copy link

Den787 commented Dec 13, 2018

I can not build, Ruby settings did not change

Error: Could not find a suitable provider for rvm_system_ruby
Error: Could not find a suitable provider for rvm_gem

@specialfae
Copy link

Probably related to #2795 and #2066

I'm experiencing a similar issue

@Ardakilic
Copy link

+1 , can confirm I'm having the same issue. I also disabled ruby from PuPHPet, but I keep getting this:

==> sandbox: Error: 'curl -fsSL https://get.rvm.io | bash -s -- --version latest' returned 2 instead of one of [0]
==> sandbox: Error: /Stage[main]/Rvm::System/Exec[system-rvm]/returns: change from 'notrun' to ['0'] failed: 'curl -fsSL https://get.rvm.io | bash -s -- --version latest' returned 2 instead of one of [0]
==> sandbox: Notice: /Stage[main]/Puphpet::Ruby/Exec[rvm rvmrc warning ignore all.rvmrcs]: Dependency Exec[system-rvm] has failures: true
==> sandbox: Warning: /Stage[main]/Puphpet::Ruby/Exec[rvm rvmrc warning ignore all.rvmrcs]: Skipping because of failed dependencies

Any solutions ?

@Den787
Copy link
Author

Den787 commented Dec 14, 2018

@Ardakilic
I did not find a solution, but I ignored these errors so far and manually think about installing ROR

@Ardakilic
Copy link

@Den787 Does it work when you ignore the issue and go on like it installed successfully ? To be honest I don't have a need for ruby on this virtual machine at all, but it tries to install nevertheless.

@Den787
Copy link
Author

Den787 commented Dec 14, 2018

@Ardakilic
I just started learning, but in yii2 -> mysql + php works fine. I have not seen any problems yet.

@kyriog
Copy link

kyriog commented Dec 14, 2018

I have the same problem and I found a workaround.
ruby/rvm installation is now signed, but the signature key seems not to be downloaded during installation (or signature key may have changed).

You can finish the installation using this workaround:

After your failed vagrant up, connect by SSH to your VM, then login as root:

vagrant ssh
sudo -i

Then you'll have to add Ruby signature keys. The command is provided in the Puppet error log, which for me is currently:

gpg --keyserver hkp://keys.gnupg.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 7D2BAF1CF37B13E2069D6956105BD0E739499BDB

You can now logout your VM and run a vagrant provision and it'll finish the creation process.

NB: Running sudo -i then gpg --recv-keys is different from runing sudo gpg --recv-keys, because the first one will install the GPG key to root keychain (which is the user used by puppet), as the second one will only install the key in vagrant keychain.

@Ardakilic
Copy link

@kyriog Can confirm your workaround works nicely. Thanks!

@kyriog
Copy link

kyriog commented Dec 14, 2018

I opened an issue to maestrodev/puppet-rvm (which seems to be used by puphpet) to ask them to update rvm signature key.

I found an other workaround which does not need a "two-step configuration":
Edit puphpet/puppet/modules/puphpet/manifests/ruby.pp and locate the gnupg_key part (lines 16-22):

  gnupg_key { "rvm_${::rvm::params::gnupg_key_id}":
    ensure     => present,
    key_id     => $::rvm::params::gnupg_key_id,
    user       => 'root',
    key_source => 'https://rvm.io/mpapis.asc',
    key_type   => public,
  }

Right after this block (but before the -> class { '::rvm:' part, add:

  gnupg_key { "rvm_pkuczynski":
    ensure     => present,
    key_id     => '7D2BAF1C',
    user       => 'root',
    key_source => 'https://rvm.io/pkuczynski.asc',
    key_type   => public,
  }

You can now run a fresh vagrant up without any problem!

@Axel29
Copy link

Axel29 commented Dec 23, 2018

I opened an issue to maestrodev/puppet-rvm (which seems to be used by puphpet) to ask them to update rvm signature key.

I found an other workaround which does not need a "two-step configuration":
Edit puphpet/puppet/modules/puphpet/manifests/ruby.pp and locate the gnupg_key part (lines 16-22):

  gnupg_key { "rvm_${::rvm::params::gnupg_key_id}":
    ensure     => present,
    key_id     => $::rvm::params::gnupg_key_id,
    user       => 'root',
    key_source => 'https://rvm.io/mpapis.asc',
    key_type   => public,
  }

Right after this block (but before the -> class { '::rvm:' part, add:

  gnupg_key { "rvm_pkuczynski":
    ensure     => present,
    key_id     => '7D2BAF1C',
    user       => 'root',
    key_source => 'https://rvm.io/pkuczynski.asc',
    key_type   => public,
  }

You can now run a fresh vagrant up without any problem!

That worked for me, thanks a lot, no other solution did (going on vagrant SSH, running the curl call to get rvm etc.)!

@PWalkow
Copy link

PWalkow commented Apr 30, 2019

Should it be merged into the master branch to avoid these issues in the future?

@fnagel
Copy link

fnagel commented May 3, 2019

@jtreminio Any chance to merge this? Running in this again and again and again...

@tlartaud
Copy link

tlartaud commented May 3, 2019

Same here :-(

Did not try yet, but it looks like there's a new key

  gnupg_key { 'rvm_pkuczynski':
    ensure     => present,
    key_id     => '39499BDB',
    user       => 'root',
    key_source => 'https://rvm.io/pkuczynski.asc',
    key_type   => public,
  }

@justpie
Copy link

justpie commented May 15, 2019

I''ve tried adding in both the workarounds provided by @kyriog and @tlartaud

However, I'm running into the following error with vagrant up

Any ideas?

==> auxmktdevdining: Error: Could not update: Execution of '/usr/local/rvm/bin/rvm 2.4 do gem install -v 1.2.1 --no-rdoc --no-ri deep_merge' returned 1: ERROR:  While executing gem ... (OptionParser::InvalidOption)
==> auxmktdevdining:     invalid option: --no-rdoc
==> auxmktdevdining: Error: /Stage[main]/Puphpet::Ruby/Puphpet::Ruby::Install[ruby1]/Rvm_gem[deep_merge for Ruby 2.4]/ensure: change from 'absent' to '1.2.1' failed: Could not update: Execution of '/usr/local/rvm/bin/rvm 2.4 do gem install -v 1.2.1 --no-rdoc --no-ri deep_merge' returned 1: ERROR:  While executing gem ... (OptionParser::InvalidOption)
==> auxmktdevdining:     invalid option: --no-rdoc
==> auxmktdevdining: Error: Could not update: Execution of '/usr/local/rvm/bin/rvm 2.4 do gem install -v 5.1.4 --no-rdoc --no-ri activesupport' returned 1: ERROR:  While executing gem ... (OptionParser::InvalidOption)
==> auxmktdevdining:     invalid option: --no-rdoc
==> auxmktdevdining: Error: /Stage[main]/Puphpet::Ruby/Puphpet::Ruby::Install[ruby1]/Rvm_gem[activesupport for Ruby 2.4]/ensure: change from 'absent' to '5.1.4' failed: Could not update: Execution of '/usr/local/rvm/bin/rvm 2.4 do gem install -v 5.1.4 --no-rdoc --no-ri activesupport' returned 1: ERROR:  While executing gem ... (OptionParser::InvalidOption)
==> auxmktdevdining:     invalid option: --no-rdoc
==> auxmktdevdining: Error: Could not update: Execution of '/usr/local/rvm/bin/rvm 2.4 do gem install -v 0.4 --no-rdoc --no-ri vine' returned 1: ERROR:  While executing gem ... (OptionParser::InvalidOption)
==> auxmktdevdining:     invalid option: --no-rdoc
==> auxmktdevdining: Error: /Stage[main]/Puphpet::Ruby/Puphpet::Ruby::Install[ruby1]/Rvm_gem[vine for Ruby 2.4]/ensure: change from 'absent' to '0.4' failed: Could not update: Execution of '/usr/local/rvm/bin/rvm 2.4 do gem install -v 0.4 --no-rdoc --no-ri vine' returned 1: ERROR:  While executing gem ... (OptionParser::InvalidOption)
==> auxmktdevdining:     invalid option: --no-rdoc
==> auxmktdevdining: Warning: Could not match bundler (default: 1.17.3)
==> auxmktdevdining: Error: Execution of '/usr/local/rvm/bin/rvm 2.4 do gem install --no-rdoc --no-ri bundler' returned 1: ERROR:  While executing gem ... (OptionParser::InvalidOption)
==> auxmktdevdining:     invalid option: --no-rdoc
==> auxmktdevdining: Error: /Stage[main]/Puphpet::Ruby/Puphpet::Ruby::Install[ruby1]/Rvm_gem[bundler for Ruby 2.4]/ensure: change from 'absent' to 'present' failed: Execution of '/usr/local/rvm/bin/rvm 2.4 do gem install --no-rdoc --no-ri bundler' returned 1: ERROR:  While executing gem ... (OptionParser::InvalidOption)
==> auxmktdevdining:     invalid option: --no-rdoc

@jonnypickett
Copy link

@justpie that's a different issue. I came across that same issue you are having, and the workaround provided on issue #2838 cleared it up for me.

@justpie
Copy link

justpie commented May 15, 2019

@jonnypickett Thanks! This solution worked.

@jcmosaiclearning
Copy link

jcmosaiclearning commented Oct 23, 2019

It appears the key ID that @tlartaud posted may have changed yet again:

==> ea.local: }
==> ea.local: Error: /Stage[main]/Puphpet::Ruby/Gnupg_key[rvm_D39DC0E3]/ensure: change from 'absent' to 'present' failed: Error while importing key D39DC0E3 from https://rvm.io/mpapis.asc:
==> ea.local: }
==> ea.local: Error: Error while importing key 39499BDB from https://rvm.io/pkuczynski.asc:
==> ea.local: }
==> ea.local: Error: /Stage[main]/Puphpet::Ruby/Gnupg_key[rvm_pkuczynski]/ensure: change from 'absent' to 'present' failed: Error while importing key 7D2BAF1C from https://rvm.io/pkuczynski.asc:
==> ea.local: }

After looking around on RVM's site and through their repo's tickets, I can't find a "Key ID" at all to use here.

@rbuelund
Copy link

I also have the same problem - any solution here ??

@quantumwebco
Copy link

This issue is still a problem. @tlartaud fix worked though.

@specialfae
Copy link

Issue's back again

@DiegoFleitas
Copy link

Same issue, I wasn't able to get it to work with any of the solutions posted here

@pgrosvenor
Copy link

I'm also having the same problem again suddenly

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests