Building of openmpi rpm hits issue with python scripts in 3rd-party modules

[acgoldma]

Thank you for taking the time to submit an issue!

Background information

Using an internal script to build the SRPM/RPMs for openmpi I am hitting a new error, that I did not see previously.

*** ERROR: ambiguous python shebang in /usr/mpi/gcc/openmpi-5.0.0a1-cuda-ofi/bin/event_rpcgen.py: #!/usr/bin/env python. Change it to python3 (or python2) explicitly.
error: Bad exit status from /var/tmp/rpm-tmp.2FgkP7 (%install)

I am building openmpi with the same script I used to build in #8764. the only difference is that it looks like the submodule pointers updated I believe.

What version of Open MPI are you using? (e.g., v3.0.5, v4.0.2, git branch name and hash, etc.)

v5.0.x (80e921c)

Describe how Open MPI was installed (e.g., from a source/distribution tarball, from a git clone, from an operating system distribution package, etc.)

git clone from github.

If you are building/installing from a git clone, please copy-n-paste the output from git submodule status.

# git submodule status
 f5f4384b150896b281d870d87bedb9de626299f7 3rd-party/openpmix (v4.0.0-141-gf5f4384b)
 c950c5d1d267360c490961fe9443625f1dd9bde9 3rd-party/prrte (dev-31139-gc950c5d1d2)

Please describe the system on which you are running

• Operating system/version: RHEL 8.1
• Computer hardware: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
• Network type: OPA and/or CVL[RoCEv2]

---

Details of the problem

Please describe, in detail, the problem that you are having, including the behavior you expect to see, the actual behavior that you are seeing, steps to reproduce the problem, etc. It is most helpful if you can attach a small program that a developer can use to reproduce your problem.

Note: If you include verbatim output (or a code block), please use a GitHub Markdown code block like below:

shell$ mpirun -np 2 ./hello_world

Not sure why I did not see this previous builds, but looks like this has been a 'feature' of fedora/redhat for a bit:
https://fedoraproject.org/wiki/Changes/Make_ambiguous_python_shebangs_error

They give an example of fixing this in the spec file, but ideally this should be fixed in python scripts:

# grep -r "#\!/usr/bin/env" | grep python$
3rd-party/libevent-2.1.12-stable/event_rpcgen.py:#!/usr/bin/env python
3rd-party/libevent-2.1.12-stable/test/check-dumpevents.py:#!/usr/bin/env python
3rd-party/prrte/contrib/libadd_mca_comp_update.py:#!/usr/bin/env python
contrib/libadd_mca_comp_update.py:#!/usr/bin/env python
contrib/dist/linux/ompi-spec-generator.py:#!/usr/bin/env python

[acgoldma]

Using the libevent-devel package gets around this, but it might be useful to add some fix in ompi to avoid this for those who wish to use the 'internal' version.