Bug 683990

Summary: If replication fails while setting up a clone it will wait forever
Product: [Retired] Dogtag Certificate System Reporter: Rob Crittenden <rcritten>
Component: Installation WizardAssignee: Ade Lee <alee>
Status: CLOSED EOL QA Contact: Ben Levenson <benl>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0CC: dpal, mharmsen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 726785 (view as bug list) Environment:
Last Closed: 2020-03-27 18:37:49 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:    
Bug Blocks: 530474, 688225, 726785    

Description Rob Crittenden 2011-03-10 21:11:38 UTC 
Description of problem:

I have been trying to set up replication in a clone to use TLS. Doing so during the initial set up requires care so your 389-ds instance comes pre-configured with a set of certificates.

If this is done incorrectly, such as not properly trusting the CA or not restarting 389-ds after configuring the NSS database and adding the SSL config, the initial replication setup will fail.

dogtag does not detect this failure, it just loops looking for the root to appear in the directory server, which it never will because replication is not working.

Rich Megginson says that the agreement status can be monitored to detect this kind of error.
Comment 1 Ade Lee 2011-08-04 18:48:04 UTC 
Patch and checkin in cloned bug:

https://bugzilla.redhat.com/show_bug.cgi?id=726785