Hello,
Our cico test for testing our Vagrant images have support for optionally using vagrant-vbguest. This is now failing with:
+ scl enable sclo-vagrant1 '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:
Authentication is required for http://gems.hashicorp.com/. Please supply credentials for this source. You can do this by running: bundle config http://gems.hashicorp.com/ username:password Build step 'Execute shell' marked build as failure
I think this is caused by the older version we have in SCL - I can install vagrant-vbguest without any issues on Vagrant 1.9.3 (on OS X). I now reverted the test to not use vagrant-vbguest, but it's still failing because SCL Vagrant doesn't support VirtualBox 5.1.x. Oracle already put a warning on the download page for VirtualBox 5.0.x: "VirtualBox 5.0.x runs out of support, switch to VirtualBox 5.1.x!"
https://www.virtualbox.org/wiki/Download_Old_Builds_5_0
We risk becoming unable to automatically test our images with VirtualBox - could we get a Vagrant update in SCL, please?
Thanks, Laurentiu
On 25/04/17 13:38, Laurentiu Pancescu wrote:
We risk becoming unable to automatically test our images with VirtualBox
- could we get a Vagrant update in SCL, please?
I changed the test to use the upstream versions of Vagrant and vagrant-libvirt (we already used the VirtualBox packages from Oracle). Vagrant 1.9.4, the newest release, doesn't recognize vagrant-libvirt, so the test fails - I'm using Vagrant 1.9.3 for the time being, that version works.
Since I'm primarily interested in finding bugs in our Vagrant images, not in Vagrant itself, I would still prefer to use the version in SCL, when it will be updated to support VirtualBox 5.1.
----- Original Message -----
From: "Laurentiu Pancescu" lpancescu@gmail.com To: "The CentOS developers mailing list." centos-devel@centos.org Sent: Tuesday, April 25, 2017 5:20:42 PM Subject: Re: [CentOS-devel] We need a newer Vagrant in SCL
On 25/04/17 13:38, Laurentiu Pancescu wrote:
We risk becoming unable to automatically test our images with VirtualBox
- could we get a Vagrant update in SCL, please?
I changed the test to use the upstream versions of Vagrant and vagrant-libvirt (we already used the VirtualBox packages from Oracle). Vagrant 1.9.4, the newest release, doesn't recognize vagrant-libvirt, so the test fails - I'm using Vagrant 1.9.3 for the time being, that version works.
I am working on the sclo-vagrant1 SCL update. Thanks for the heads-up regarding the vagrant version usability. I will push to testing the new SCL builds ASAP(ETA < 1 month)
Since I'm primarily interested in finding bugs in our Vagrant images, not in Vagrant itself, I would still prefer to use the version in SCL, when it will be updated to support VirtualBox 5.1.
Regards,
Pavel Valena Associate Software Engineer Brno, Czech Republic
RED HAT | TRIED. TESTED. TRUSTED. All of the airlines in the Fortune Global 500 rely on Red Hat. Find out why at Trusted | Red Hat
On 02/05/17 13:13, Pavel Valena wrote:
On 25/04/17 13:38, Laurentiu Pancescu wrote: I changed the test to use the upstream versions of Vagrant and vagrant-libvirt (we already used the VirtualBox packages from Oracle). Vagrant 1.9.4, the newest release, doesn't recognize vagrant-libvirt, so the test fails - I'm using Vagrant 1.9.3 for the time being, that version works.
I am working on the sclo-vagrant1 SCL update. Thanks for the heads-up regarding the vagrant version usability. I will push to testing the new SCL builds ASAP(ETA < 1 month)
It seems a bit more nuanced than I thought: upstream vagrant-libvirt only supports Vagrant 1.5 to 1.8. [1] There's also a table with build failures on Vagrant 1.9.1 if you scroll up. For some reason, 1.9.3 worked on CentOS Linux 7 with vagrant-libvirt and 1.9.4 didn't, but 1.9.x is clearly not a supported configuration - not yet.
With KVM as the default virtualization on CentOS, fully supported, and VirtualBox not even packaged in our repos (not to mention kernel tainting), wouldn't it be better to upgrade the SCL version to another 1.8.x version instead of the current 1.9 series? Perhaps 1.8.6, it worked reliably for me for a long time and it would support both KVM and VirtualBox 5.1.
Thanks, Laurențiu
[1] https://github.com/vagrant-libvirt/vagrant-libvirt#installation
On Tue, May 2, 2017 at 11:06 PM, Laurentiu Pancescu lpancescu@gmail.com wrote:
On 02/05/17 13:13, Pavel Valena wrote:
On 25/04/17 13:38, Laurentiu Pancescu wrote: I changed the test to use the upstream versions of Vagrant and vagrant-libvirt (we already used the VirtualBox packages from Oracle). Vagrant 1.9.4, the newest release, doesn't recognize vagrant-libvirt, so the test fails - I'm using Vagrant 1.9.3 for the time being, that version works.
I am working on the sclo-vagrant1 SCL update. Thanks for the heads-up regarding the vagrant version usability. I will push to testing the new SCL builds ASAP(ETA < 1 month)
It seems a bit more nuanced than I thought: upstream vagrant-libvirt only supports Vagrant 1.5 to 1.8. [1] There's also a table with build failures on Vagrant 1.9.1 if you scroll up. For some reason, 1.9.3 worked on CentOS Linux 7 with vagrant-libvirt and 1.9.4 didn't, but 1.9.x is clearly not a supported configuration - not yet.
Regarding this specific point, I think it is maybe more likely a documentation oversight that they haven't updated that reference to include 1.9+. The continuation of the line mentioning supported versions says "We only test with the upstream version! If you decide to install your distros version and you run into problems, as a first step you should switch to upstream." The lead contributor also seems to have closed an issue against the 'latest' vagrant on CentOS 7 a few days ago [1].
Just thought I'd mention it, but I agree that the compatibility table suggests the earlier versions would be more stable. Additionally, I don't use libvirt anyway, so I will be quiet now :)
[1] https://github.com/vagrant-libvirt/vagrant-libvirt/issues/772
-
Laurentiu Pancescu -
Michael Vermaes -
Pavel Valena