Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 953095[details]
example session
Description of problem:
The current version of the package has broken the ability to run openmpi-1.4
binaries that it had in v. 1.4.3-1. (I expressed surprise in #1159507 that it
would work to mix 1.4 and 1.5 runtime components, and then thought I'd better
check that it does.) I can't find a statement about it, but the maintainers
have said that there's no guarantee of compatibility of the ORTE components
between different versions, even within the same series which is compatible at
the application ABI level.
I haven't checked the package build, but it appears experimentally to have ORTE
components from 1.5 and just libmpi from both 1.4 and 1.5.
If Red Hat intend to support openmpi 1.4, 1.5/6, and 1.8, there need to be
separate packages/environments for each.
Version-Release number of selected component (if applicable):
1.4.3-1.2.el6.x86_64
How reproducible:
Steps to Reproduce:
See the attached session log with a binary from an RHEL5 cluster using
openmpi-1.4 through an upgrade from the original version of the package.
compat-openmpi packaging will be reworked in bug 1158864 to have distinct compat subpackages for openmpi 1.4 and 1.5 (and possibly more).
*** This bug has been marked as a duplicate of bug 1158864 ***
Created attachment 953095 [details] example session Description of problem: The current version of the package has broken the ability to run openmpi-1.4 binaries that it had in v. 1.4.3-1. (I expressed surprise in #1159507 that it would work to mix 1.4 and 1.5 runtime components, and then thought I'd better check that it does.) I can't find a statement about it, but the maintainers have said that there's no guarantee of compatibility of the ORTE components between different versions, even within the same series which is compatible at the application ABI level. I haven't checked the package build, but it appears experimentally to have ORTE components from 1.5 and just libmpi from both 1.4 and 1.5. If Red Hat intend to support openmpi 1.4, 1.5/6, and 1.8, there need to be separate packages/environments for each. Version-Release number of selected component (if applicable): 1.4.3-1.2.el6.x86_64 How reproducible: Steps to Reproduce: See the attached session log with a binary from an RHEL5 cluster using openmpi-1.4 through an upgrade from the original version of the package.