Bug 2124214

Summary: schema compat plugin deadlock on delete post op
Product: Red Hat Enterprise Linux 8 Reporter: Anton Bobrov <abobrov>
Component: slapi-nisAssignee: Alexander Bokovoy <abokovoy>
Status: CLOSED MIGRATED QA Contact: ipa-qe
Severity: high Docs Contact:
Priority: high    
Version: 8.6CC: abokovoy, cilmar, dcamilof, frenaud, ftrivino, gkaihoro, msauton, pasik, progier, rcritten, tbordaz, tmihinto, tscherf
Target Milestone: rcKeywords: MigratedToJIRA, Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-19 15:16:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Anton Bobrov 2022-09-05 10:01:11 UTC
Description of problem:

The IPA schema compat plugin for RHDS deadlocks on delete post op. One thread is trying to acquire a write lock while in delete post op while several other threads are trying to acquire read locks in bind ops. It is not clear which thread is actually holding the lock/s. No FATAL error messages are reported in the logs for lock/unlock API. Because of this issue the RHDS gets into a "hang" like state where it is not responsive to operations which is obviously a problem. There is one thread that is doing post op plugin ops for add op tho it is not in schema compat plugin. And there are a few threads that just stuck in backend search ops inside bdb code likely because the locks they need are held by thread/s stuck in schema compat plugin operations. 

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

OS: Red Hat Enterprise Linux release 8.6 (Ootpa)
     Kernel: 4.18.0-372.13.1.el8_6.x86_64

389-ds: 1.4.3.28-6

IPA: 4.9.8-7


How reproducible:

We do not have a local lab reproducer however it happens fairly often on a customer system (just one specific master).


Additional info:

We havent gathered any RHDS PLUGIN level logs as it does not look like they would be of much help to debug this. I see there is DEBUG_MAP_LOCK flag that can be helpful however there doesnt seem to be any way to enable it dynamically. Unless this is a known issue or someone familiar with the related code can pin it as is a debug build with DEBUG_MAP_LOCK enabled is probably the next step to do.

Comment 27 Pierre Rogier 2023-08-11 08:51:36 UTC
*** Bug 2211904 has been marked as a duplicate of this bug. ***

Comment 28 Pierre Rogier 2023-08-11 09:00:27 UTC
*** Bug 2218887 has been marked as a duplicate of this bug. ***

Comment 34 RHEL Program Management 2023-09-19 15:11:23 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 35 RHEL Program Management 2023-09-19 15:16:32 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.