Description of problem: Replication UI most of the time don't return consumer initialization error Version-Release number of selected component (if applicable): DS 7.1 SP1 How reproducible: Most of the time Steps to Reproduce: 1. Setup replication agreement through console. Make it such that the bind DN or passwd is wrong, or the consumer is another Master, such that the initialization will always fail. 2. Pick to initialize consumer now. 3. More often than not when user click on Done button on the Summary dialog, a dialog with "Consumer Initialization Started" title comes up stating the initialization has been successfully started. Only once in a while do I actually get the expected error dialog. Not sure why this inconsistency happens.
*** Bug 200989 has been marked as a duplicate of this bug. ***
Created attachment 327021 [details] diffs
Created attachment 327025 [details] cvs commit log Reviewed by: nkinder (Thanks!) Fix Description: Just added a 3 second sleep after telling the server to perform the consumer init. This seems to give the server time enough to attempt the init, fail, and set an appropriate error code. Platforms tested: RHEL5 Flag Day: no Doc impact: no
fix verified: RHEL5 Repeated attempts to add a new agreement with invalid credentials all produced errors on initialization.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-0455.html