[LU-17398] Quash rpmbuild false warning due to %() in comment Created: 06/Jan/24  Updated: 30/Jan/24  Resolved: 10/Jan/24

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: Lustre 2.16.0

Type: Improvement Priority: Minor
Reporter: Shaun Tancheff Assignee: Shaun Tancheff
Resolution: Fixed Votes: 0
Labels: None

Attachments: Text File lustre-master-next-756-x86_86.txt     Text File lustre-reviews-ib-6871-x86_86.txt    
Issue Links:
Related
is related to LU-16967 Split LNDs into sub-packages so MOFED... Open
is related to LU-17487 parsing --with-o2ib fails Open
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

rpmbuild reports the following warning:

00:08:26.905 sh: -c: line 0: syntax error near unexpected token `)'
00:08:26.905 sh: -c: line 0: `)'
00:08:26.905 warning: Macro expanded in comment on line 261: %()

However the root cause if this entire 3 lines of warning is a %() found in comment.
Rewrite the comment to escape the %() as %%() ... and suppress the warning.



 Comments   
Comment by Gerrit Updater [ 06/Jan/24 ]

"Shaun Tancheff <shaun.tancheff@hpe.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/53604
Subject: LU-17398 build: quash rpmbuild false warning
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 51b601b66792ee5b0e594b540f323c39fd427330

Comment by Gerrit Updater [ 08/Jan/24 ]

"Shaun Tancheff <shaun.tancheff@hpe.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/53613
Subject: LU-17398 build: detect mlnx-ofa_kernel-devel contents
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: a16751e16167be9caa1a79a412817815d64e84b9

Comment by Andreas Dilger [ 09/Jan/24 ]

I've attached logs from the failed builds:

Comment by Andreas Dilger [ 09/Jan/24 ]

The 53604 patch resolved the syntax error/warning, but 53613 has not yet resolved the MOFED IB build failure, though it has changed the mode of failure. It no longer complains about BuildRequires but hits an error later during the build (you may not be able to access the URL, but this is the lustre-reviews-ib-6871-x86_86.txt log that is attached):
https://build.whamcloud.com/job/lustre-reviews-ib/6871/arch=x86_64,build_type=client,distro=el9.1,ib_stack=mlx/console

00:07:30.741 + export OMPI_MCA_rmaps_base_oversubscribe=1
00:07:30.741 + OMPI_MCA_rmaps_base_oversubscribe=1
00:07:30.741 + WITH_O2IB=
00:07:30.741 ++ find /usr/src/ofa_kernel/ -type d -name ofed_scripts
00:07:30.742 ++ xargs dirname
00:07:30.743 find: '/usr/src/ofa_kernel/': No such file or directory
00:07:30.743 dirname: missing operand
00:07:30.743 Try 'dirname --help' for more information.
00:07:30.744 + o2ib_path=
00:07:30.744 error: Bad exit status from /tmp/rpmbuild-lustre-jenkins-szUKCBIl/TMP/rpm-tmp.UzokKA (%build) 
Comment by Minh Diep [ 09/Jan/24 ]
610 WITH_O2IB=""
611 %if %{with mofed}
612 ▶·······o2ib_path=$(find /usr/src/ofa_kernel/ -type d -name ofed_scripts | xargs dirname)
613 ▶·······if [ -z "$o2ib_path" ]; then 

Need to check if /usr/src/ofa_kernel exists

Comment by Andreas Dilger [ 09/Jan/24 ]

The most recent version of patch https://review.whamcloud.com/53613 "LU-17398 build: detect mlnx-ofa_kernel-devel contents" resolves the MOFED build issue.

Comment by Gerrit Updater [ 10/Jan/24 ]

"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/53604/
Subject: LU-17398 build: quash rpmbuild false warning
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: fdab3f6455c99072d2b4e93e176432cd7f5d3c2f

Comment by Gerrit Updater [ 10/Jan/24 ]

"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/53613/
Subject: LU-17398 build: detect mlnx-ofa_kernel-devel contents
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 3c66185c84c94c47f5d8031b92165c68ef666e0e

Comment by Peter Jones [ 10/Jan/24 ]

Merged for 2.16

Comment by Shuichi Ihara [ 30/Jan/24 ]

this patch contains a regression. see LU-17487

Generated at Sat Feb 10 03:35:07 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.