Hide Forgot
Description of problem: In the man page for the command ipa-replica-manage the command is mis-typed on lines 106, 109, & 112. The command is referenced as: ipa replica-manage which makes it appear to be related to the ipa system wide management command. Version-Release number of selected component (if applicable): [root@test ipa]# rpm -qif `which ipa-replica-manage` Name : ipa-server Relocations: (not relocatable) Version : 2.1.3 Vendor: Red Hat, Inc. Release : 9.el6 Build Date: Mon 07 Nov 2011 03:00:54 PM EST Install Date: Thu 09 Feb 2012 06:07:51 PM EST Build Host: x86-001.build.bos.redhat.com Group : System Environment/Base Source RPM: ipa-2.1.3-9.el6.src.rpm Size : 3382131 License: GPLv3+ Signature : RSA/8, Tue 08 Nov 2011 10:03:12 AM EST, Key ID 199e2f91fd431d51 Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> Additional info: A patch for the man unzipped man page (ipa-replica-manage.1) is attached.
Created attachment 565052 [details] Patch for file ipa-replica-manage.1
Upstream ticket: https://fedorahosted.org/freeipa/ticket/2428
Fixed upstream: master: https://fedorahosted.org/freeipa/changeset/1cc761353bad6d279cd7d14939f67baef784433f ipa-2-2: https://fedorahosted.org/freeipa/changeset/0bcd66af30720e08739ba40db7270faa5826019c
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No documentation needed.
Verified. Version :: ipa-server-2.2.0-12.el6.x86_64 Manual Test Results :: # man ipa-replica-manage <go down to line 105> Add a new replication agreement: # ipa-replica-manage connect srv2.example.com srv4.example.com Remove an existing replication agreement: # ipa-replica-manage disconnect srv1.example.com srv3.example.com Completely remove a replica: # ipa-replica-manage del srv4.example.com
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. http://rhn.redhat.com/errata/RHBA-2012-0819.html