Bug 1324242

Summary: rhds10 doc admin guide - incorrect Managing_Replication-Solving_Common_Replication_Conflicts.html#cleanallruv-task
Product: Red Hat Directory Server Reporter: Marc Sauton <msauton>
Component: Doc-administration-guideAssignee: Petr Bokoc <pbokoc>
Status: CLOSED CURRENTRELEASE QA Contact: Viktor Ashirov <vashirov>
Severity: high Docs Contact:
Priority: high    
Version: 10.0CC: gparente, msauton, rhel-docs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-14 15:03:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Marc Sauton 2016-04-05 23:08:51 UTC
Description of problem:

As of 2016-04-01, the online documentation is "incorrect" at

https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/10/html/Administration_Guide/Managing_Replication-Solving_Common_Replication_Conflicts.html#cleanallruv-task

chapter
11.23.4.1. Removing an Obsolete or Missing Supplier Using the cleanallruv Task Operation

I opened the following article for an example of the steps:
How to clean RUVs
https://access.redhat.com/articles/2217151

acknowledged by a customer in case and comment 46:
https://c.na7.visual.force.com/apex/Case_View?sbstr=01606055#comment_a0aA000000GoOTnIAN

the KB article is detailed, so not everything need to go into the admin guide, but the main steps need to be corrected for 1.1 and 1.2, and the step 2 could be improved

this is important to get right, because we do quite have cases for RHDS and quite often in IPA context that require those detailed steps, and we keep pointing to the upstream doc, http://www.port389.org/docs/389ds/howto/howto-cleanruv.html


Version-Release number of selected component (if applicable):
RHDS10 admin guide


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Petr Bokoc 2016-05-10 12:13:46 UTC
Hi Marc,

I updated most of the procedure based on the kbase article you provided. However, I have a question - in the KBase I don't understand what's actually happening in the two examples in step 4:

>To execute a CLEANRUV task, use ldapmodify against the DN of the replica
>configuration entry, and the number appended to either the strings "cn=clean "
>or "CLEANRUV" in "nsds5task: CLEANRUV" is the replica ID of the entry you want
>to remove, 8 in this example:

>ldapmodify -x -D "cn=directory manager" -W <<EOF
>dn: cn=clean 8,cn=cleanallruv,cn=tasks,cn=config
>objectclass: extensibleObject
>replica-base-dn: dc=example,dc=com
>replica-id: 8
>replica-force-cleaning: no
>cn: clean 8
>EOF

>To execute a CLEANRUV task, use ldapmodify:

>ldapmodify -x -D "cn=directory manager" -W <<EOF
>dn: cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config
>changetype: modify
>replace: nsds5task
>nsds5task: CLEANRUV8
>EOF

Both of the examples are introduced with "Execute a CLEANRUV task". Is the first one a preparation step while the second one actually runs it? Or

Comment 3 Marc Sauton 2016-05-10 17:59:48 UTC
yes, the first one is CLEANALLRUV and the second one a CLEANRUV, updated the kb, thanks.

Comment 4 Petr Bokoc 2016-05-11 13:53:38 UTC
Whoops, it even says so in the example, I guess I missed that. Thank you both.

So, I have an updated procedure ready - can you please take a look? I used somewhat different commands in a few steps, they should work the same but I don't have a multi-master environment to test everything thoroughly. Preview is at: http://jenkinscat.gsslab.pnq.redhat.com:8080/view/Directory%20Server/job/doc-Red_Hat_Directory_Server-Administration_Guide%20%28html-single%29/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#cleanruv

Comment 5 Petr Bokoc 2016-05-26 17:07:34 UTC
Marc, could you please take a look at the link in the previous comment, and let me know if it's ok? Thanks!

Comment 6 Marc Sauton 2016-05-26 22:57:41 UTC
it looks ok, thanks for all the detailed examples in the doc.

Comment 7 Petr Bokoc 2016-05-27 13:02:10 UTC
Thanks. Setting to verified, and I'll publish the update on the Customer Portal next week.