Bug 1321442

Summary:	OpenMPI- mpi4py ImportError: libmpi.so.1
Product:	[Fedora] Fedora EPEL	Reporter:	Jak <simfake.mapping+rh>
Component:	mpi4py	Assignee:	Thomas Spura <tomspur>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel7	CC:	pdimitrov, peter, rgm+rh, tomspur
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	mpi4py-1.3.1-2.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-08 19:04:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jak 2016-03-27 04:31:27 UTC

Description of problem:
When running a mpi-enabled python script with "mpirun -n x python script.py", receive the error: ImportError: libmpi.so.1: cannot open shared object file: No such file or directory.

No such file exists on system. In /usr/lib64/openmpi/lib, there exists libmpi.so.12 . Symlinking to this may fix the problem.


Version-Release number of selected component (if applicable):
CentOS 7

How reproducible:
Very. Every time.

Steps to Reproduce:
1. yum install openmpi mpi4py-openmpi 
2. module load mpi/openmpi-x86_64
3. export LD_LIBRARY_PATH=/usr/lib64/openmpi/lib:$LD_LIBRARY_PATH
4. mpirun -n x python script.py

Actual results:
Crash out. ImportError: libmpi.so.1: cannot open shared object file: No such file or directory.

Expected results:
Script to run

Additional info:

Comment 1 Glenn Morris 2016-04-15 19:21:43 UTC

I have the same issue on Scientific Linux 7.2.
The compat-openmpi16 package provides a libmpi.so.1, but simply switching to that module removes mpi4py from PYTHONPATH. Perhaps juat adding
/usr/lib64/compat-openmpi16/lib to the end of LD_LIBRARY_PATH would
be a workaround.

Please rebuild mpi4py to link against the current openmpi rpm.

Comment 2 Glenn Morris 2016-04-18 17:15:55 UTC

PS just to give some more details, looks like the version of OpenMPI in RHEL was updated from 1.6 to 1.10 in RHEL 7.2. Eg:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/7.2_Release_Notes/

"Red Hat Enterprise Linux 7.2 supports only the Open MPI application binary interface (ABI) in version 1.10, which is incompatible with the previously shipped 1.6 version of the Open MPI ABI."

IIRC, it is EPEL policy to support (only?) the latest RHEL point release?

Comment 3 Fedora Update System 2016-04-19 11:39:44 UTC

mpi4py-1.3.1-2.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-1c04eba8b4

Comment 4 Fedora Update System 2016-04-20 15:52:07 UTC

mpi4py-1.3.1-2.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-1c04eba8b4

Comment 5 Fedora Update System 2016-05-08 19:04:48 UTC

mpi4py-1.3.1-2.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.

Comment 6 pdimitrov 2017-01-11 14:41:10 UTC

Just encountered the same issue with

Fedora 25
openmpi-1.10.5-1.fc25.x86_64
python2-mpi4py-openmpi-2.0.0-5.fc25.x86_64

and symlinking solved the problem.