No regression here. The error code is not specific enough, that's all.

http://gerrit.usersys.redhat.com/#change,441

verified on ic119
vdsm-4.9-70.el6.x86_64


2011-05-30 11:38:36,004 ERROR [com.redhat.rhevm.vdsbroker.vdsbroker.BrokerCommandBase] (http-0.0.0.0-8443-1) Error code noVM and error message VDSGenericException: VDSErrorException: Failed to SetVmTicketVDS, error = Virtual machine does not exist
2011-05-30 11:38:36,005 INFO  [com.redhat.rhevm.vdsbroker.vdsbroker.BrokerCommandBase] (http-0.0.0.0-8443-1) Command com.redhat.rhevm.vdsbroker.vdsbroker.SetVmTicketVDSCommand return value 
 Class Name: com.redhat.rhevm.vdsbroker.vdsbroker.StatusOnlyReturnForXmlRpc
mStatus                       Class Name: com.redhat.rhevm.vdsbroker.vdsbroker.StatusForXmlRpc
mCode                         1
mMessage                      Virtual machine does not exist

hread-34160::ERROR::2011-05-30 11:35:59,064::clientIF::58::vds::(wrapper) Traceback (most recent call last):
  File "/usr/share/vdsm/clientIF.py", line 54, in wrapper
    res = f(*args, **kwargs)
  File "/usr/share/vdsm/clientIF.py", line 421, in setVmTicket
    return vm.setTicket(otp, seconds, connAct)
  File "/usr/share/vdsm/libvirtvm.py", line 1046, in setTicket
    graphics = xml.dom.minidom.parseString(self._dom.XMLDesc(0)) \
  File "/usr/share/vdsm/libvirtvm.py", line 295, in f
    ret = attr(*args, **kwargs)
  File "/usr/share/vdsm/libvirtconnection.py", line 59, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 239, in XMLDesc
    if ret is None: raise libvirtError ('virDomainGetXMLDesc() failed', dom=self)
libvirtError: Domain not found: no domain with matching uuid '893188aa-7f42-4252-92fb-550c85f305f0'

Thread-34159::DEBUG::2011-05-30 11:35:59,118::lvm::359::Storage.Misc.excCmd::(cmd) SUCCESS: <err> = ''; <rc> = 0
Thread-34159::DEBUG::2011-05-30 11:35:59,129::lvm::482::OperationMutex::(_reloadlvs) Operation 'lvm reload operation' released the operation mutex

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2011-1782.html