Bug 1645197

Summary: on-line re-initialization hangs [rhel-7.6.z]
Product: Red Hat Enterprise Linux 7 Reporter: Oneata Mircea Teodor <toneata>
Component: 389-ds-baseAssignee: thierry bordaz <tbordaz>
Status: CLOSED ERRATA QA Contact: RHDS QE <ds-qe-bugs>
Severity: high Docs Contact: Marc Muehlfeld <mmuehlfe>
Priority: high    
Version: 7.5CC: amsharma, gparente, lkrispen, mhonek, mreynolds, msauton, nkinder, rmeggins, spichugi, tbordaz, vashirov
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 389-ds-base-1.3.8.4-19.el7_6 Doc Type: Bug Fix
Doc Text:
During a total initialization, Directory Server retrieves the top suffix entry. Previously, the server assumed that the database ID of the suffix entry is "1". If the ID was different, the server failed to prepare the list of entries and the initialization hung. With this update, Directory Server provides the correct ID of the suffix to the routine that prepares the list of entries. As a result, a total initialization works successfully if the database ID of the suffix entry is different from "1".
 Story Points: ---
Clone Of: 1626375 Environment:
Last Closed: 2019-01-29 17:23:03 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: 1626375    
Bug Blocks:    
Attachments:
Description Flags
Automated test case none

Description Oneata Mircea Teodor 2018-11-01 15:35:55 UTC 
This bug has been copied from bug #1626375 and has been proposed to be backported to 7.6 z-stream (EUS).
Comment 6 Viktor Ashirov 2019-01-17 23:47:10 UTC 
Build tested: 389-ds-base-1.3.8.4-22.el7_6.x86_64

test_bz1626375.py::test_online_reinit_can_hang PASSED

Marking as VERIFIED.
Comment 7 Viktor Ashirov 2019-01-17 23:47:43 UTC 
Created attachment 1521387 [details]
Automated test case
Comment 9 errata-xmlrpc 2019-01-29 17:23:03 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-2019:0179