Skip to content
This repository has been archived by the owner on Jan 30, 2021. It is now read-only.

Plugin fails to install with vagrant 1.9.1 #150

Closed
matt-richardson opened this issue Jan 18, 2017 · 16 comments · Fixed by #156
Closed

Plugin fails to install with vagrant 1.9.1 #150

matt-richardson opened this issue Jan 18, 2017 · 16 comments · Fixed by #156
Assignees
@devigned
Labels
documentation

Comments

@matt-richardson
Copy link
Contributor

Installing the plugin fails on vagrant 1.9.1 with the following error:

$ vagrant --version
Vagrant 1.9.1
$ vagrant plugin install vagrant-azure
Installing the 'vagrant-azure' plugin. This can take a few minutes...
/opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/specification.rb:2100:in `check_version_conflict': can't activate mime-types-2.99.3, already activated mime-types-3.1 (Gem::LoadError)
	from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/specification.rb:1276:in `activate'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/bundler.rb:323:in `block in activate_solution'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/bundler.rb:320:in `each'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/bundler.rb:320:in `activate_solution'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/bundler.rb:248:in `internal_install'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/bundler.rb:98:in `install'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/manager.rb:62:in `block in install_plugin'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/manager.rb:72:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/manager.rb:72:in `install_plugin'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/plugin/action/install_gem.rb:37:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/action/builder.rb:116:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/action/runner.rb:66:in `block in run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/util/busy.rb:19:in `busy'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/action/runner.rb:66:in `run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/plugin/command/base.rb:14:in `action'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/plugin/command/install.rb:32:in `block in execute'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/plugin/command/install.rb:31:in `each'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/plugin/command/install.rb:31:in `execute'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/plugin/command/root.rb:66:in `execute'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/cli.rb:42:in `execute'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/environment.rb:308:in `cli'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.9.1/bin/vagrant:127:in `<main>'

I need to use the service management version, rather than the azure resource manager version as I need classic VMs.

Rolling back to vagrant 1.8.7 works.
@AlexZeitler
Copy link

Same here.

@freedev
Copy link
Contributor

freedev commented Jan 23, 2017

same here

@charleswisniewski
Copy link

👍 same here

@devigned devigned mentioned this issue Feb 2, 2017
Merged
@maxi1192
Copy link

the same happens for the plugin vagrant-windows

@devigned devigned reopened this Feb 10, 2017
@ediri
Copy link

ediri commented Feb 17, 2017

same here! can't install the plugin anymore.

@ediri
Copy link

ediri commented Feb 17, 2017 •
edited
Loading

i tried it with the pre3

vagrant plugin install vagrant-azure-2.0.0.pre3.gem
Installing the 'vagrant-azure-2.0.0.pre3.gem' plugin. This can take a few minutes...
C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/rubygems/specification.rb:2100:in `check_version_conflict': can't activate mime-types-2.99.3, already activated mime-types-3.1 (Gem::LoadError)
        from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/rubygems/specification.rb:1276:in `activate'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/bundler.rb:323:in `block in activate_solution'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/bundler.rb:320:in `each'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/bundler.rb:320:in `activate_solution'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/bundler.rb:248:in `internal_install'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/bundler.rb:114:in `install_local'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/plugin/manager.rb:47:in `install_plugin'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/plugin/action/install_gem.rb:37:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/action/runner.rb:66:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/action/runner.rb:66:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/plugin/command/base.rb:14:in `action'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/plugin/command/install.rb:32:in `block in execute'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/plugin/command/install.rb:31:in `each'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/plugin/command/install.rb:31:in `execute'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/plugins/commands/plugin/command/root.rb:66:in `execute'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/cli.rb:42:in `execute'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/lib/vagrant/environment.rb:308:in `cli'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.1/bin/vagrant:127:in `<main>'

@devigned
Copy link
Member

Ok... I want to figure out what's going on here so we can get this corrected. Unfortunately, I'm seeing the following on OS X.

david at warmachine in ~
$ vagrant plugin install vagrant-azure --plugin-version '2.0.0.pre3'
Installing the 'vagrant-azure --version '2.0.0.pre3'' plugin. This can take a few minutes...
Fetching: multipart-post-2.0.0.gem (100%)
Fetching: faraday-0.11.0.gem (100%)
Fetching: concurrent-ruby-1.0.4.gem (100%)
Fetching: timeliness-0.3.8.gem (100%)
Fetching: ms_rest-0.6.3.gem (100%)
Fetching: faraday-cookie_jar-0.0.6.gem (100%)
Fetching: ms_rest_azure-0.6.2.gem (100%)
Fetching: highline-1.7.8.gem (100%)
Fetching: haikunator-1.1.0.gem (100%)
Fetching: azure_mgmt_storage-0.8.0.gem (100%)
Fetching: azure_mgmt_network-0.8.0.gem (100%)
Fetching: azure_mgmt_compute-0.8.0.gem (100%)
Fetching: azure_mgmt_resources-0.8.0.gem (100%)
Fetching: vagrant-azure-2.0.0.pre3.gem (100%)
Installed the plugin 'vagrant-azure (2.0.0.pre3)'!

david at warmachine in ~
$ vagrant --version
Vagrant 1.9.1

Could someone run the install with vagrant plugin install vagrant-azure --plugin-version '2.0.0.pre3' --plugin-clean-sources and see if that helps. If running that install command doesn't help, please respond back with a gist of --debug output.

@ediri
Copy link

ediri commented Feb 20, 2017

@devigned Your proposed command worked for me 👍

@devigned
Copy link
Member

@ediri, thank you for the response!

I'm going to leave this issue open for just a bit to ensure this gets added to the readme. Based on the number of responses to this issues, it appears it may be a common problem.

@devigned devigned self-assigned this Feb 20, 2017
@maxi1192
Copy link

for me the issue only appears for old vagrant boxes. With more recent boxes the newest version of vagrant is not asked for windows plugin any more.

@devigned
Copy link
Member

I ran into this problem today. I ended up reinstalling Vagrant and everything just worked... 🤷‍♂️

Seems like something to do with previously installed gem dependencies and boxes. This is really odd.

@ediri
Copy link

ediri commented Mar 1, 2017

@devigned reinstalling vagrant is big bang solution. Really interested if this happens with other plugins too?

@devigned
Copy link
Member

devigned commented Mar 1, 2017

@ediri agreed. I don't like that solution.

Do you have a set of steps that can reliably reproduce the issue?

Also, I feel like this issue will end up in https://github.com/mitchellh/vagrant rather than here. I went through our gem dependencies and nothing in the v2.0 dependency chain includes mime-types.

Hmm... were using v1.x and moved to v2 of vagrant-azure? Perhaps, the gem dependency is in an old v1.x box or something.

@devigned devigned mentioned this issue Mar 7, 2017
Closed
@purplefeetguy
Copy link

is there an answer for this? I reinstalled vagrant and get the same, I pushed to an earlier version and broke the rest of my plugins. what is the fix here?

@devigned devigned reopened this May 1, 2017
@devigned devigned closed this as completed May 1, 2017
@purplefeetguy
Copy link

purplefeetguy@pflnuc04:$ vagrant plugin install vagrant-azure
Installing the 'vagrant-azure' plugin. This can take a few minutes...
/opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/specification.rb:2100:in check_version_conflict': can't activate mime-types-2.99.3, already activated mime-types-3.1 (Gem::LoadError) from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/specification.rb:1276:in activate'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/bundler.rb:388:in block in activate_solution' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/bundler.rb:385:in each'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/bundler.rb:385:in activate_solution' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/bundler.rb:288:in internal_install'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/bundler.rb:106:in install' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/plugin/manager.rb:62:in block in install_plugin'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/plugin/manager.rb:72:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/plugin/manager.rb:72:in install_plugin'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/commands/plugin/action/install_gem.rb:29:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/action/warden.rb:34:in call'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/action/builder.rb:116:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/action/runner.rb:66:in block in run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/util/busy.rb:19:in busy' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/action/runner.rb:66:in run'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/commands/plugin/command/base.rb:14:in action' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/commands/plugin/command/install.rb:32:in block in execute'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/commands/plugin/command/install.rb:31:in each' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/commands/plugin/command/install.rb:31:in execute'
from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/commands/plugin/command/root.rb:66:in execute' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:42: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

'
purplefeetguy@pflnuc04:$

@purplefeetguy
Copy link

my bad, I should read more....can be closed

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

@devigned devigned

Labels
documentation
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update the project devigned/vagrant-azure
8 participants
@AlexZeitler @matt-richardson @devigned @freedev @ediri @purplefeetguy @maxi1192 @charleswisniewski