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:

If you kill rgmanager at just the right time during event processing during startup, it can throw errors in to the logs:

Oct 18 15:26:30 snap rgmanager[15382]: Shutting down
Oct 18 15:26:30 snap rgmanager[15382]: Stopping service service:b
Oct 18 15:26:30 snap rgmanager[15382]: Service service:b is stopped
Oct 18 15:26:30 snap rgmanager[15382]: #45: Unable to obtain cluster lock: Bad file descriptor
Oct 18 15:26:30 snap rgmanager[15382]: #50: Unable to obtain cluster lock: Bad file descriptor
Oct 18 15:26:30 snap rgmanager[15382]: #13: Service service:wtf failed to stop cleanly
Oct 18 15:26:30 snap rgmanager[15382]: #55: Unable to obtain cluster lock: Bad file descriptor

Version-Release number of selected component (if applicable): 3.0.12.1-4.el6

How reproducible: 10%

Steps to Reproduce:
1.  service rgmanager start
2.  sleep 8
3.  service rgmanager stop
  
Actual results: Errors in logs.  This occurs because we close the lockspace while other threads are trying to acquire locks.

Expected results: No errors, clean shutdown.

Additional info: This does not look like a high-risk condition, but it is a lot of noise.

Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.