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

vagrant --help displays a rubygems error #8519

Closed
mfdj opened this Issue Apr 24, 2017 · 38 comments

Comments

Projects
None yet
@mfdj

mfdj commented Apr 24, 2017

Vagrant version

$ vagrant --version
1.9.4

Host operating system

$ sw_ver
ProductName:     Mac OS X
ProductVersion:   10.12.4
BuildVersion:    16E195

Expected behavior

vagrant and vagrant --help prints a list of commands

Actual behavior

A rubygems error occurs.

/opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- vagrant-share/helper/api (LoadError)
from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /opt/vagrant/embedded/gems/gems/vagrant-share-1.1.7/lib/vagrant-share/activate.rb:244:in `'
from /opt/vagrant/embedded/gems/gems/vagrant-share-1.1.7/lib/vagrant-share/activate.rb:16:in `RGLoader_load'
from /opt/vagrant/embedded/gems/gems/vagrant-share-1.1.7/lib/vagrant-share/activate.rb:16:in `'
from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /opt/vagrant/embedded/gems/gems/vagrant-share-1.1.7/lib/vagrant-share.rb:23:in `block in '
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:75:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:75:in `block (2 levels) in help'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/registry.rb:49:in `block in each'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/registry.rb:48:in `each'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/registry.rb:48:in `each'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:69:in `block in help'
from /opt/vagrant/embedded/lib/ruby/2.2.0/optparse.rb:917:in `initialize'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:57:in `new'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:57:in `help'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:32:in `execute'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/environment.rb:308:in `cli'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/bin/vagrant:127:in `'

Steps to reproduce

  1. Install vagrant from the web
  2. Run vagrant --help
@piotr-cz

This comment has been minimized.

Show comment
Hide comment
@piotr-cz

piotr-cz Apr 25, 2017

This is a 1.9.4 thing,
it happens when running just vagrant too

piotr-cz commented Apr 25, 2017

This is a 1.9.4 thing,
it happens when running just vagrant too

@teresaejunior

This comment has been minimized.

Show comment
Hide comment
@teresaejunior

teresaejunior Apr 25, 2017

I think the latest Vagrant build is just incomplete. Same error on Ubuntu 17.04.

teresaejunior commented Apr 25, 2017

I think the latest Vagrant build is just incomplete. Same error on Ubuntu 17.04.

@mattyhansen

This comment has been minimized.

Show comment
Hide comment
@mattyhansen

mattyhansen Apr 25, 2017

Also happening on Windows 10 (vagrant 1.9.1 on other machine is working okay)

mattyhansen commented Apr 25, 2017

Also happening on Windows 10 (vagrant 1.9.1 on other machine is working okay)

@adiachenko

This comment has been minimized.

Show comment
Hide comment
@adiachenko

adiachenko Apr 25, 2017

I concur that Vagrant 1.9.4 doesn't work on Windows 10.

adiachenko commented Apr 25, 2017

I concur that Vagrant 1.9.4 doesn't work on Windows 10.

@xjchengo

This comment has been minimized.

Show comment
Hide comment
@xjchengo

xjchengo Apr 26, 2017

I upgraded Vagrant to 1.9.4 on Windows 8. Same error occurs.

C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file
-- vagrant-share/helper/api (LoadError)
        from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-share-1.1.7/lib/vagrant-share/activate.rb:244:in `<encoded>
'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-share-1.1.7/lib/vagrant-share/activate.rb:16:in `RGLoader_l
oad'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-share-1.1.7/lib/vagrant-share/activate.rb:16:in `<top (requ
ired)>'
        from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-share-1.1.7/lib/vagrant-share.rb:23:in `block in <class:Plu
gin>'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:75:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:75:in `block (2 levels) in help'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/registry.rb:49:in `block in each'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/registry.rb:48:in `each'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/registry.rb:48:in `each'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:69:in `block in help'
        from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/optparse.rb:917:in `initialize'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:57:in `new'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:57:in `help'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:32:in `execute'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/environment.rb:308:in `cli'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/bin/vagrant:127:in `<main>'

xjchengo commented Apr 26, 2017

I upgraded Vagrant to 1.9.4 on Windows 8. Same error occurs.

