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.

Bug 1440654

Summary: Possible deadlock while installing an ipa replica.
Product: Red Hat Enterprise Linux 7 Reporter: Jaroslav Reznik <jreznik>
Component: 389-ds-baseAssignee: mreynolds
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: urgent Docs Contact: Marc Muehlfeld <mmuehlfe>
Priority: urgent    
Version: 7.3CC: afarley, gparente, lkrispen, mreynolds, msauton, nkinder, rmeggins, spichugi, tbordaz, tmihinto, tscherf
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 389-ds-base-1.3.5.10-21.el7_3 Doc Type: Bug Fix
Doc Text:
The replica data structure is protected by a lock. Previously, if the first direct update on the server failed, a thread that acquired the lock did not released it. Consequently, the server could no longer use the replica data structure and further read and write requests hung. A patch has been applied to release the lock in the mentioned scenario. As a result, the server now works correctly if the first direct update failed.
Story Points: ---
Clone Of: 1432016 Environment:
Last Closed: 2017-05-25 15:52:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1432016    
Bug Blocks:    

Description Jaroslav Reznik 2017-04-10 08:12:33 UTC
This bug has been copied from bug #1432016 and has been proposed
to be backported to 7.3 z-stream (EUS).

Comment 5 Simon Pichugin 2017-05-09 15:51:54 UTC
Build tested:
389-ds-base-1.3.5.10-21.el7_3.x86_64
ipa-server-4.4.0-14.el7_3.7.x86_64


Verification steps:
1. Install IPA server on one machine
2. Install IPA replica on another machine.
ipa-replica-install should be successful:
[root@vm-idm-003 ~]# ipa-replica-install
WARNING: conflicting time&date synchronization service 'chronyd' will
be disabled in favor of ntpd

Password for admin.BOS.REDHAT.COM:
Run connection check to master
Connection check OK

[...]

Upgrading IPA:
  [1/9]: stopping directory server
  [2/9]: saving configuration
  [3/9]: disabling listeners
  [4/9]: enabling DS global lock
  [5/9]: starting directory server
  [6/9]: upgrading server
  [7/9]: stopping directory server
  [8/9]: restoring configuration
  [9/9]: starting directory server
Done.
Configuring ipa-otpd
  [1/2]: starting ipa-otpd
  [2/2]: configuring ipa-otpd to start on boot
Done configuring ipa-otpd.

3. Check ipa.service status:
[root@qe-blade-13 ~]# service ipa status
Redirecting to /bin/systemctl status  ipa.service
● ipa.service - Identity, Policy, Audit
   Loaded: loaded (/usr/lib/systemd/system/ipa.service; enabled; vendor preset: disabled)
   Active: active (exited) since Tue 2017-05-09 11:47:01 EDT; 2min 11s ago
  Process: 31320 ExecStart=/usr/sbin/ipactl start (code=exited, status=0/SUCCESS)
 Main PID: 31320 (code=exited, status=0/SUCCESS)

[...]

May 09 11:47:01 qe-blade-13.idmqe.lab.eng.bos.redhat.com systemd[1]: Started Identity, Poli...
Hint: Some lines were ellipsized, use -l to show in full.


Result. IPA replica was successfully installed and no deadlock has happened.
Marking as verified.

Comment 7 errata-xmlrpc 2017-05-25 15:52:46 UTC
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.

https://access.redhat.com/errata/RHBA-2017:1313