DAOS-13378 build: Temporarily pin libfabric to < 1.18

[soumagne]

Required-githooks: true

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]

Bug-tracker data:
Errors are Unable to load ticket data
https://daosio.atlassian.net/browse/DAOS-13378

[daosbuild1]

LGTM. No errors found by checkpatch.

[daosbuild1]

LGTM. No errors found by checkpatch.

[daosbuild1]

LGTM. No errors found by checkpatch.

[daosbuild1]

LGTM. No errors found by checkpatch.

[daosbuild1]

Test stage NLT on EL 8 completed with status UNSTABLE. https://build.hpdd.intel.com/job/daos-stack/job/daos//view/change-requests/job/PR-12119/4/testReport/(root)/

[daosbuild1]

LGTM. No errors found by checkpatch.

[daosbuild1]

Test stage Functional Hardware Medium Verbs Provider completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-12119/5/execution/node/1162/log

[brianjmurrell]

How temporary is this expected to be?

Just for clarity, once again, I will re-iterate that setting maximum dependency versions will severely hamper our future ability to push out an update to a component/dependency in an agile manner, and instead of just being able to push out an update (without any DAOS release -- including full testing, QA, SDL, etc.) to the component, we will need to update DAOS, do all required testing on it and re-qualify it with SDL before users can have a libfabric update.

We really really need to strive to never use maximum dependency versions, especially in a released product. If this will be reverted before any release is made, we can live with it, but we must make sure to remember to not make any release with this change in it.

[soumagne]

I agree, yes we're working on the issue currently and that restriction should be lifted before release.