We have just seen libvirt ending up in an inconsistent state : a shut off transient domain.
 
Has anyone seen this before ?

We had a defined domain in shut off state
then
virsh shutdown domain &   # note this is sent to the background
virsh domstate domain
virsh destroy domain

at this point libvirtd.log reported

2014-06-05 00:47:52.000+0000: 10063: warning : qemuDomainObjBeginJobInternal:839 : Cannot start job (modify, none) for domain aspn-testapp5-Na6r; current job is (modify, none) owned by (10060, 0)

subsequently,
virsh undefine domain
-> then succeeded (exit 0)

but now virsh list still reports it :

virsh # list --all
 Id    Name                           State
----------------------------------------------------
 104   aspn-testapp5-Na6r             shut off

and it cannot be undefined any more as it is considered transient.

virsh # undefine aspn-testapp5-Na6r
error: Failed to undefine domain aspn-testapp5-Na6r
error: Requested operation is not valid: cannot undefine transient domain

Compiled against library: libvirt 0.10.2
Using library: libvirt 0.10.2
Using API: QEMU 0.10.2
Running hypervisor: QEMU 0.12.1

running on RHEL 6.2 updated with RHEL 6.4 packages : libvirt.x86_64 0.10.2-18.el6_4.9

--------------------------------------------------
Edoardo Comar
WebSphere Application Service Platform for Networks (ASPN)
ecomar@uk.ibm.com
+44 (0)1962 81 5576
IBM UK Ltd, Hursley Park, SO21 2JN

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU