DAOS-19088 ci: pin mercury-devel to latest 15.5 version

[grom72]

The latest available leap 15.5 mercury-devel RPM has version 2.4.1-2.
This version must be used for proper DAOS build on leap 15.5.

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 'Build RPM on Leap 15.5 failed on release/2.6 branch'
Status is 'Open'
Labels: 'request_for_2.6.6'
https://daosio.atlassian.net/browse/DAOS-19088

[daltonbohning]

This will get the build working but I think we need approval from relevant parties on whether we actually want to do this because it means we would not be able to update mercury without also releasing a new version of DAOS.

Is it feasible to build mercury with lp155 and lp156 so the latest works for all branches?

[soumagne]

what is the issue here? do we know why it fails with the latest rpm build ? there is nothing in it that should prevent any update and/or require pinning.

[grom72]

This will get the build working but I think we need approval from relevant parties on whether we actually want to do this because it means we would not be able to update mercury without also releasing a new version of DAOS.

Is it feasible to build mercury with lp155 and lp156 so the latest works for all branches?

There is no straightforward way to support both lp155 and lp156 RPMs
The only solution I know is to create a PR for the master branch (with leap 15.5 as the target OS) and manually copy lp155 RPMs to artifactory.

[grom72]

what is the issue here? do we know why it fails with the latest rpm build ? there is nothing in it that should prevent any update and/or require pinning.

Every build on the release/2.6 branch requires mercury-devel-...-lp155 RPM. Otherwise build fails due to libc incompatibility between 15.6 and 15.5.

We can either pin mercury-devel to the latest lp155 version or manually create mercury-devel-2.4.1-3.suse.lp155.

The problem is more generic as it has been described in #18166 (comment).

We do not have solution that ensures proper RPM version on Leap 15.5.

[soumagne]

honestly I think that goes back to that more general issue where we need to have separate dependency repositories for each DAOS major version and not put everything into the same shared artifactory for all releases, otherwise we are just tied to pinning and have shared pipeline for stuff that is not backported and causes issues etc... we just need to have more control on what each DAOS release picks as its dependencies and stop having it from picking up whatever lands in master... is there a ticket for that more general issue already ? otherwise I'd like to create one.