DAOS-15431 vos: clear DTX in CoS cache for the one committed by other - b24

[Nasf-Fan]

It is possible that the DTX is committed locally via commit-on-share mechanism during some subsequent modification. But such modification may get failure on some remote paraticipant. Then the DTX entry will not be removed from CoS cache under such case because we do not know whether such DTX has already been committed on remote participant(s) successfully or not. Keeping it in CoS cache will allow us to re-try the commit globally sometime later.

Next time, when we re-try to commit such DTX globally, if all remote participants claim as done (return 0 or DER_NONEXIST or DER_ALREADY) successfully, then even if local VOS calims as DER_ALREADY, we still need to remove the DTX entry from CoS cache. Otherwise, we will find such DTX entry in the CoS cache everytime for batched commit (or DTX resync) as to block related process.

Before requesting gatekeeper:

• Two review approvals and any prior change requests have been resolved.
• Testing is complete and all tests passed or there is a reason documented in the PR why it should be force landed and forced-landing tag is set.
• Features: (or Test-tag*) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.
• Commit messages follows the guidelines outlined here.
• Any tests skipped by the ticket being addressed have been run and passed in the PR.

Gatekeeper:

• You are the appropriate gatekeeper to be landing the patch.
• The PR has 2 reviews by people familiar with the code, including appropriate owners.
• Githooks were used. If not, request that user install them and check copyright dates.
• Checkpatch issues are resolved. Pay particular attention to ones that will show up on future PRs.
• All builds have passed. Check non-required builds for any new compiler warnings.
• Sufficient testing is done. Check feature pragmas and test tags and that tests skipped for the ticket are run and now pass with the changes.
• If applicable, the PR has addressed any potential version compatibility issues.
• Check the target branch. If it is master branch, should the PR go to a feature branch? If it is a release branch, does it have merge approval in the JIRA ticket.
• Extra checks if forced landing is requested
  • Review comments are sufficiently resolved, particularly by prior reviewers that requested changes.
  • No new NLT or valgrind warnings. Check the classic view.
  • Quick-build or Quick-functional is not used.
• Fix the commit message upon landing. Check the standard here. Edit it to create a single commit. If necessary, ask submitter for a new summary.

[github-actions]

Bug-tracker data:
Ticket title is 'daos_test/suite.py: test_daos_rebuild_simple: during iteration: Test interrupted by SIGTERM'
Status is 'In Review'
Labels: 'scrubbed,triaged'
https://daosio.atlassian.net/browse/DAOS-15431

[daosbuild1]

LGTM. No errors found by checkpatch.

[Nasf-Fan]

No plan for back-port to release/2.4.