Invalid UUID (Libvirt::RetrieveError)

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Invalid UUID (Libvirt::RetrieveError)

D Rhodes
I had a crash while a vagrant/libvirt machine was being constructed. It is now listed in global-status as preparing, but any other commands fail with the exception below.

Is there a manual way to remove this machine and/or remnants?

Thanks!

stack@opcoast-ryzen ~/cord/build $ vagrant status
/opt/stack/.vagrant.d/gems/2.2.5/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_domains.rb:9:in `lookup_domain_by_uuid': Call to virDomainLookupByUUID failed: Invalid UUID (Libvirt::RetrieveError)
    from /opt/stack/.vagrant.d/gems/2.2.5/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_domains.rb:9:in `list_domains'
    from /opt/stack/.vagrant.d/gems/2.2.5/gems/fog-libvirt-0.0.3/lib/fog/libvirt/models/compute/servers.rb:15:in `get'
    from /opt/stack/.vagrant.d/gems/2.2.5/gems/vagrant-libvirt-0.0.35/lib/vagrant-libvirt/driver.rb:53:in `get_domain'
    from /opt/stack/.vagrant.d/gems/2.2.5/gems/vagrant-libvirt-0.0.35/lib/vagrant-libvirt/driver.rb:67:in `created?'
    from /opt/stack/.vagrant.d/gems/2.2.5/gems/vagrant-libvirt-0.0.35/lib/vagrant-libvirt/provider.rb:101:in `state'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/machine.rb:506:in `state'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/machine.rb:145:in `initialize'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/vagrantfile.rb:79:in `new'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/vagrantfile.rb:79:in `machine'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/environment.rb:669:in `machine'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/plugin/v2/command.rb:177:in `block in with_target_vms'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/plugin/v2/command.rb:210:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/plugin/v2/command.rb:210:in `block in with_target_vms'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/plugin/v2/command.rb:209:in `map'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/plugin/v2/command.rb:209:in `with_target_vms'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/commands/status/command.rb:20:in `execute'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/cli.rb:42:in `execute'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/environment.rb:308:in `cli'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/bin/vagrant:127:in `<main>'
stack@opcoast-ryzen ~/cord/build $ vagrant global-status
id       name           provider state     directory                          
-------------------------------------------------------------------------------
f261ba1  corddev        libvirt running   /opt/stack/cord/build              
53a16c6  prod           libvirt running   /opt/stack/cord/build              
b22a9d3  leaf-1         libvirt running   /opt/stack/cord/build              
bcb492c  leaf-2         libvirt running   /opt/stack/cord/build              
ac8a9ac  spine-1        libvirt running   /opt/stack/cord/build              
3c0e1cb  compute-node-1 libvirt preparing /opt/stack/cord/build              
 
The above shows information about all known Vagrant environments
on this machine. This data is cached and may not be completely
up-to-date. To interact with any of the machines, you can go to
that directory and run Vagrant, or you can use the ID directly
with Vagrant commands from any directory. For example:
"vagrant destroy 1a2b3c4d"

stack@opcoast-ryzen ~/cord/build $ vagrant destroy compute-node-1
/opt/stack/.vagrant.d/gems/2.2.5/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_domains.rb:9:in `lookup_domain_by_uuid': Call to virDomainLookupByUUID failed: Invalid UUID (Libvirt::RetrieveError)
    from /opt/stack/.vagrant.d/gems/2.2.5/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_domains.rb:9:in `list_domains'
    from /opt/stack/.vagrant.d/gems/2.2.5/gems/fog-libvirt-0.0.3/lib/fog/libvirt/models/compute/servers.rb:15:in `get'
    from /opt/stack/.vagrant.d/gems/2.2.5/gems/vagrant-libvirt-0.0.35/lib/vagrant-libvirt/driver.rb:53:in `get_domain'
    from /opt/stack/.vagrant.d/gems/2.2.5/gems/vagrant-libvirt-0.0.35/lib/vagrant-libvirt/driver.rb:67:in `created?'
    from /opt/stack/.vagrant.d/gems/2.2.5/gems/vagrant-libvirt-0.0.35/lib/vagrant-libvirt/provider.rb:101:in `state'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/machine.rb:506:in `state'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/machine.rb:145:in `initialize'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/vagrantfile.rb:79:in `new'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/vagrantfile.rb:79:in `machine'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/environment.rb:669:in `machine'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/plugin/v2/command.rb:177:in `block in with_target_vms'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/plugin/v2/command.rb:201:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/plugin/v2/command.rb:201:in `block in with_target_vms'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/plugin/v2/command.rb:183:in `each'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/plugin/v2/command.rb:183:in `with_target_vms'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/commands/destroy/command.rb:30:in `execute'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/cli.rb:42:in `execute'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/environment.rb:308:in `cli'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.9.3/bin/vagrant:127:in `<main>'

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/1a509be4-47bc-430f-acdf-c511b4726743%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Invalid UUID (Libvirt::RetrieveError)

D Rhodes
Nevermind, I found the answer: here

But I'll leave the post in case it helps others?

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/4592bfac-18a0-49cd-ab67-41c520181810%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.