Bug 1384785
| Summary: | Replica install fails with old IPA master sometimes during replication process | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Marcel Kolaja <mkolaja> |
| Component: | 389-ds-base | Assignee: | Noriko Hosoi <nhosoi> |
| Status: | CLOSED ERRATA | QA Contact: | Viktor Ashirov <vashirov> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.3 | CC: | anazmy, gagriogi, gparente, ksiddiqu, mkolaja, mmuehlfe, msauton, nhosoi, nkinder, pvoborni, rcritten, rmeggins, tbordaz, vonsch |
| Target Milestone: | rc | Keywords: | Regression, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 389-ds-base-1.3.5.10-12.el7_3 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, Identity Management closed the replication connection in the following scenario: The supplier has the "389-ds-base 1.2.11" package installed on Red Hat Enterprise Linux 6 and the consumer runs the 1.3.4 version or newer. Additionally, the supplier sends a custom schema to the consumer, that is a subset of the custom schema of the consumer. If all conditions met, the schema replication failed and as a consequence, no data is replicated. To fix the problem, the schema replication failure event has been changed from "FATAL" to "NOT FATAL". As a result, a failed schema replication process no longer interrupts the data replication.
|
Story Points: | --- |
| Clone Of: | 1377730 | Environment: | |
| Last Closed: | 2016-12-06 17:03:55 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: | 1377730, 1385300 | ||
| Bug Blocks: | 1378353 | ||
|
Description
Marcel Kolaja
2016-10-14 07:24:07 UTC
*** Bug 1385300 has been marked as a duplicate of this bug. *** Marking as VERIFIED based on https://bugzilla.redhat.com/show_bug.cgi?id=1389434#c6 (Thanks Kaleem!) 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://rhn.redhat.com/errata/RHBA-2016-2879.html |