DAOS-14126 pool: Debug fetch_hdls (#12889)

[liw]

Because I couldn't reproduce the hang in pool_fetch_hdls_ult_abort even after a considerable effort both manually and through CI, I have to propose landing these extra logging.

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 watchers.
• [ ] 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[bot]]

Bug-tracker data: Ticket title is 'pool/create_capacity.py:PoolCreateTests.test_create_pool_quantity - pool destroy takes long time and causes test timeout in teardown' Status is 'Awaiting backport' Labels: 'scrubbed,triaged' Job should run at elevated priority (1) https://daosio.atlassian.net/browse/DAOS-14126

[daltonbohning]

Still awaiting merge approval for 2.4.2

[daltonbohning]

Merge approval granted, but last commit was 5 weeks ago. Will you please merge latest 2.4 and re-add gatekeeper when ready?

[daosbuild1]

Test stage Functional Hardware Medium Verbs Provider completed with status UNSTABLE. https://build.hpdd.intel.com/job/daos-stack/job/daos//view/change-requests/job/PR-13510/3/testReport/

[liw]

@daos-stack/daos-gatekeeper, this backport debug PR has waited almost 3 months. Could you let me know what it takes to get it landed, please?

[mchaarawi]

@daos-stack/daos-gatekeeper, this backport debug PR has waited almost 3 months. Could you let me know what it takes to get it landed, please?

this is approved to merge to 2.4.3 and not 2.4.2. so it cannot be merged by gatekeepers until 2.4.2 is officially released.

[liw]

@daos-stack/daos-gatekeeper, this backport debug PR has waited almost 3 months. Could you let me know what it takes to get it landed, please?

this is approved to merge to 2.4.3 and not 2.4.2. so it cannot be merged by gatekeepers until 2.4.2 is officially released.

Hmm, I see. :( Thanks, @mchaarawi.

[liw]

Cherry-picked into #14019.