DAOS-16914 vos: don't print error message on ITER_EXIT

[NiuYawei]

Don't print error message on ITER_EXIT in vos_obj_iterate().

Signed-off-by: Niu Yawei [email protected]

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]

Ticket title is 'typo in vos_iterate_internal()'
Status is 'In Review'
https://daosio.atlassian.net/browse/DAOS-16914

[daltonbohning]

Copyright GHA failing implies the githooks are not configured. It probably shouldn't be an Intel copyright anymore, but either way you should configure the githooks since the lint checks are required.
\https://github.com/daos-stack/daos/tree/master/utils/githooks#readme

[NiuYawei]

Copyright GHA failing implies the githooks are not configured. It probably shouldn't be an Intel copyright anymore, but either way you should configure the githooks since the lint checks are required. \https://github.com/daos-stack/daos/tree/master/utils/githooks#readme

yeah, I forgot to configure githooks on my HPE laptop.

[daosbuild1]

Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-15675/2/execution/node/1484/log

[NiuYawei]

Fixed copyright

[daosbuild1]

Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-15675/3/execution/node/1464/log

[NiuYawei]

@sherintg , @jolivier23 Sorry, I realized that we don't return 0 for ITER_EXIT for some reason, updated patch.

[daltonbohning]

I restarted the Jenkins pipeline due to pipeline-lib bug fix