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

Update to Ruby 2.5.0 appears to break vagrant provision #6391

Closed
1 of 2 tasks
northerner opened this issue Jan 31, 2018 · 0 comments
Closed
1 of 2 tasks

Update to Ruby 2.5.0 appears to break vagrant provision #6391

northerner opened this issue Jan 31, 2018 · 0 comments

Comments

@northerner
Copy link
Contributor

northerner commented Jan 31, 2018

The update to Ruby 2.5.0 (#6097) appears to have broken the vagrant provision at the point it starts to download gem dependencies.

Have attempted to provision vagrant box from scratch with preceding commit (b1e0319) and it works fine.

default: ruby-2.5.0 - #validate archive
    default: ruby-2.5.0 - #extract
    default: ruby-2.5.0 - #validate binary
    default: ruby-2.5.0 - #setup
    default: ruby-2.5.0 - #gemset created /home/vagrant/.rvm/gems/ruby-2.5.0@global
    default: ruby-2.5.0 - #importing gemset /home/vagrant/.rvm/gemsets/global.gems
    default: there was an error installing gem rubygems-bundler
    default: ....................................
    default: ruby-2.5.0 - #generating global wrappers
    default: ........
    default: Error running 'run_gem_wrappers_regenerate',
    default: please read /home/vagrant/.rvm/log/1517359029_ruby-2.5.0/gemset.wrappers.global.log
    default: ruby-2.5.0 - #gemset created /home/vagrant/.rvm/gems/ruby-2.5.0
    default: ruby-2.5.0 - #importing gemsetfile /home/vagrant/.rvm/gemsets/default.gems evaluated to empty gem list
    default: ruby-2.5.0 - #generating default wrappers
    default: ........
    default: Error running 'run_gem_wrappers_regenerate',
    default: please read /home/vagrant/.rvm/log/1517359029_ruby-2.5.0/gemset.wrappers.default.log
    default: Creating alias default for ruby-2.5.0
    default: ...
    default:   * To start using RVM you need to run `source /home/vagrant/.rvm/scripts/rvm`
    default:     in all your open shell windows, in rare cases you need to reopen all shell windows.
    default: Already installed ruby-2.5.0.
    default: To reinstall use:
    default:     rvm reinstall ruby-2.5.0
    default: /home/vagrant/.rvm/scripts/override_gem: /home/vagrant/.rvm/rubies/ruby-2.5.0/bin/gem: /home/travis/.rvm/rubies/ruby-2.5.0/bin/ruby: bad interpreter: No such file or directory
    default: /tmp/vagrant-shell: /home/vagrant/.rvm/rubies/ruby-2.5.0/bin/bundle: /home/travis/.rvm/rubies/ruby-2.5.0/bin/ruby: bad interpreter: No such file or directory

When running vagrant ssh -c "cd /vagrant && foreman start" after failed provision error bash: foreman: command not found is returned.


  • I searched or browsed the repo’s other issues to ensure this is not a duplicate.
  • This bug happens on a tagged release and not on master (If you're a user, don't worry about this).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant