[lustre-discuss] lustre-dkms 2.12.9 O2IBPATHS failure

Tancheff, Shaun shaun.tancheff at hpe.com
Fri Sep 2 20:36:06 PDT 2022


This was fixed in https://review.whamcloud.com/46383 but was not ported / included in 2.12.9

In the meantime you can move to an older OFED or apply the patch to the b2_12 sources and rebuild the dkms package?

From: lustre-discuss <lustre-discuss-bounces at lists.lustre.org> on behalf of Liam Forbes via lustre-discuss <lustre-discuss at lists.lustre.org>
Reply-To: Liam Forbes <loforbes at alaska.edu>
Date: Saturday, September 3, 2022 at 4:38 AM
To: "lustre-discuss at lists.lustre.org" <lustre-discuss at lists.lustre.org>
Subject: [lustre-discuss] lustre-dkms 2.12.9 O2IBPATHS failure

I'm attempting to install lustre-client-dkms 2.12.9 on a Rocky Linux 8.6 system with kernel 4.18.0-372.19.1.el8_6.x86_64 and Mellanox OFED 5.7.1.0.2.1.rhel8u5.x86_64. I have the mlnx-ofa_kernel-devel RPM installed, but the lustre configure script is giving me the following error during the `yum install`:

You seem to have an OFED installed but have not installed it's devel package.
If you still want to build Lustre for your OFED I/B stack, you need to install its devel headers RPM.
Instead, if you want to build Lustre for your kernel's built-in I/B stack rather than your installed OFED stack, either remove the OFED package(s) or use --with-o2ib=no.

Error! Bad return status for module build on kernel: 4.18.0-372.19.1.el8_6.x86_64 (x86_64)
Consult /var/lib/dkms/lustre-client/2.12.9/build/make.log for more information.
warning: %post(lustre-client-dkms-2.12.9-1.el8.noarch) scriptlet failed, exit status 10

I think I've tracked it down to a "$" at the end of a grep in the /var/lib/dkms/lustre-client/2.12.9/build/configure script, line 19530. Running the commands manually, if I drop the "$" then the O2IBPATHS variable gets populated.

[root at n1]# O2IBPATHS=$(eval /usr/bin/ofed_info | egrep -w 'mlnx-ofed-kernel-dkms|mlnx-ofa_kernel-devel|compat-rdma-devel|kernel-ib-devel|ofa_kernel-devel' | xargs rpm -ql | grep '\(/openib\|/ofa_kernel/default\|/ofa_kernel\)$' | head -n1)
[root at n1]# echo $O2IBPATHS

[root at n1]# O2IBPATHS=$(eval /usr/bin/ofed_info | egrep -w 'mlnx-ofed-kernel-dkms|mlnx-ofa_kernel-devel|compat-rdma-devel|kernel-ib-devel|ofa_kernel-devel' | xargs rpm -ql | grep '\(/openib\|/ofa_kernel/default\|/ofa_kernel\)' | head -n1)
[root at n1]# echo $O2IBPATHS
/usr/src/ofa_kernel/x86_64/4.18.0-372.19.1.el8_6.x86_64

It's hard to believe that I'm the first person to run into this, but googling I haven't found any other reports of it being an issue. Just thought I'd check. I'm also not sure how to insert this tweak to test if it really fixes the configure failure.

--
Regards,
-liam

-There are uncountably more irrational fears than rational ones. -P. Dolan
Liam Forbes           loforbes at alaska.edu<mailto:loforbes at alaska.edu>                       ph: 907.450.8618
UAF GI Research Computing Systems Manager
https://calendly.com/ualoforbes/30min<https://calendly.com/ualoforbes/30min>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20220903/30bfc64e/attachment-0001.htm>


More information about the lustre-discuss mailing list