The clean-dangling-ruv fails with topologies either with single IPA server or in topologies with only one CA
How to reproduce: Have a master server and a CA-less replica Run ipa-replica-manage clean-dangling-ruv
Expected result: No dangling RUVs found. (or cleaning the dangling RUVs if there are any)
Actual result: Failed to obtain information from 'xxx.yyy': no such entry
Actually, the described behavior was encountered during implementation of another ipa-replica-manage enhancement. Currently, "No dangling RUVs found." is really printed to stdout. However, this is still a bug as instead of the actual error, sys.exit is called resulting in not executing the code of clean_dangling_ruvs if there's still some RUVs in other than the defect tree.
Possible solutions:[[BR]] Replace the sys.exits with exceptions as proposed in my patch 0027-3 from the ML[[BR]] OR[[BR]] backport the whole ticket https://fedorahosted.org/freeipa/ticket/4987
AND build the fix on top of the changes.
It seems that the behavior is the same even in master as the execution dies at conn.get_entry for ipaca tree in case of a single CA in the topology. However, even if this exception is handled to be passed instead, the execution would still end at the sys.exit in get_ruv.
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1298848 (Red Hat Enterprise Linux 7)
master:
ipa-4-3:
Metadata Update from @stlaz: - Issue assigned to stlaz - Issue set to the milestone: FreeIPA 4.3.2
Login to comment on this ticket.