Hi, a very casual vagrant user here. I've been using a vagrant setup that
has worked for a couple of weeks up until a day or two ago. It is now
failing 100% of the time with the same error. Before trying to dig into it
beyond my cargo-cult understanding of the entire setup, I thought I'd ask
if this is an obvious error to the experienced vagrant user, perhaps a sign
of a login problem, cert expiration, netcat configuration or similar.
(virsh appears to be working fine.)
Vagrant is running in a docker container. The vagrant-libvirt plugin is
installed via a Dockerfile and appears to install cleanly:
Step 13 : RUN vagrant plugin install vagrant-libvirt
---> Running in 4c0de88cc36e
Installing the 'vagrant-libvirt' plugin. This can take a few minutes...
Installed the plugin 'vagrant-libvirt (0.0.26)'!
---> a2550df549c6
Removing intermediate container 4c0de88cc36e
Here is the log relating to this "libvirt is not a recognized compute
provider" error that I get on "vagrant up":
INFO host: Detected: linux!
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 1 hooks defined.
INFO runner: Running action: #<Vagrant::Action::Builder:0x00000002793f90>
INFO warden: Calling IN action:
#<Vagrant::Action::Builtin::ConfigValidate:0x0000000182be40>
INFO warden: Calling IN action:
#<VagrantPlugins::ProviderLibvirt::Action::ConnectLibvirt:0x0000000182bdc8>
INFO connect_libvirt: Connecting to Libvirt
(qemu+ssh://root@XXXXXXXXXXXXX/system?no_verify=1&keyfile=/root/.ssh/id_rsa)
...
ERROR warden: Error occurred: libvirt is not a recognized compute provider
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO environment: Released process lock:
machine-action-4e622f570939387af0e282d1988e87d2
INFO environment: Running hook: environment_unload
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 1 hooks defined.
INFO runner: Running action: #<Vagrant::Action::Builder:0x00000002909938>
/root/.vagrant.d/gems/gems/fog-core-1.30.0/lib/fog/compute.rb:66:in `new':
libvirt is not a recognized compute provider (ArgumentError)
from
/root/.vagrant.d/gems/gems/vagrant-libvirt-0.0.26/lib/vagrant-libvirt/action/connect_libvirt.rb:38:in
`call'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/warden.rb:34:in
`call'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/builtin/config_validate.rb:25:in
`call'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/warden.rb:34:in
`call'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/builder.rb:116:in
`call'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/runner.rb:66:in
`block in run'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/util/busy.rb:19:in
`busy'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/runner.rb:66:in
`run'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/machine.rb:214:in
`action_raw'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/machine.rb:191:in
`block in action'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:516:in
`lock'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/machine.rb:178:in
`call'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/machine.rb:178:in
`action'
from
/root/.vagrant.d/gems/gems/vagrant-libvirt-0.0.26/lib/vagrant-libvirt/provider.rb:70:in
`state'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/machine.rb:480:in
`state'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/machine.rb:141:in
`initialize'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/vagrantfile.rb:75:in
`new'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/vagrantfile.rb:75:in
`machine'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:614:in
`machine'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/plugin/v2/command.rb:168:in
`block in with_target_vms'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/plugin/v2/command.rb:192:in
`call'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/plugin/v2/command.rb:192:in
`block in with_target_vms'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/plugin/v2/command.rb:174:in
`each'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/plugin/v2/command.rb:174:in
`with_target_vms'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/plugins/commands/up/command.rb:74:in
`block in execute'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:277:in
`block (2 levels) in batch'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:275:in
`tap'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:275:in
`block in batch'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:274:in
`synchronize'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:274:in
`batch'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/plugins/commands/up/command.rb:58:in
`execute'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/cli.rb:42:in
`execute'
from
/opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:301:in
`cli'
from
/opt/vagrant/bin/../embedded/gems/gems/vagrant-1.7.2/bin/vagrant:174:in
`<main>'
Any advice appreciated,
Thanks.
-bruce
--
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
