Bug 1502238

Summary: The provider 'libvirt' could not be found
Product: [Fedora] Fedora Reporter: Pierguido Lambri <plambri>
Component: vagrant-libvirtAssignee: Pavel Valena <pvalena>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: lmohanty, madam, mnk, pvalena, strzibny, thrcka, vondruch
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: vagrant-1.9.8-2.fc27 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-18 13:16:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Debug logs from 'vagrant up' none

Description Pierguido Lambri 2017-10-15 11:37:01 UTC
Description of problem:
Tried to install and run vagrant but I always get this error.


Version-Release number of selected component (if applicable):
vagrant-1.9.1-3.fc27.noarch
vagrant-libvirt-0.0.40-2.fc27.noarch


How reproducible:
Always


Steps to Reproduce:
1. Install vagrant
2. Run 'vagrant up' 


Actual results:
It returns the error in $SUBJECT

Expected results:
It should run without issues


Additional info:

Comment 1 Pierguido Lambri 2017-10-15 11:39:18 UTC
The installed packages are:

$ rpm -qa | grep vagrant                        
vagrant-sshfs-1.3.0-4.fc27.noarch                
vagrant-1.9.1-3.fc27.noarch                      
vagrant-libvirt-0.0.40-2.fc27.noarch             

Modules:

$ lsmod | grep kvm
kvm_intel             200704  0
kvm                   585728  1 kvm_intel
irqbypass              16384  1 kvm

Vagrant plugin output:

$ vagrant plugin list
vagrant-sshfs (1.3.0, system)

Comment 2 Pierguido Lambri 2017-10-15 11:40:36 UTC
Created attachment 1338809 [details]
Debug logs from 'vagrant up'

Comment 3 Pavel Valena 2017-10-16 15:29:18 UTC
Hello Pierguido,

please check if the issue persists with Vagrant 1.9.8. which is currently in testing repository:

https://bodhi.fedoraproject.org/updates/vagrant-1.9.8-1.fc27

Additionaly, please try installing '@vagrant' group.

Thank you for your report.

Comment 4 Pierguido Lambri 2017-10-16 16:40:46 UTC
Hello Pavel,

Yep, vagrant 1.9.8-1.fc27 seems to fix it:

# vagrant up                                                                                                               
Bringing machine 'frontend' up with 'libvirt' provider...
Bringing machine 'distgit' up with 'libvirt' provider...
Bringing machine 'backend' up with 'libvirt' provider...
==> frontend: An error occurred. The error will be shown after all tasks complete.
==> backend: An error occurred. The error will be shown after all tasks complete.
==> distgit: An error occurred. The error will be shown after all tasks complete.
An error occurred while executing multiple actions in parallel.
Any errors that occurred are shown below.
...

These errors are because I wasn't running polkit (I use i3 and I have to fix this).

Thanks for the quick response.

Comment 5 Pavel Valena 2017-10-16 16:47:32 UTC
I'm glad to hear that!

Comment 6 Fedora Update System 2017-10-16 16:48:46 UTC
vagrant-1.9.8-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-84cfa48781

Comment 7 Fedora Update System 2017-10-17 02:25:25 UTC
vagrant-1.9.8-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-84cfa48781

Comment 8 Fedora Update System 2017-11-25 02:34:52 UTC
vagrant-1.9.8-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.

Comment 9 Mathias Nicolajsen Kjærgaard 2017-12-15 19:12:21 UTC
I had the same problem with vagrant-1.9.8-1.fc27 and vagrant-libvirt-0.0.40-2.fc27 installed:

$ vagrant plugin list
No plugins installed.

Reinstalling vagrant-libvirt fixed the problem:

$ sudo rpm -e vagrant-libvirt; sudo dnf install -y vagrant-libvirt

$ vagrant plugin list
vagrant-libvirt (0.0.40, system)

Comment 10 Pavel Valena 2017-12-18 13:07:03 UTC
This was actually resolved in Bug 1523296.

Comment 11 Pavel Valena 2017-12-18 13:16:38 UTC

*** This bug has been marked as a duplicate of bug 1523296 ***