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
Does not install on Fedora 32 #1105
Comments
Figured it out.
Note the |
Hmm actually now vagrant up is failing with this
|
I have the same problem with the upstream vagrant 2.2.8 from Hashicorp on Fedora 32. I found a similar error for matlab (see https://www.mathworks.com/matlabcentral/answers/514366-error-while-installing-matlab-r2020a-on-fedora-32). The hack used there does not resolve the vagrant problem that i can find. |
Same problem here... |
My attempt to capture this as a bug with RedHat Bugzilla for Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1833024 Not sure what will happen. |
I think the problem is that Ruby in Vagrant is build against bundled version of OpenSSL while during vagrant-libvirt installation, the system version of OpenSSL is used and later they clash. The configure args are hardly correct. They should refer to vagrant libraries, not to the system. This won't happen with Fedora version of Vagrant. |
@voxik - thanks. I was using the configure args as recommended by the vagrant-libvirt readme when running into installation problems. Do you have a recommended change to CONFIGURE_ARGS? |
Please see the solution in this thread: hashicorp/vagrant#11020 (comment). |
The readme has been updated with the steps needed in #1107 that appear to work as described. |
Steps to reproduce
vagrant plugin install vagrant-libvirt
Expected behaviour
Plugin should install
Actual behaviour
System configuration
OS/Distro version:: Fedora 32
Libvirt version: libvirtd (libvirt) 6.1.0
Output of
vagrant version; vagrant plugin list
:Are you using upstream vagrant package or your distros package?
Upstream
I saw a few similar issues on this repo but none of them seem to have this specific error.
The text was updated successfully, but these errors were encountered: