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 493481[details]
vdsm.log
Description of problem:
When running rhel6 host in 2.3 cluster in DC 2.2, vdsm is running a few processes on the host. If the parent of those processes is killed, child processes become orphans and keep runnning. Note that DC 2.2 is important in this case, in DC 2.3 there is not that amount of processes.
Version-Release number of selected component (if applicable):
ic114
vdsm-4.9-60.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Have rhel6.x host in DC2.2
2. Kill vdsm
3. Check running vdsm processes
Actual results:
Watchdog revives vdsmd and new duplicit processes are created
Expected results:
Oprhan processes dies with it's parent or are cleaned at new vdsm start
Additional info:
gdb of one of orphan processes
pystack
/usr/share/vdsm/storage/processPool.py (124): _helperMainLoop
/usr/share/vdsm/storage/processPool.py (124): _helperMainLoop
/usr/lib64/python2.6/multiprocessing/process.py (83): run
/usr/lib64/python2.6/multiprocessing/process.py (215): _bootstrap
/usr/lib64/python2.6/multiprocessing/forking.py (89): __init__
/usr/lib64/python2.6/multiprocessing/forking.py (89): __init__
/usr/lib64/python2.6/multiprocessing/process.py (90): start
/usr/share/vdsm/storage/processPool.py (97): __init__
/usr/share/vdsm/storage/processPool.py (97): __init__
/usr/share/vdsm/storage/processPool.py (38): runExternally
/usr/share/vdsm/storage/processPool.py (38): runExternally
/usr/share/vdsm/storage/processPool.py (33): wrapper
/usr/share/vdsm/storage/processPool.py (33): wrapper
/usr/share/vdsm/storage/nfsSD.py (134): collectMetaFiles
/usr/share/vdsm/storage/nfsSD.py (134): collectMetaFiles
/usr/share/vdsm/storage/misc.py (1112): wrapper
/usr/share/vdsm/storage/misc.py (1112): wrapper
/usr/lib64/python2.6/threading.py (481): run
/usr/lib64/python2.6/threading.py (513): __bootstrap_inner
/usr/lib64/python2.6/threading.py (490): __bootstrap
/usr/lib64/python2.6/threading.py (490): __bootstrap
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
Created attachment 493481 [details] vdsm.log Description of problem: When running rhel6 host in 2.3 cluster in DC 2.2, vdsm is running a few processes on the host. If the parent of those processes is killed, child processes become orphans and keep runnning. Note that DC 2.2 is important in this case, in DC 2.3 there is not that amount of processes. Version-Release number of selected component (if applicable): ic114 vdsm-4.9-60.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Have rhel6.x host in DC2.2 2. Kill vdsm 3. Check running vdsm processes Actual results: Watchdog revives vdsmd and new duplicit processes are created Expected results: Oprhan processes dies with it's parent or are cleaned at new vdsm start Additional info: gdb of one of orphan processes pystack /usr/share/vdsm/storage/processPool.py (124): _helperMainLoop /usr/share/vdsm/storage/processPool.py (124): _helperMainLoop /usr/lib64/python2.6/multiprocessing/process.py (83): run /usr/lib64/python2.6/multiprocessing/process.py (215): _bootstrap /usr/lib64/python2.6/multiprocessing/forking.py (89): __init__ /usr/lib64/python2.6/multiprocessing/forking.py (89): __init__ /usr/lib64/python2.6/multiprocessing/process.py (90): start /usr/share/vdsm/storage/processPool.py (97): __init__ /usr/share/vdsm/storage/processPool.py (97): __init__ /usr/share/vdsm/storage/processPool.py (38): runExternally /usr/share/vdsm/storage/processPool.py (38): runExternally /usr/share/vdsm/storage/processPool.py (33): wrapper /usr/share/vdsm/storage/processPool.py (33): wrapper /usr/share/vdsm/storage/nfsSD.py (134): collectMetaFiles /usr/share/vdsm/storage/nfsSD.py (134): collectMetaFiles /usr/share/vdsm/storage/misc.py (1112): wrapper /usr/share/vdsm/storage/misc.py (1112): wrapper /usr/lib64/python2.6/threading.py (481): run /usr/lib64/python2.6/threading.py (513): __bootstrap_inner /usr/lib64/python2.6/threading.py (490): __bootstrap /usr/lib64/python2.6/threading.py (490): __bootstrap