[Bug 1133312] New: Dependencies for Vagrant are broken
http://bugzilla.opensuse.org/show_bug.cgi?id=1133312 Bug ID: 1133312 Summary: Dependencies for Vagrant are broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs@suse.de Reporter: andrew@fluidgravity.co.uk QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I've been using Vagrant installed with zypper from here: https://download.opensuse.org/repositories/Virtualization:/vagrant/openSUSE_... The latest update is broken, rendering vagrant unusable: sudo zypper -n in vagrant vagrant plugin install vagrant-vbguest Installing the 'vagrant-vbguest' plugin. This can take a few minutes... Bundler, the underlying system Vagrant uses to install plugins, reported an error. The error is shown below. These errors are usually caused by misconfigured plugin installations or transient network issues. The error from Bundler is: conflicting dependencies fog-core (~> 1.43.0) and fog-core (= 2.1.2) Activated fog-core-2.1.2 which does not match conflicting dependency (~> 1.43.0) Conflicting dependency chains: fog-core (= 2.1.2), 2.1.2 activated versus: vagrant-libvirt (> 0), 0.0.41 activated, depends on fog-core (~> 1.43.0) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1133312 http://bugzilla.opensuse.org/show_bug.cgi?id=1133312#c10 --- Comment #10 from Johannes Kastl <opensuse_buildservice@ojkastl.de> --- Hi I'll try to have a look tomorrow. Any reason why you have vagrant-libvirt 0.0.41 installed? I see 0.0.45 in Virtualization:vagrant... Johannes -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1133312 http://bugzilla.opensuse.org/show_bug.cgi?id=1133312#c11 Johannes Kastl <opensuse_buildservice@ojkastl.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(andrew@fluidgravi | |ty.co.uk) --- Comment #11 from Johannes Kastl <opensuse_buildservice@ojkastl.de> --- Hi everyone, I just fixed the builds for Leap 15* and SLE15, so vagrant* are building again. As for installations of plugins: We need to workaround several limitations so we provide plugins installable via RPM. Try installing the vbguest RPM and check if this works, rather than using "vagrant plugin install ...". If you need additional plugins packaged as RPMs, just drop Dan or me a line and we can have a look. Kind Regards, Johannes -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1133312 http://bugzilla.opensuse.org/show_bug.cgi?id=1133312#c12 Andrew Wood <andrew@fluidgravity.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(andrew@fluidgravi | |ty.co.uk) | --- Comment #12 from Andrew Wood <andrew@fluidgravity.co.uk> --- (In reply to Johannes Kastl from comment #10)
Hi I'll try to have a look tomorrow.
Any reason why you have vagrant-libvirt 0.0.41 installed? I see 0.0.45 in Virtualization:vagrant...
Johannes
I don't have version 0.0.41 installed. That's just what's reported when I run "vagrant plugin install vagrant-vbguest". "zypper if vagrant-libvirt" gives this output: Loading repository data... Reading installed packages... Information for package vagrant-libvirt: ---------------------------------------- Repository : Vagrant Name : vagrant-libvirt Version : 0.0.45-lp150.2.2 Arch : x86_64 Vendor : obs://build.opensuse.org/Virtualization Installed Size : 384.0 KiB Installed : Yes (automatically) Status : up-to-date Source package : vagrant-libvirt-0.0.45-lp150.2.2.src Summary : Vagrant provider for libvirt Description : This is a Vagrant plugin that adds an Libvirt provider to Vagrant, allowing Vagrant to control and provision machines via Libvirt toolkit. "zypper in vagrant-vbguest" still isn't working and it's giving me the same error as before: Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides rubygem(ruby:2.5.0:micromachine:2.0) needed by vagrant-vbguest-0.17.2-lp150.1.6.x86_64 Solution 1: do not install vagrant-vbguest-0.17.2-lp150.1.6.x86_64 Solution 2: break vagrant-vbguest-0.17.2-lp150.1.6.x86_64 by ignoring some of its dependencies -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1133312 http://bugzilla.opensuse.org/show_bug.cgi?id=1133312#c13 --- Comment #13 from Johannes Kastl <opensuse_buildservice@ojkastl.de> --- Hi, sorry, I am working on providing a micromachine package. Johannes -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1133312 http://bugzilla.opensuse.org/show_bug.cgi?id=1133312#c14 Johannes Kastl <opensuse_buildservice@ojkastl.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(andrew@fluidgravi | |ty.co.uk) --- Comment #14 from Johannes Kastl <opensuse_buildservice@ojkastl.de> --- Hi, I could install the packages, can you test if it works for you? Johannes The following 2 NEW packages are going to be installed: ruby2.5-rubygem-micromachine-2.0 vagrant-vbguest 2 new packages to install. Overall download size: 85.8 KiB. Already cached: 0 B. After the operation, additional 148.2 KiB will be used. Continue? [y/n/...? shows all options] (y): y Retrieving package ruby2.5-rubygem-micromachine-2.0-2.0.0-lp150.3.1.x86_64 (1/2), 19.1 KiB ( 19.3 KiB unpacked) Retrieving: ruby2.5-rubygem-micromachine-2.0-2.0.0-lp150.3.1.x86_64.rpm ...............................................................................................................[done] Retrieving package vagrant-vbguest-0.17.2-lp150.1.6.x86_64 (2/2), 66.7 KiB (128.9 KiB unpacked) Retrieving: vagrant-vbguest-0.17.2-lp150.1.6.x86_64.rpm ...............................................................................................................................[done] Checking for file conflicts: ..........................................................................................................................................................[done] (1/2) Installing: ruby2.5-rubygem-micromachine-2.0-2.0.0-lp150.3.1.x86_64 .............................................................................................................[done] (2/2) Installing: vagrant-vbguest-0.17.2-lp150.1.6.x86_64 .............................................................................................................................[done] -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1133312 http://bugzilla.opensuse.org/show_bug.cgi?id=1133312#c15 --- Comment #15 from Andrew Wood <andrew@fluidgravity.co.uk> --- (In reply to Johannes Kastl from comment #14)
Hi,
I could install the packages, can you test if it works for you?
Johannes
vagrant-vbguest installs successfully with zypper. I also need vagrant-hosts and vagrant-scp, but "vagrant plugin install ..." complains about conflicting dependencies for fog-core again. Can you add these too? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1133312 http://bugzilla.opensuse.org/show_bug.cgi?id=1133312#c18 --- Comment #18 from Johannes Kastl <opensuse_buildservice@ojkastl.de> --- HI Andrew, I built both of them yesterday in Virtualization:vagrant, but had no time yet to test. Can you check if those are working? Kind Regards, Johannes -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1133312 http://bugzilla.opensuse.org/show_bug.cgi?id=1133312#c20 --- Comment #20 from Johannes Kastl <opensuse_buildservice@ojkastl.de> --- I tried to tackle this in SR#712282 (https://build.opensuse.org/request/show/712282), which tells vagrant-scp to use newer versions of bundler and net-scp. Both of the dependencies are already being built in Virtualization:vagrant for SLES15/SLES15-SP1 and Leap 15.0/15.1. Johannes -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1133312 http://bugzilla.opensuse.org/show_bug.cgi?id=1133312#c21 --- Comment #21 from Andrew Wood <andrew@fluidgravity.co.uk> --- (In reply to Johannes Kastl from comment #20)
I tried to tackle this in SR#712282 (https://build.opensuse.org/request/show/712282), which tells vagrant-scp to use newer versions of bundler and net-scp. Both of the dependencies are already being built in Virtualization:vagrant for SLES15/SLES15-SP1 and Leap 15.0/15.1.
Johannes
I still get this: sudo zypper in vagrant-scp Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides rubygem(ruby:2.5.0:bundler:1.3) needed by vagrant-scp-0.5.7-lp150.2.3.x86_64 Solution 1: do not install vagrant-scp-0.5.7-lp150.2.3.x86_64 Solution 2: break vagrant-scp-0.5.7-lp150.2.3.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c] (c): c -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1133312 http://bugzilla.opensuse.org/show_bug.cgi?id=1133312#c22 --- Comment #22 from Dan Čermák <dcermak@suse.com> --- (In reply to Andrew Wood from comment #21)
I still get this:
sudo zypper in vagrant-scp Loading repository data... Reading installed packages... Resolving package dependencies...
Problem: nothing provides rubygem(ruby:2.5.0:bundler:1.3) needed by vagrant-scp-0.5.7-lp150.2.3.x86_64 Solution 1: do not install vagrant-scp-0.5.7-lp150.2.3.x86_64 Solution 2: break vagrant-scp-0.5.7-lp150.2.3.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/c] (c): c
This will not get fixed until https://build.opensuse.org/request/show/712282 get's accepted. We are currently waiting for upstream to react to limit the number of custom patches that we carry around. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1133312 http://bugzilla.opensuse.org/show_bug.cgi?id=1133312#c24 Alexander Ahjolinna <ahjolinna@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ahjolinna@yahoo.com --- Comment #24 from Alexander Ahjolinna <ahjolinna@yahoo.com> --- I still have this same original issue on tumbleweed (20191109), but when I tried to install vagrant-scp pkgs I got an different error...sigh: vagrant plugin install vagrant-vbguest Installing the 'vagrant-vbguest' plugin. This can take a few minutes... Vagrant failed to properly resolve required dependencies. These errors can commonly be caused by misconfigured plugin installations or transient network issues. The reported error is: conflicting dependencies bundler (= 1.17.2) and bundler (= 2.0.2) Activated bundler-2.0.2 which does not match conflicting dependency (= 1.17.2) Conflicting dependency chains: bundler (= 2.0.2), 2.0.2 activated versus: bundler (= 1.17.2) Gems matching bundler (= 1.17.2): bundler-1.17.2 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1133312 http://bugzilla.opensuse.org/show_bug.cgi?id=1133312#c25 Dan Cermak <dcermak@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |WONTFIX --- Comment #25 from Dan Cermak <dcermak@suse.com> --- (In reply to Alexander Ahjolinna from comment #24)
I still have this same original issue on tumbleweed (20191109), but when I tried to install vagrant-scp pkgs I got an different error...sigh:
vagrant plugin install vagrant-vbguest Installing the 'vagrant-vbguest' plugin. This can take a few minutes... Vagrant failed to properly resolve required dependencies. These errors can commonly be caused by misconfigured plugin installations or transient network issues. The reported error is:
conflicting dependencies bundler (= 1.17.2) and bundler (= 2.0.2) Activated bundler-2.0.2 which does not match conflicting dependency (= 1.17.2)
Conflicting dependency chains: bundler (= 2.0.2), 2.0.2 activated
versus: bundler (= 1.17.2)
Gems matching bundler (= 1.17.2): bundler-1.17.2
Please stop installing vagrant plugins via `vagrant plugin install` if you installed vagrant via zypper unless the plugin is not packaged as an rpm. The vagrant rpm from the openSUSE repositories shares the rubygems with the systemwide ruby installation, which causes odd version conflicts when vagrant tries to install plugins (vagrant's dependency resolution is weird). There is an upstream issue for this: https://github.com/hashicorp/vagrant/issues/10826. If you really want to use `vagrant plugin install`, then please obtain vagrant from upstream directly. They provide an isolated installation, where these kind of conflicts shouldn't appear. Unfortunately, there's really nothing that I can do to prevent these kind of issues, beside patching vagrant to remove the `vagrant plugin install` functionality. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com