Navigation Menu

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

1.9.4 installs very old version of plugin #8550

Closed
kivoli opened this issue May 2, 2017 · 4 comments · Fixed by #8571
Closed

1.9.4 installs very old version of plugin #8550

kivoli opened this issue May 2, 2017 · 4 comments · Fixed by #8571

Comments

@kivoli
Copy link

kivoli commented May 2, 2017

For an unknown reason Vagrant 1.9.4 reproducible installs only a very old version of vagrant-libvirt (0.0.20) while 1.9.3 does pull the correct version, 0.0.40. Downgrading Vagrant for this purpose works, too.

Vagrant version

Installed Version: 1.9.4
Latest Version: 1.9.4

Host operating system

Ubuntu 16.04

Guest operating system

N/A

Vagrantfile

N/A

Debug output

Installed the plugin 'vagrant-libvirt (0.0.20)'!

Expected behavior

Install newest version (0.0.40) of vagrant-libvirt plugin.

Actual behavior

Installs very old version (0.0.20)

Steps to reproduce

  1. Set up Ubuntu 16.0.4
  2. Install Vagrant 1.9.4 using the Debian 64 binary from vagrantup.com
  3. Run vagrant plugin install vagrant-libvirt
@chrisroberts
Copy link
Member

@kivoli Forcing the latest version (vagrant plugin install vagrant-libvirt --plugin-version 0.0.40) shows there is a dependency conflict with nokogiri. I've been looking at removing nokogiri from the shipped installer to prevent these conflicts, and it looks like I'll need to speed that up.

@chrisroberts chrisroberts added this to the 1.9.5 milestone May 2, 2017
@kivoli
Copy link
Author

kivoli commented May 3, 2017

@chrisroberts Okay, but I find the behaviour of Vagrant a bit confusing, too. Because it insisted on vagrant plugin update that 0.0.20 is the latest version. Other users may not have realised that there is a newer version available. Would it be possible to print a warning in such a case?
Anyway, thanks for finding the culprit! Didn’t think of forcing the new version; I’ll remember that for my next bug report.

@COLABORATI
Copy link

Please support libvirt right oob, this is the best virtualization option on Linux systems and it sux that vagrant still produces problems with that. It would help if your devs used Linux systems, then these kind of errors would never happen.

chrisroberts added a commit to chrisroberts/vagrant that referenced this issue May 8, 2017
Removes the nokogiri dependency to prevent resolution conflicts
with plugins that may require earlier or later versions than what
Vagrant constrains to.

Fixes hashicorp#8550
@ghost
Copy link

ghost commented Apr 2, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@hashicorp hashicorp locked and limited conversation to collaborators Apr 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants