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 637986 [details]
## Logs vdsm, rhevm, screen-shots

Description of problem: Summary: Threads leakage after failure of storage domain 


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

RHEVM: rhevm-3.1.0-25.el6ev.noarch
VDSM: vdsm-4.9.6-40.0.el6_3.x86_64
LIBVIRT: libvirt-0.9.10-21.el6_3.5.x86_64
QEMU & KVM: qemu-kvm-rhev-0.12.1.2-2.295.el6_3.4.x86_64
SANLOCK: sanlock-2.3-4.el6_3.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create iSCSI DC with one Host and one SD
2. Create a VM with OS installed (in my case was VM with RHEL 6.3, and VirtIO disk)
3. Run a VM
4. Create a Live-Snapshot 
5. Wait when disks VM in “Locked” state
6. Block via IpTables SD connection 
7. Wait when Host on “Non Responsive” state
8. Remove restriction from IpTables
  
Actual results:
After 2 hours, no more free threads
Disks VM in “Locked” state 
Snapshot on Locked state

Expected results:
System need handler with SD disconnection, and know to recover from this state

Additional info:

[root@cougar08 ~]# 
ps auxH | awk '/vdsm/ {print $1}' |grep vdsm | wc -l
4096

patch posted upstream:
http://gerrit.ovirt.org/#/c/8980/

Verified on RHEVM 3.1 - SI24

RHEVM: rhevm-3.1.0-28.el6ev.noarch
VDSM: vdsm-4.9.6-42.0.el6_3.x86_64
LIBVIRT: libvirt-0.9.10-21.el6_3.5.x86_64
QEMU & KVM: qemu-kvm-rhev-0.12.1.2-2.295.el6_3.5.x86_64
SANLOCK: sanlock-2.3-4.el6_3.x86_64

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/RHSA-2012-1508.html