C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file
-- vagrant-share/helper/api (LoadError)
        from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-share-1.1.7/lib/vagrant-share/activate.rb:244:in `<encoded>
'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-share-1.1.7/lib/vagrant-share/activate.rb:16:in `RGLoader_l
oad'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-share-1.1.7/lib/vagrant-share/activate.rb:16:in `<top (requ
ired)>'
        from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-share-1.1.7/lib/vagrant-share.rb:23:in `block in <class:Plu
gin>'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:75:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:75:in `block (2 levels) in help'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/registry.rb:49:in `block in each'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/registry.rb:48:in `each'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/registry.rb:48:in `each'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:69:in `block in help'
        from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/optparse.rb:917:in `initialize'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:57:in `new'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:57:in `help'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:32:in `execute'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/environment.rb:308:in `cli'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/bin/vagrant:127:in `<main>'

@chrisroberts chrisroberts added the share label Apr 26, 2017

@chrisroberts

This comment has been minimized.

Show comment
Hide comment
@chrisroberts

chrisroberts Apr 26, 2017

Collaborator

To fix this error:

$ vagrant plugin install vagrant-share --plugin-version 1.1.8
Collaborator

chrisroberts commented Apr 26, 2017

To fix this error:

$ vagrant plugin install vagrant-share --plugin-version 1.1.8
@mfdj

This comment has been minimized.

Show comment
Hide comment
@mfdj

mfdj Apr 26, 2017

Can confirm that upgrading vagrant-share from 1.1.7 to 1.1.8 stops the rubygems error.

mfdj commented Apr 26, 2017

Can confirm that upgrading vagrant-share from 1.1.7 to 1.1.8 stops the rubygems error.

@DnZmfr

This comment has been minimized.

Show comment
Hide comment
@DnZmfr

DnZmfr Apr 26, 2017

I also confirm @chrisroberts' solution 👍 Thanks :)

DnZmfr commented Apr 26, 2017

I also confirm @chrisroberts' solution 👍 Thanks :)

@rockts

This comment has been minimized.

Show comment
Hide comment
@rockts

rockts Apr 27, 2017

非常感谢,这个命令解决了问问难题

rockts commented Apr 27, 2017

非常感谢,这个命令解决了问问难题

@amontalban

This comment has been minimized.

Show comment
Hide comment
@amontalban

amontalban Apr 28, 2017

Contributor

Any idea if a 1.9.5 version is going to be released quickly to address this?

Contributor

amontalban commented Apr 28, 2017

Any idea if a 1.9.5 version is going to be released quickly to address this?

@adiachenko

This comment has been minimized.

Show comment
Hide comment
@adiachenko

adiachenko Apr 28, 2017

I second the question, 1.9.4 is still posted on official site, this is just bad considering there in no official notice about this bug and you need to go out of your way to download the older versions.

adiachenko commented Apr 28, 2017

I second the question, 1.9.4 is still posted on official site, this is just bad considering there in no official notice about this bug and you need to go out of your way to download the older versions.

@stephenconnolly1

This comment has been minimized.

Show comment
Hide comment
@stephenconnolly1

stephenconnolly1 Apr 28, 2017

