[Nasf-Fan]

db_traverse() calls vos_iterate() to traverse the VOS_ITER_AKEY for related sysdb table. For each found item, it handles it via sys_db_trav_cb_t() that may remove such item from related sysdb table, such as for some CHK cleanup use case. If that happened, We will notify vos_iterate() logic via set "VOS_ITER_CB_DELETE" flag in the "acts" parameter; otherwise some item(s) in related sysdb table may be skipped in subsequent iteration. For CHK use case, that may affect new check instance to reset automatically.

Test-tag: cat_recov

Steps for the author:

• Commit message follows the guidelines.
• Appropriate Features or Test-tag pragmas were used.
• Appropriate Functional Test Stages were run.
• At least two positive code reviews including at least one code owner from each category referenced in the PR.
• Testing is complete. If necessary, forced-landing label added and a reason added in a comment.

After all prior steps are complete:

• Gatekeeper requested (daos-gatekeeper added as a reviewer).

[github-actions]

Ticket title is 'recovery/cat_recov_core.py:CatRecovCoreTest.test_daos_cat_recov_core - CR9: Failure assert_rc_equal src/tests/suite/daos_cr.c:1861 DER_INVAL(-1003) != DER_SUCCESS(0) and then CR10 - CR28 '
Status is 'In Progress'
Labels: 'ci_master_daily,daily_test'
https://daosio.atlassian.net/browse/DAOS-17977

[daosbuild3]

Test stage Functional Hardware Medium Verbs Provider MD on SSD completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-16896/3/execution/node/1391/log

[daosbuild3]

Test stage Functional Hardware Medium MD on SSD completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-16896/5/execution/node/624/log

[Nasf-Fan]

Test stage Functional Hardware Medium MD on SSD completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-16896/5/execution/node/624/log

PoolMembershipTest.test_dangling_rank_entry failed for DAOS-18018, not related with the patch.

[daltonbohning]

ftest changes LGTM but is this really meant to run with

Test-tag: cat_recov

Instead of

Features: cat_recov

[Nasf-Fan]

ftest changes LGTM but is this really meant to run with

Test-tag: cat_recov

Instead of

Features: cat_recov

I want to only run test cases with tags=cat_recov (that are under src/tests/ftest/recovery/), then which one I should use? @daltonbohning , thanks!

[daltonbohning]

I want to only run test cases with tags=cat_recov (that are under src/tests/ftest/recovery/), then which one I should use? @daltonbohning , thanks!

Test-tag: cat_recov is the way to do that, but do the src/bio and src/vos changes not affect any other tests or areas?

[Nasf-Fan]

I want to only run test cases with tags=cat_recov (that are under src/tests/ftest/recovery/), then which one I should use? @daltonbohning , thanks!

Test-tag: cat_recov is the way to do that, but do the src/bio and src/vos changes not affect any other tests or areas?

No, the new parameter in the patch is useless for src/bio and src/vos related changes.

[Nasf-Fan]

test_dangling_rank_entry failed for DAOS-18018, not related with the patch.