Ticket 11111

Summary:	Very strict version requirements for ucx/pmix in spec file
Product:	Slurm	Reporter:	Ward Poelmans <ward.poelmans>
Component:	Build System and Packaging	Assignee:	Tim Wickberg <tim>
Status:	OPEN ---	QA Contact:
Severity:	C - Contributions
Priority:	---	CC:	jvilarru
Version:	20.11.5
Hardware:	Linux
OS:	Linux
See Also:	https://bugs.schedmd.com/show_bug.cgi?id=11973
Site:	VUB	Slinky Site:	---
Alineos Sites:	---	Atos/Eviden Sites:	---
Confidential Site:	---	Coreweave sites:	---
Cray Sites:	---	DS9 clusters:	---
Google sites:	---	HPCnow Sites:	---
HPE Sites:	---	IBM Sites:	---
NOAA SIte:	---	NoveTech Sites:	---
Nvidia HWinf-CS Sites:	---	OCF Sites:	---
Recursion Pharma Sites:	---	SFW Sites:	---
SNIC sites:	---	Tzag Elita Sites:	---
Linux Distro:	---	Machine Name:
CLE Version:		Version Fixed:
Target Release:	---	DevPrio:	---
Emory-Cloud Sites:	---
Attachments:	Remove strict version requirements for ucx/pmix in spec file

Description Ward Poelmans 2021-03-17 02:58:55 MDT

Created attachment 18494 [details]
Remove strict version requirements for ucx/pmix in spec file

In bug 6598 support was added to the slurm spec file to use ucx and pmix.

The current approach is to require exactly the same version of ucx and pmix as the one used to build slurm. Is there any reason for this?
I understand ucx and pmix need to be ABI compatible but minor version increase should not be an issue. It's not very common to have this kind of strict requirements in a spec file. It will also break 'yum update' if new version of ucx or pmix are available. If one wants to make sure the version of ucx and/or pmix are fixed, the correct way is a version lock.

We have nodes with different generation of Mellanox cards which have different version of OFED and in turn different version of ucx. So this is quite annoying and it works fine without the strict version lock.

In attachment there is a patch for the spec file that just requires ucx/pmix without a strict version requirement.

This also fixes bug 9293.