Initial comments:

The cleanallruv task is designed, for good reasons, to continue to run until all the replicas (replication agreements) can be reached and cleaned. If this is not done, as soon as that downed replica comes back online it will pollute all the RUV's of all the other replicas with the "invalid rid". Then you will have to run cleanallruv all over again.

If a replication agreement is invalid, it should be fixed, deleted, or disabled. Then cleanAllRUV will complete.

I don't see any value in adding a new task to test if replicas are reachable. This could be done with a simple shell/python script issuing searches using the credentials found in the replica agreement.

Also, what is the harm with cleanallruv running in the background waiting for a replica agreement to be reachable? It's not really consuming any resources, and impacting performance.

The abort task is different, and there is a ticket open to address some of the shortcomings of an abort task(like not being able to abort an abort task). https://fedorahosted.org/389/ticket/48154

There is also another issue where cleanAllRUV task can run into issues if it encounters a RUV that is missing the URL. This will be addressed in: https://fedorahosted.org/389/ticket/48159

"This has been addressed in ticket 48154." by mreynolds.

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1488

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.