Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1212719
Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.
Description of problem: The operation clean-ruv has the drawback that is sending a "CLEANALLRUV" operation which is quite optimal but requires all the nodes up and running. If not, it will block. We have seen that these CLEANALLRUV operations stay hang'd and they are cumulated over several attempts. Of course, we have an subcommand to abort the tasks but we have the same problem there. I think the best would be to add an option: --force to "abort-clean-ruv" which will set the attribute: "replica-certifyall: no" in the task: ------------- modified extract of ipaserver/install/replication.py ------- dn, { 'replica-base-dn': [api.env.basedn], 'replica-id': [replicaId], 'objectclass': ['top', 'extensibleObject'], 'replica-certifyall': <yes / no if --force> 'cn': ['abort %d' % replicaId], } ---------------------------------------------------------------------------- Version-Release number of selected component (if applicable): ipa-server-4.1 How reproducible: it's a sort of RFE, always reproducible. Actual results: cleanallruv task could stay hanged and not easily aborted. Expected results: to be able to abort the task.
Note, the DS attribute is 'replica-certify-all'
This ticket is not critical for 4.2 GA and can be done in follow-up stabilization release - postponing.
master:
ipa-4-2:
Metadata Update from @pvoborni: - Issue assigned to mbasti - Issue set to the milestone: FreeIPA 4.2.1
Login to comment on this ticket.