Back to bug 1384785
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Ahmed Nazmy | 2016-10-16 05:00:22 UTC | Depends On | 1385300 | |
| Ahmed Nazmy | 2016-10-18 08:21:28 UTC | Blocks | 1378353 | |
| Nathan Kinder | 2016-10-20 15:52:28 UTC | Status | NEW | POST |
| Noriko Hosoi | 2016-10-31 21:29:12 UTC | Status | POST | MODIFIED |
| Fixed In Version | 389-ds-base-1.3.5.10-12.el7 | |||
| errata-xmlrpc | 2016-10-31 21:35:18 UTC | Status | MODIFIED | ON_QA |
| Noriko Hosoi | 2016-10-31 21:37:13 UTC | Fixed In Version | 389-ds-base-1.3.5.10-12.el7 | 389-ds-base-1.3.5.10-12.el7_3 |
| Noriko Hosoi | 2016-11-01 18:37:53 UTC | Doc Text | In a replication topology, there was a combination of conditions which makes the following replication fail. condition 1. A supplier is 389-ds-base-1.2.11 on RHEL-6 and a consumer is 389-ds-base-1.3.4 or newer. condition 2. The supplier has custom schema to send to the consumer, where the custom schema sent from the supplier is subset of the custom schema of the consumer. This schema replication is rejected and failed. (Note that if the supplier is also 1.3.4 or newer, it does not replicate the schema.) Consequence: The replication failure closes the replication connection and the replication to be followed does not happen. Fix: Changing the schema replication failure from FATAL to NOT FATAL. Result: The schema replication failure does not prevent the following replication any more. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Marc Muehlfeld | 2016-11-14 12:53:59 UTC | CC | mmuehlfe | |
| Doc Text | In a replication topology, there was a combination of conditions which makes the following replication fail. condition 1. A supplier is 389-ds-base-1.2.11 on RHEL-6 and a consumer is 389-ds-base-1.3.4 or newer. condition 2. The supplier has custom schema to send to the consumer, where the custom schema sent from the supplier is subset of the custom schema of the consumer. This schema replication is rejected and failed. (Note that if the supplier is also 1.3.4 or newer, it does not replicate the schema.) Consequence: The replication failure closes the replication connection and the replication to be followed does not happen. Fix: Changing the schema replication failure from FATAL to NOT FATAL. Result: The schema replication failure does not prevent the following replication any more. | 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. | ||
| Flags | needinfo?(nhosoi) | |||
| Viktor Ashirov | 2016-11-14 13:18:59 UTC | Status | ON_QA | VERIFIED |
| Noriko Hosoi | 2016-11-14 17:40:54 UTC | Flags | needinfo?(nhosoi) | |
| Adam Tkac | 2016-11-23 11:11:00 UTC | CC | vonsch | |
| errata-xmlrpc | 2016-12-06 00:23:33 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-12-06 17:03:55 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-12-06 12:03:55 UTC |
Back to bug 1384785