I'm airgapped so can't update offline to get the older version :( How do1.1.8 plugin and install?

stephenconnolly1 commented Apr 28, 2017

I'm airgapped so can't update offline to get the older version :( How do1.1.8 plugin and install?

@chrisroberts

This comment has been minimized.

Show comment
Hide comment
@chrisroberts

chrisroberts Apr 28, 2017

Collaborator

@stephenconnolly1 First fetch the gem:

$ gem fetch --clear-sources --source https://gems.hashicorp.com vagrant-share

move gem to offline machine, then install as plugin:

$ vagrant plugin install ./vagrant-share-1.1.8.gem
Collaborator

chrisroberts commented Apr 28, 2017

@stephenconnolly1 First fetch the gem:

$ gem fetch --clear-sources --source https://gems.hashicorp.com vagrant-share

move gem to offline machine, then install as plugin:

$ vagrant plugin install ./vagrant-share-1.1.8.gem
@belcebus

This comment has been minimized.

Show comment
Hide comment
@belcebus

belcebus Apr 28, 2017

vagrant plugin install vagrant-share --plugin-version 1.1.8 only fix vagrant --help and vagrant command, but when starting virtual machine from Windows 7 Host the error still happens:

development: Warning: Remote connection disconnect. Retrying...

==> development: Forcing shutdown of VM...
==> development: Destroying VM and associated drives...
C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:54:in readpartial': An established connection was aborted by the software in your host machine. (Errno::ECONNABORTED) from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:54:inblock (2 levels) in negotiate!'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:52:in loop' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:52:inblock in negotiate!'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:50:in loop' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:50:innegotiate!'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:32:in initialize' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/session.rb:84:innew'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/session.rb:84:in initialize' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh.rb:233:innew'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh.rb:233:in start' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:397:inblock (2 levels) in connect'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:in block in timeout' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:inblock in catch'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:incatch'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:in timeout' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:371:inblock in connect'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/util/retryable.rb:17:in retryable' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:370:inconnect'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:68:in block in wait_for_ready' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:inblock in timeout'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in block in catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:incatch'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:intimeout'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:46:in wait_for_ready' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/action/builtin/wait_for_communicator.rb:16:inblock in call'

belcebus commented Apr 28, 2017

vagrant plugin install vagrant-share --plugin-version 1.1.8 only fix vagrant --help and vagrant command, but when starting virtual machine from Windows 7 Host the error still happens:

development: Warning: Remote connection disconnect. Retrying...

==> development: Forcing shutdown of VM...
==> development: Destroying VM and associated drives...
C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:54:in readpartial': An established connection was aborted by the software in your host machine. (Errno::ECONNABORTED) from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:54:inblock (2 levels) in negotiate!'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:52:in loop' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:52:inblock in negotiate!'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:50:in loop' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:50:innegotiate!'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:32:in initialize' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/session.rb:84:innew'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/session.rb:84:in initialize' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh.rb:233:innew'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh.rb:233:in start' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:397:inblock (2 levels) in connect'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:in block in timeout' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:inblock in catch'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:incatch'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:in timeout' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:371:inblock in connect'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/util/retryable.rb:17:in retryable' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:370:inconnect'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:68:in block in wait_for_ready' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:inblock in timeout'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in block in catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:incatch'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:intimeout'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:46:in wait_for_ready' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/action/builtin/wait_for_communicator.rb:16:inblock in call'

@chrisroberts

This comment has been minimized.

Show comment
Hide comment
@chrisroberts
Collaborator

chrisroberts commented Apr 28, 2017

@belcebus

This comment has been minimized.

Show comment
Hide comment
@belcebus

belcebus Apr 28, 2017

Thanks! That works for me!

Regards

belcebus commented Apr 28, 2017

Thanks! That works for me!

Regards

@UmanShahzad

This comment has been minimized.

Show comment
Hide comment
@UmanShahzad

UmanShahzad Apr 29, 2017

Christrobert's solution works. Was wanting to try Vagrant for the first time today and ran into the error. Would be very helpful if the official version was updated lest confusion ensue..

UmanShahzad commented Apr 29, 2017

Christrobert's solution works. Was wanting to try Vagrant for the first time today and ran into the error. Would be very helpful if the official version was updated lest confusion ensue..

@danstreeter

This comment has been minimized.

Show comment
Hide comment
@danstreeter

danstreeter Apr 29, 2017

I can confirm that the advice by @chrisroberts above to perform:
vagrant plugin install vagrant-share --plugin-version 1.1.8
has worked for me on a recently upgraded to Vagrant 1.9.4 Win10 machine.

Thanks.

danstreeter commented Apr 29, 2017

I can confirm that the advice by @chrisroberts above to perform:
vagrant plugin install vagrant-share --plugin-version 1.1.8
has worked for me on a recently upgraded to Vagrant 1.9.4 Win10 machine.

Thanks.

@cgatesman

This comment has been minimized.

Show comment
Hide comment
@cgatesman

cgatesman May 1, 2017

The workaround works, but as soon as you do a vagrant plugin update it reverts back to 1.1.7.

cgatesman commented May 1, 2017

The workaround works, but as soon as you do a vagrant plugin update it reverts back to 1.1.7.

@SP3C7RE

This comment has been minimized.

Show comment
Hide comment
@SP3C7RE

SP3C7RE May 1, 2017

Glad I found this thread. I had a problem with "Vagrant up" on 1.9.3... I am new, so I reinstalled with Vagrant 1.9.4, imagine my surprise when I got that error. Good that Vagrant plugin update worked on Win10/64. Thanks.

SP3C7RE commented May 1, 2017

Glad I found this thread. I had a problem with "Vagrant up" on 1.9.3... I am new, so I reinstalled with Vagrant 1.9.4, imagine my surprise when I got that error. Good that Vagrant plugin update worked on Win10/64. Thanks.

@WestleyArgentum

This comment has been minimized.

Show comment
Hide comment
@WestleyArgentum

WestleyArgentum May 2, 2017

Bump – it would be really nice if this went out asap

WestleyArgentum commented May 2, 2017

Bump – it would be really nice if this went out asap

@uoryon

This comment has been minimized.

Show comment
Hide comment
@uoryon

uoryon commented May 3, 2017

thx

@techmaniack

This comment has been minimized.

Show comment
Hide comment
@techmaniack

techmaniack May 3, 2017

vagrant: 1.9.4
osx: 10.12.4

➜  ~ vagrant
/opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- vagrant-share/helper/api (LoadError)
	from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /opt/vagrant/embedded/gems/gems/vagrant-share-1.1.7/lib/vagrant-share/activate.rb:244:in `<encoded>'
	from /opt/vagrant/embedded/gems/gems/vagrant-share-1.1.7/lib/vagrant-share/activate.rb:16:in `RGLoader_load'
	from /opt/vagrant/embedded/gems/gems/vagrant-share-1.1.7/lib/vagrant-share/activate.rb:16:in `<top (required)>'
	from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'

techmaniack commented May 3, 2017

vagrant: 1.9.4
osx: 10.12.4

➜  ~ vagrant
/opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- vagrant-share/helper/api (LoadError)
	from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /opt/vagrant/embedded/gems/gems/vagrant-share-1.1.7/lib/vagrant-share/activate.rb:244:in `<encoded>'
	from /opt/vagrant/embedded/gems/gems/vagrant-share-1.1.7/lib/vagrant-share/activate.rb:16:in `RGLoader_load'
	from /opt/vagrant/embedded/gems/gems/vagrant-share-1.1.7/lib/vagrant-share/activate.rb:16:in `<top (required)>'
	from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
@ochetski

This comment has been minimized.

Show comment
Hide comment
@ochetski

ochetski May 3, 2017

Confirmed that fresh instal of 1.9.4 on windows was fixed by:
vagrant plugin install vagrant-share --plugin-version 1.1.8

ochetski commented May 3, 2017

Confirmed that fresh instal of 1.9.4 on windows was fixed by:
vagrant plugin install vagrant-share --plugin-version 1.1.8

@sergeyklay

This comment has been minimized.

Show comment
Hide comment
@sergeyklay

sergeyklay May 4, 2017

@chrisroberts There is reason to not release bug fix asap?

sergeyklay commented May 4, 2017

@chrisroberts There is reason to not release bug fix asap?

@verhulstm

This comment has been minimized.

Show comment
Hide comment
@verhulstm

verhulstm May 4, 2017

the problem also exists for vagrant v1.9.3

verhulstm commented May 4, 2017

the problem also exists for vagrant v1.9.3

@bulat-nugmanov

This comment has been minimized.

Show comment
Hide comment
@bulat-nugmanov

bulat-nugmanov May 6, 2017

Like others mentioned, issue is fixed on Win 10 by updating the vagrant-share plugin version - hopefully this is fixed in next release

bulat-nugmanov commented May 6, 2017

Like others mentioned, issue is fixed on Win 10 by updating the vagrant-share plugin version - hopefully this is fixed in next release

@eannastew

This comment has been minimized.

Show comment
Hide comment
@eannastew

eannastew May 9, 2017

I'm on Windows 10.
I tried vagrant plugin install vagrant-share --plugin-version 1.1.8.
It didn't work.

I then ran a vagrant plugin update
vagrant-share reverted to 1.1.7
vagrant-hostmanager upgraded to 1.8.6 (from 1.8.5)
and vagrant-vbguest upgraded to 0.14.2 (from 0.13.0)
All working now.
Hope this helps.

eannastew commented May 9, 2017

I'm on Windows 10.
I tried vagrant plugin install vagrant-share --plugin-version 1.1.8.
It didn't work.

I then ran a vagrant plugin update
vagrant-share reverted to 1.1.7
vagrant-hostmanager upgraded to 1.8.6 (from 1.8.5)
and vagrant-vbguest upgraded to 0.14.2 (from 0.13.0)
All working now.
Hope this helps.

@olojiang

This comment has been minimized.

Show comment
Hide comment
@olojiang

olojiang May 10, 2017

Thanks, it works fine with: vagrant plugin install vagrant-share --plugin-version 1.1.8

olojiang commented May 10, 2017

Thanks, it works fine with: vagrant plugin install vagrant-share --plugin-version 1.1.8

@jay7793

This comment has been minimized.

Show comment
Hide comment
@jay7793

jay7793 May 10, 2017

vagrant plugin install vagrant-share --plugin-version 1.1.8 That work on osx 10.12.4

jay7793 commented May 10, 2017

vagrant plugin install vagrant-share --plugin-version 1.1.8 That work on osx 10.12.4

@helieting

This comment has been minimized.

Show comment
Hide comment
@helieting

helieting May 12, 2017

vagrant plugin install vagrant-share --plugin-version 1.1.8 work on osx 10.11.6

helieting commented May 12, 2017

vagrant plugin install vagrant-share --plugin-version 1.1.8 work on osx 10.11.6

@xRomZak

This comment has been minimized.

Show comment
Hide comment
@xRomZak

xRomZak May 12, 2017

vagrant plugin install vagrant-share --plugin-version 1.1.8 work on Windows 8 + Babun

xRomZak commented May 12, 2017

vagrant plugin install vagrant-share --plugin-version 1.1.8 work on Windows 8 + Babun

@adiachenko

This comment has been minimized.

Show comment
Hide comment
@adiachenko

adiachenko May 12, 2017

Hey, guys, it's not a census, I'm pretty sure everybody have already caught on the fact that this fixes the issue. 😄

adiachenko commented May 12, 2017

Hey, guys, it's not a census, I'm pretty sure everybody have already caught on the fact that this fixes the issue. 😄

@l0010o0001l

This comment has been minimized.

Show comment
Hide comment
@l0010o0001l

l0010o0001l May 12, 2017

:P They are happy! @adiachenko

l0010o0001l commented May 12, 2017

:P They are happy! @adiachenko

@miroswan

This comment has been minimized.

Show comment
Hide comment
@miroswan

miroswan May 15, 2017

Also, you don't have to go that far back to get a working version. Just a heads up.

miroswan commented May 15, 2017

Also, you don't have to go that far back to get a working version. Just a heads up.

@chrisroberts

This comment has been minimized.

Show comment
Hide comment
@chrisroberts

chrisroberts May 16, 2017

Collaborator

Fixed in 1.9.5 release. Cheers!

Collaborator

chrisroberts commented May 16, 2017

Fixed in 1.9.5 release. Cheers!

@piotr-cz

This comment has been minimized.

Show comment
Hide comment
@piotr-cz

piotr-cz May 17, 2017

Confirming it's been fixed in v1.9.5.
Too bad it's not noted in CHANGELOG.md

piotr-cz commented May 17, 2017

Confirming it's been fixed in v1.9.5.
Too bad it's not noted in CHANGELOG.md

@settermjd

This comment has been minimized.

Show comment
Hide comment
@settermjd

settermjd Oct 24, 2017

Thanks @chrisroberts for your comment. It worked perfectly. Fwiw, my issue arose after upgrading from macOS Sierra to High Sierra.

settermjd commented Oct 24, 2017

Thanks @chrisroberts for your comment. It worked perfectly. Fwiw, my issue arose after upgrading from macOS Sierra to High Sierra.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment