Bug 1498399

Summary: [Doc] [RFE] Handling replication conflict entries
Product: Red Hat Enterprise Linux 7 Reporter: Martin Kosek <mkosek>
Component: doc-Linux_Domain_Identity_Management_GuideAssignee: Aneta Šteflová Petrová <apetrova>
Status: CLOSED CURRENTRELEASE QA Contact: ipa-qe <ipa-qe>
Severity: unspecified Docs Contact:
Priority: high    
Version: 7.5CC: enewland, gparente, lkrispen, lmanasko, mkosek, mmuehlfe, mreynolds, msauton, nhosoi, nkinder, rhel-docs, rmeggins, tmihinto, tscherf, vashirov
Target Milestone: rcKeywords: Documentation, FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://www.port389.org/docs/389ds/design/managing-repl-conflict-entries.html
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1274430 Environment:
Last Closed: 2018-04-12 15:38:54 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: 1470091    

Description Martin Kosek 2017-10-04 08:44:07 UTC 
+++ This bug was initially created as a clone of Bug #1274430 +++

Bug 1274430 introduces a new way of handling Replication Conflicts, see design page:
http://www.port389.org/docs/389ds/design/managing-repl-conflict-entries.html

We need to make sure that IdM users will be able to understand the new Replication Conflict behavior, find the conflicts and resolve them.

I noticed that right now, replication conflicts are only linked from IdM guide:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/linux_domain_identity_authentication_and_policy_guide/trouble-replica

The new replication conflict advise will again need to be either documented or linked from the main IdM guide.
Comment 8 Tomas Capek 2018-04-12 15:38:54 UTC 
published at:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/linux_domain_identity_authentication_and_policy_guide/#trouble-specific