Document how to recover from there situations:
The setup looks like the following, A is the configuration Hub. B,C,D are siblings. A / | \ B C D
Case no. 1, A is broken, like disc failure, and then re-imaged after several days.
Case no. 2, A is working, but either B, or C is broken.
Case no. 3, If some un-expected IPA changes happens on A -- like all users are deleted by human mistakes --, and even worse, all the changes are propagated to B and C in minutes.
Details:
https://www.redhat.com/archives/freeipa-users/2012-May/msg00224.html
Interesting post/part of thread: https://www.redhat.com/archives/freeipa-users/2012-May/msg00248.html
Other details in this thread https://www.redhat.com/archives/freeipa-users/2012-May/msg00174.html
Doc bug related to it is https://bugzilla.redhat.com/show_bug.cgi?id=814489
Moving doc tickets to a separate 3.0 doc milestone.
Rename component.
FreeIPA project no longer actively maintains an upstream guide (see details). This ticket is already cloned to RHEL downstream guide so the issue should fixed at least there.
Metadata Update from @pspacek: - Issue assigned to elladeon - Issue set to the milestone: FreeIPA 3.x Documentation
Login to comment on this ticket.