Ticket 5748

Summary: error building for RHEL V6/usr/local/slurm/sbin/slurmsmwd unattached to RPM
Product: Slurm Reporter: GSK-ONYX-SLURM <slurm-support>
Component: Build System and PackagingAssignee: Felip Moll <felip.moll>
Status: RESOLVED FIXED QA Contact:
Severity: 4 - Minor Issue    
Priority: --- CC: felip.moll
Version: 17.11.7   
Hardware: Linux   
OS: Linux   
Site: GSK Alineos Sites: ---
Atos/Eviden Sites: --- Confidential Site: ---
Coreweave sites: --- Cray Sites: ---
DS9 clusters: --- HPCnow Sites: ---
HPE Sites: --- IBM Sites: ---
NOAA SIte: --- OCF Sites: ---
Recursion Pharma Sites: --- SFW Sites: ---
SNIC sites: --- Linux Distro: ---
Machine Name: 0 CLE Version:
Version Fixed: 17.11.10 Target Release: ---
DevPrio: --- Emory-Cloud Sites: ---

Description GSK-ONYX-SLURM 2018-09-18 07:50:12 MDT 
Requires: libc.so.6()(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3.4)(64bit) libc.so.6(GLIBC_2.4)(64bit) libc.so.6(GLIBC_2.7)(64bit) libpthread.so.0()(64bit) libpthread.so.0(GLIBC_2.2.5)(64bit) libslurm.so.32()(64bit)
Obsoletes: pam_slurm
Checking for unpackaged file(s): /usr/lib/rpm/check-files /root/rpmbuild/BUILDROOT/slurm-17.11.7-1.el6.x86_64
warning: Installed (but unpackaged) file(s) found:
   /usr/local/slurm/sbin/slurmsmwd
Wrote: /root/rpmbuild/SRPMS/slurm-17.11.7-1.el6.src.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/slurm-17.11.7-1.el6.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/slurm-perlapi-17.11.7-1.el6.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/slurm-devel-17.11.7-1.el6.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/slurm-munge-17.11.7-1.el6.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/slurm-slurmdbd-17.11.7-1.el6.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/slurm-sql-17.11.7-1.el6.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/slurm-plugins-17.11.7-1.el6.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/slurm-torque-17.11.7-1.el6.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/slurm-openlava-17.11.7-1.el6.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/slurm-lua-17.11.7-1.el6.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/slurm-contribs-17.11.7-1.el6.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/slurm-pam_slurm-17.11.7-1.el6.x86_64.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.c3DQrf
+ umask 022
+ cd /root/rpmbuild/BUILD
+ cd slurm-17.11.7
+ rm -rf /root/rpmbuild/BUILDROOT/slurm-17.11.7-1.el6.x86_64
+ exit 0
[root@us1salx08242 tmp]# pwd
Comment 1 Felip Moll 2018-09-18 10:37:27 MDT 
Hi,

It seems that you have the slurmsmwd software installed from outside the RPM system. Is there any chance you have once run "make install" in the contribs directory of slurm smwd (slurm/contribs/cray/slurmsmwd) ?

Can you do an 'ldd /usr/local/slurm/sbin/slurmsmwd'?

You can safely uninstall this component (make uninstall in the contribs dir) since slurmsmwd is about support of daemons and software for the Cray SMW (System Management Workstation), and you're running Linux.

But in any case this shouldn't happen: I'd like to know how you compiled the RPM, have you used '--with cray' option?
Comment 2 Felip Moll 2018-09-21 02:05:00 MDT 
Hi,

Have you managed to find why you had a slurmsmwd already installed?

It was a warning, so I understand you have no problems on the installation?
Comment 3 GSK-ONYX-SLURM 2018-09-21 02:34:22 MDT 
I am confused by your approach.

I was building 17.11.7 for RHEL V6, and the checks showed that it had compiled a binary which was not associated with any RPM it was generating.  This normally results because the file name is not referenced in the SLURM.SPEC file.

So, I guess my question is in which RPM should the file appear?
Comment 6 Felip Moll 2018-09-26 01:51:02 MDT 
(In reply to GSK-EIS-SLURM from comment #3)
> I am confused by your approach.
> 
> I was building 17.11.7 for RHEL V6, and the checks showed that it had
> compiled a binary which was not associated with any RPM it was generating. 
> This normally results because the file name is not referenced in the
> SLURM.SPEC file.
> 
> So, I guess my question is in which RPM should the file appear?

Hi, you were right I didn't understand the problem initially.

I have a patch pending for review to fix slurm.spec-legacy just following commit 9c3441909bc07804f2f176ee4294641939a87bf3 approach. If you are bothered with this error and need the patch right now I can forward it to you, just have to say it.

Regards,
Felip
Comment 7 GSK-ONYX-SLURM 2018-09-26 02:00:27 MDT 
Felip

Thanks for the update; I have ""fixed"" the issue, and it is working, so I don't need the patch urgently.

But, this is the 2nd or 3rd time you have had problems with slurm.spec-legacy  not matching the build.  Can you please ensure that this does not happen again?
Comment 8 Felip Moll 2018-09-26 03:26:46 MDT 
(In reply to GSK-EIS-SLURM from comment #7)
> Felip
> 
> Thanks for the update; I have ""fixed"" the issue, and it is working, so I
> don't need the patch urgently.

Well, in any case I guess this was just a warning and not caused any real problems.

> But, this is the 2nd or 3rd time you have had problems with
> slurm.spec-legacy  not matching the build.  Can you please ensure that this
> does not happen again?

I understand your concern. What I can do is to talk with the team and make sure that all of us are aware of that changing spec files inmplies also changing legacy one. We will discuss for how much time we should maintain the legacy files. Also I can make sure that previous to a release, a build using this old spec file is also done correctly that should avoid further problems.

Aside from this, bugs happen, so please, if you still find anything just keep reporting and we will respond ASAP trying to do our best to fix them and not repeat the same mistakes.

Thanks
Comment 10 Felip Moll 2018-09-27 04:31:42 MDT 
Hi, commit 5490b994d2d3c fixes the issue in 17.11.10.

Closing bug now,
Felip