Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 510099 [details]
vdsm log

Description of problem:
when killing a vm stats Thread gets "libvirtError: Domain not found" and still keeps on running.

Thread-56159::ERROR::2011-06-27 15:22:19,117::utils::371::vm.Vm::(collect) vmId=`0f6e0767-272e-4739-a963-b164dc08c43f`::Stats function failed: 
...
libvirtError: Domain not found: no domain with matching uuid '0f6e0767-272e-4739-a963-b164dc08c43f'


Thread-56159::ERROR::2011-06-27 15:22:24,121::utils::371::vm.Vm::(collect) vmId=`0f6e0767-272e-4739-a963-b164dc08c43f`::Stats function failed: <AdvancedStatsFunction _sampleNet at 0x24a13b0>
....
libvirtError: Domain not found: no domain with matching uuid '0f6e0767-272e-4739-a963-b164dc08c43f'


Version-Release number of selected component (if applicable):
vdsm-4.9-76.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.kill -9 qemu process 
  
Actual results:
vdsm keeps on trying to get statistics on a killed vm.

Expected results:
vdsm should stop stats thread when getting VIR_ERR_NO_DOMAIN (42)

Additional info:
full log attached

Could it be that this was fixed by:

Related to BZ#705297: have a single virEventLoopPure thread
http://gerrit.usersys.redhat.com/625

It doesn't reproduce after applying the patch.

for a moment I thought that it could have nice if the stats thread knew that it should not continue polling after the domain no longer exists. but I'm not sure at all about it, and as you say - the underlying issue of lost events is solved. let's close.