freeipa

Clone
Source Code
GIT

#5066 meaningful error messages for ipa-replica-manage failures
Closed: Fixed None Opened 8 years ago by ofayans.

Closed: Fixed
Reopen Issue

At domain levels above 0 all the replica removals are controlled by the Topology Plugin, so ipa-replica-manage del is prohibited. We should provide a meaningful error messages for the cases when ipa-replica-manage fails due to Topology Plugin controlling the segment. Currently we have the following:[[BR]]
$ ipa-replica-manage list f22master.bagam.net[[BR]]
f22replica1.bagam.net: replica[[BR]]
f22replica2.bagam.net: replica[[BR]]
$ ipa-replica-manage del f22replica2.bagam.net --force[[BR]]
unexpected error: no such entry[[BR]]
$ ipa-replica-manage force-sync --from f22replica1.bagam.net[[BR]]
Directory Manager password:[[BR]]
unexpected error: no such entry

some notes:

  • ipa-replica-manage del is not prohibited and should be fixed with e9e4509
  • force-sync fails and re-initialze can suffer from error no such entry because new replication agreements, which were created by a topology plugin, have different naming pattern than the ones created by ipa-replica-manage connect.
  • topology plugin actually allows to modify replication agreement in a way to allow refresh and reinitialize

master:

  • dcb6916 fix force-sync, re-initialize of replica and a check for replication agreement existence

Metadata Update from @ofayans:
- Issue assigned to pvoborni
- Issue set to the milestone: FreeIPA 4.2
7 years ago

Login to comment on this ticket.

Metadata
None
None
None
normal
None
None
None
None
defect
None
None
IPA
None
1
None
None
None
None
todo
None
None
None
Powered by Pagure 5.13.3
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.