Ignore replica busy condition in healthcheck

[progier389]

Replica Busy condition is expected when there is more than 2 suppliers so healthcheck should not report any error for such condition.

Issue: #6626

Reviewed by: ?

[tbordaz]

LGTM
I think you also need to update existing calls to run_healthcheck_and_flush_log to set isnot=True|False.

[progier389]

I think you also need to update existing calls to run_healthcheck_and_flush_log to set isnot=True|False.

isnot is an optional parameter with False as default value, so there is no need to change the existing calls (they will just use False for isnot ...

[progier389]

test_healthcheck_replication_out_of_sync_broken is failing:
ERROR:dirsrvtests.tests.suites.healthcheck.health_repl_test:DSREPLLE0001 is not in healthcheck output:
Both in bdb and lmdb
Maybe there is a side effect ?

[progier389]

Apparently that is a test case issue: test_healthcheck_replication_out_of_sync_broken has a race condition allowing to run healthcheck before replication is out of sync (because agmt fro M1 to M2,M3 are not broken.
Changing the test to do updates on all instances, and restore broken replica once the test is finished.