Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failure of RVM installation not causing chef-client to fail #182

Closed
finack opened this issue Mar 16, 2013 · 3 comments
Closed

Failure of RVM installation not causing chef-client to fail #182

finack opened this issue Mar 16, 2013 · 3 comments

Comments

@finack
Copy link

finack commented Mar 16, 2013

If retrieval of the rvm install script fails, it does not cause the failure to surface to Chef and abort the client.

The command in question is (for me):

 https://get.rvm.io | bash  -s -- --version 1.18.14

I believe the issue is that it fails (because of rvm.io ssl error) but bash is returning exit code 0.

Maybe this should be two steps? One curl the script, two run the script?

Background

Currently there is an issue with the SSL Certificate on rvm.io. Thanks to @cromulus comment in #51, I was able to fix the issue by changing the rvm install path to:

node['rvm']: ['installer_url']="https://raw.github.com/wayneeseguin/rvm/master/binscripts/rvm-installer"

For those searching for this problem, the error I received in my chef logs was

private method `chomp' called for nil:NilClass

See https://gist.github.com/finack/5174496 for my logs.

@noahgibbs
Copy link

I'm seeing a failure in Ruby installation, too. When Ruby install fails, it's not aborting the chef run. It only prints a warning saying that the Ruby wasn't installed.

@cmluciano
Copy link
Contributor

This should be fixed for system with #285 and user in #298. Please reopen if this is still an issue

@lock
Copy link

lock bot commented Apr 25, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2020
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

3 participants