Bug 1028667 - Another random libvirt failure: "could not destroy libvirt domain: Domain not found: no domain with matching uuid"
Summary: Another random libvirt failure: "could not destroy libvirt domain: Domain not...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: TRACKER-bugs-affecting-libguestfs
TreeView+ depends on / blocked
 
Reported: 2013-11-09 09:36 UTC by Richard W.M. Jones
Modified: 2016-04-10 15:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-10 15:12:02 UTC


Attachments (Terms of Use)
~/.cache/libvirt/qemu/log/guestfs-um8kjsm37joctrs6.log (2.92 KB, text/plain)
2013-11-09 09:36 UTC, Richard W.M. Jones
no flags Details

Description Richard W.M. Jones 2013-11-09 09:36:37 UTC
Created attachment 821859 [details]
~/.cache/libvirt/qemu/log/guestfs-um8kjsm37joctrs6.log

Description of problem:

libvirt failed randomly again:

$ ./run ./builder/virt-builder fedora-19 --format=qcow2 --size=10G
[   0.0] Downloading: file:///home/rjones/d/libguestfs/builder/website/fedora-19.xz
[   1.0] Creating disk image: fedora-19.qcow2
[   1.0] Uncompressing: file:///home/rjones/d/libguestfs/builder/website/fedora-19.xz
[  14.0] Running virt-resize to expand the disk to 10.0G
Fatal error: exception Guestfs.Error("could not destroy libvirt domain: Domain not found: no domain with matching uuid '120761a0-fd2a-46e6-bc37-c2d943196dee' (guestfs-um8kjsm37joctrs6) [code=42 domain=10]")
virt-builder: error: virt-resize failed

Please make libvirt robust so we can depend on it not
failing randomly.

Version-Release number of selected component (if applicable):

libvirt-daemon-1.1.3-2.fc21.x86_64

How reproducible:

Unknown, only seen once.

Steps to Reproduce:
1. Unknown.

Comment 1 Cole Robinson 2016-04-10 15:12:02 UTC
Unfortunately there really isn't much actionable here, given it was a random failure and the age of the bug. Closing as DEFERRED but Rich if this is something you still see on occasion please reopen


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