Hide Forgot
Description of problem: this could seem to be very not very important bug. But in fact, customers are deleting replicas doing first the "ipa-server-install --uninstall" in the replica and then, "ipa-replica-manage del <replica>" at master side. with the former command, we have --force --cleanup to destroy all the references to the replica at master side. But ... ipa-cs-replica-manage is missing the --cleanup which could be extremely useful to do the cleanup of the replica at master side. Already, I would say that ipa-replica-manage del ... should remove also all the references to the CA instance so as not to have to run ipa-csreplica-manage del Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
With RHEL 7.3 and IPA 4.4 on domain level 1 this RFE won't be needed. `ipa-replica-manage del` will be an alias for `ipa server-del` which takes care of RUV cleanup on both suffixes. So question is whether it is worth to implement it for domain level 0. Per triage on Mon Oct 3, devel team thinks it isn't and this bz should be closed as won't fix.
Upstream ticket: https://fedorahosted.org/freeipa/ticket/6403
Let's wait with closing if there will be still demand after 7.3 adoption.
RHEL-7.7 is already near the end of a Development Phase and development is being wrapped up. I am bulk-moving to RHEL 8 the Bugs which were already triaged, but to which we did not commit (without devel_ack) and we cannot keep them even as a stretch goal for RHEL-7.7. If you believe this particular bug should be reconsidered for 7.7, please let us know.
This BZ has been evaluated multiple times over the last several years and we assessed that it is a valuable request to keep in the backlog and address it at some point in future. Time showed that we did not have such capacity, nor have it now nor will have in the foreseeable future. In such a situation keeping it in the backlog is misleading and setting the wrong expectation that we will be able to address it. Unfortunately we will not. To reflect this we are closing this BZ. If you disagree with the decision please reopen or open a new support case and create a new BZ. However this does not guarantee that the request will not be closed during the triage as we are currently applying much more rigor to what we actually can accomplish in the foreseeable future. Contributions and collaboration in the upstream community and CentOS Stream is always welcome! Thank you for understanding. Red Hat Enterprise Linux Identity Management Team