Bug 1374325
| Summary: | "The provider 'libvirt' could not be found" even when vagrant-libvirt is installed | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tomas Tomecek <ttomecek> |
| Component: | vagrant-libvirt | Assignee: | Vít Ondruch <vondruch> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | dima85, lmohanty, madam, pvalena, rbhupathi, strzibny, vondruch |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-09-12 12:49:16 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: | |||
|
Description
Tomas Tomecek
2016-09-08 12:48:48 UTC
(In reply to Tomas Tomecek from comment #0) > Vagrant can't start my VM with libvirt provider: > > ``` > $ vagrant plugin list > No plugins installed. This looks suspicious. Here is the output on my system: ``` $ vagrant plugin list vagrant-libvirt (0.0.33, system) ``` I suspect that re-installation of vagrant-libvirt will fix the issue for you, but how that happened? You probably don't remember any scriptlet failures during system update or something like that ... Thanks! Reinstallation fixed it. Unfortunately I don't. Checking logs, nothing. I guess we can close. This is still a bug. I am on SuSE Leap 42.2 and I installed vagrant and installed the plugin for libvirt as well and the vagrant plugin list shows it. vagrant plugin list vagrant-libvirt (0.0.40) vagrant-share (1.1.6, system) However when I try to bring up any instance , I get the error and it says it cannot find any provider libvirtd vagrant up The provider 'libvirtd' could not be found, but was requested to back the machine 'admin'. Please use a provider that exists. (In reply to Rama Krishna from comment #3) > This is still a bug. I am on SuSE Leap 42.2 and I installed vagrant and > installed the plugin for libvirt as well and the vagrant plugin list shows > it. > > vagrant plugin list > vagrant-libvirt (0.0.40) > vagrant-share (1.1.6, system) > > However when I try to bring up any instance , I get the error and it says it > cannot find any provider libvirtd > > vagrant up > The provider 'libvirtd' could not be found, but was requested to > back the machine 'admin'. Please use a provider that exists. I reinstalled the plugin several times and gave up. Same issue as before. (In reply to Rama Krishna from comment #3) > The provider 'libvirtd' could not be found libvirtd? Where is the 'd' coming from? It should be just 'libvirt' if I am not mistaken ... (In reply to Vít Ondruch from comment #5) > (In reply to Rama Krishna from comment #3) > > The provider 'libvirtd' could not be found > > libvirtd? Where is the 'd' coming from? It should be just 'libvirt' if I am > not mistaken ... No clue where it is coming from. But the libvirt deamon is named libvitd. grep -R libvirtd */* gems/gems/ruby-libvirt-0.7.0/ext/libvirt/domain.c: * to make this domain autostart when libvirtd starts up. gems/gems/ruby-libvirt-0.7.0/ext/libvirt/network.c: * to determine if this network will be autostarted when libvirtd starts. gems/gems/ruby-libvirt-0.7.0/ext/libvirt/network.c: * to set this network to be autostarted when libvirtd starts. gems/gems/ruby-libvirt-0.7.0/ext/libvirt/storage.c: * to determine whether this storage pool will autostart when libvirtd starts. gems/gems/ruby-libvirt-0.7.0/ext/libvirt/storage.c: * to make this storage pool start when libvirtd starts. gems/gems/vagrant-libvirt-0.0.40/README.md:* `host` - The name of the server, where libvirtd is running gems/gems/vagrant-libvirt-0.0.40/example_box/Vagrantfile: # The name of the server, where libvirtd is running. gems/gems/vagrant-libvirt-0.0.40/lib/vagrant-libvirt/config.rb: # The name of the server, where libvirtd is running. rbhupathi@ramak-suse:~/.vagrant.d> ps -fe | grep libvirtd root 1268 1 0 Jul31 ? 00:00:00 /usr/sbin/libvirtd --listen rbhupat+ 31077 15104 0 22:58 pts/4 00:00:00 grep --color=auto libvirtd Well.. there is definitely a bug somewhere and I am stuck because I am cleaning up and reinstalling vagrant plugin repeatedly ,but to no avail. This is on SuSE Linux Leap 42.2 . If there is any cleanup I can do to restore it to pristine form, I will be happy to do it. --RamaK (In reply to Rama Krishna from comment #3) > This is still a bug. I am on SuSE Leap 42.2 This is a bug tracker for Fedora rawhide distribution. Please consult the issue in a bug tracker for your distribution. |