Bug 1833024 - Upstream vagrant and vagrant-libvirt plugin fail due to ruby-libvirt load error
Summary: Upstream vagrant and vagrant-libvirt plugin fail due to ruby-libvirt load error
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-ruby-libvirt
Version: 32
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Vít Ondruch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-07 16:45 UTC by Brad Smith
Modified: 2020-05-07 20:42 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-07 18:13:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Brad Smith 2020-05-07 16:45:14 UTC
Description of problem: Vagrnt-libvirt plugin fails to run with upstream vagrant (2.2.7 and 2.2.8) due to a load error reported by ruby-libvirt gem


Version-Release number of selected component (if applicable):
libvirt version: 6.1.0, package: 2.fc32

[bgsmith@pico ~]$ vagrant version; vagrant plugin list
Installed Version: 2.2.8
Latest Version: 2.2.8
 
You're running an up-to-date version of Vagrant!
vagrant-libvirt (0.0.45, global)


How reproducible:
100 % failure to run

Steps to Reproduce:
1. Install upstream vagrant
2. Install libvirt-plugin according to directions on github
3. Run vagrant using libvirt as provider

Actual results:
vagrant up --provider=libvirt
Bringing machine 'fcserver' up with 'libvirt' provider...
/opt/vagrant/embedded/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require': /usr/lib64/libk5crypto.so.3: undefined symbol: EVP_KDF_ctrl, version OPENSSL_1_1_1b - /home/rbelgrave/.vagrant.d/gems/2.4.9/gems/ruby-libvirt-0.7.1/lib/_libvirt.so (LoadError)


Expected results:
Running vm in vagrant 

Additional info:

See this issue on github for more info https://github.com/vagrant-libvirt/vagrant-libvirt/issues/1105#issue-612216895

Comment 1 Vít Ondruch 2020-05-07 18:13:00 UTC
It seems that the upstream Vagrant is not compatible with the Fedora version of OpenSSL. I don't think I can do anything about it. Ask upstream please. Closing now. Feel free to reopen.

Comment 2 Brad Smith 2020-05-07 20:42:50 UTC
Thank you for the quick response and recommendation.

Brad


Note You need to log in before you can comment on or make changes to this bug.