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.

Description of problem:

case: connectStoragePool doesn't return on host & and host recovery fails
cause: several vdsm sudo sub-procosses left in defunct state which stuck other threads work


root      8102  0.0  0.0  51048  1904 ?        S<   16:00   0:00 /usr/bin/sudo -n /usr/bin/python /usr/share/vdsm/supervdsmServer.pyc 3e57466d-f015-4686-bea5-d91b291b1296 8063
root     28573  0.0  0.0      0     0 ?        Z<   17:03   0:00 [sudo] <defunct>
root     29226  0.0  0.0      0     0 ?        Z<   17:04   0:00 [sudo] <defunct>
root     29675  0.0  0.0      0     0 ?        Z<   17:04   0:00 [sudo] <defunct>
root     29796  0.0  0.0      0     0 ?        Z<   17:04   0:00 [sudo] <defunct>
root     31861  0.0  0.0      0     0 ?        Z<   17:04   0:00 [sudo] <defunct>
root     32113  0.0  0.0      0     0 ?        Z<   17:04   0:00 [sudo] <defunct>

reproducer: not easy
repro steps:

1) VMs are running 
2) logout from iscsi-session 
3) restart VDSM

see attached logs

not sure if its a regression.

It's likely that recent patches already fixed this bug. Please try to reproduce it with latest vdsm (>77)

After two weeks with no answer or reproduction, closing.