PR landed to both master and 2.6 branch.

We are still seeing target_failure.py test failure on master… This ticket is linked to . Is this correct?

If so, we are noticing target_failure.py tests failing on weekly testing (last week).

https://build.hpdd.intel.com/job/daos-stack/job/daos/job/weekly-testing/394/artifact/Functional%20Hardware%20Medium/deployment/target_failure.py/

PR landed to master, is for 2.6

please approve merge for 2.6, thx

Observed in a PR based on master.

https://build.hpdd.intel.com/job/daos-stack/job/daos/job/PR-14835/1/testReport/junit/FTEST_daos_test/DaosCoreTest-DAOS_Rebuild_EC/Test_Hardware___Functional_Hardware_Medium_Verbs_Provider___REBUILD45__multiple_shards_fail_tgts/

Another failure instance on release/2.6:

https://build.hpdd.intel.com/job/daos-stack/job/daos/job/PR-14827/2/artifact/Functional Hardware Medium Verbs Provider/daos_test/suite.py/test-results/23-._daos_test_suite.py_DaosCoreTest.test_daos_rebuild_ec_run-agent_config-transport_config-daos_tests-args-daos_test-num_clients-pools_created-stopped_ranks-test_name-dmg-hosts-pool-server_config-engines-0-storage-0-1-timeouts-d50f/