Bug 789150 - SGE integration broken in openmpi-1.5.3
Summary: SGE integration broken in openmpi-1.5.3
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: openmpi
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jay Fenlason
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-09 23:19 UTC by Joshua Baker-LePain
Modified: 2014-08-31 23:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-05 20:50:22 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Joshua Baker-LePain 2012-02-09 23:19:34 UTC 
Description of problem:
OpenMPI automatically detects when it is running under SGE (aka gridengine) and uses qrsh to launch remote tasks rather than ssh.  This integration is broken in 1.5.3 as included in 6.2.

Version-Release number of selected component (if applicable):
openmpi-1.5.3-3

How reproducible:
Every time.

Steps to Reproduce:
1. Launch an OpenMPI-1.5.3 program using SGE
2.
3.
  
Actual results:
OpenMPI attemts to use ssh

Expected results:
OpenMPI uses qrsh

Additional info:
Upstream claims this was fixed in 1.5.4.  See <https://svn.open-mpi.org/trac/ompi/ticket/2763>.
Comment 2 RHEL Program Management 2012-05-03 05:35:43 UTC 
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 3 Jay Fenlason 2012-06-04 19:06:53 UTC 
It looks like this should be fixed by the OpenMPI upgrade in Red Hat Enterprise Linux 6.3.  Can you test the 6.3 beta version and report whether this is still broken?
Comment 4 Joshua Baker-LePain 2012-06-05 20:36:42 UTC 
That version does indeed fix it -- thanks!
Note You need to log in before you can comment on or make changes to this bug.