This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2111084 - [RHEL9.1] all mvapich2 benchmarks timeout when run with "mpirun_rsh" command on HFI OPA device
Summary: [RHEL9.1] all mvapich2 benchmarks timeout when run with "mpirun_rsh" command ...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: mvapich2
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Kamal Heib
QA Contact: Brian Chae
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-26 13:10 UTC by Brian Chae
Modified: 2023-09-21 15:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-21 15:05:02 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-6159 0 None Migrated None 2023-09-21 15:04:56 UTC
Red Hat Issue Tracker RHELPLAN-129105 0 None None None 2022-07-26 13:11:16 UTC

Description Brian Chae 2022-07-26 13:10:17 UTC 
Description of problem:

all mvapich2 benchmarks fail with timeouts when run with "mpirun_rsh" command, on HFI OPA device; while all benchmarks run successfully when run with "mpirun" command. This is a REGRESSION from RHEL-9.1.0-20220524.0 build, where NO SUCH failures observed.


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

Clients: rdma-qe-15
Servers: rdma-qe-14

DISTRO=RHEL-9.1.0-20220718.0

+ [22-07-20 23:40:51] cat /etc/redhat-release
Red Hat Enterprise Linux release 9.1 Beta (Plow)

+ [22-07-20 23:40:51] uname -a
Linux rdma-qe-15.rdma.lab.eng.rdu2.redhat.com 5.14.0-130.el9.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Jul 15 08:52:03 EDT 2022 x86_64 x86_64 x86_64 GNU/Linux

+ [22-07-20 23:40:51] cat /proc/cmdline
BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.14.0-130.el9.x86_64 root=UUID=abd4cfd1-c58e-4c29-836b-d0f6ee695d89 ro intel_idle.max_cstate=0 processor.max_cstate=0 console=tty0 rd_NO_PLYMOUTH intel_iommu=on crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M resume=UUID=95f34601-5d88-4b38-bff8-afc96012d612 console=ttyS1,115200

+ [22-07-20 23:40:51] rpm -q rdma-core linux-firmware
rdma-core-37.2-1.el9.x86_64
linux-firmware-20220509-126.el9.noarch

+ [22-07-20 23:40:51] tail /sys/class/infiniband/hfi1_0/fw_ver
1.27.0
+ [22-07-20 23:40:51] lspci
+ [22-07-20 23:40:51] grep -i -e ethernet -e infiniband -e omni -e ConnectX
02:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe
02:00.1 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe
03:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe
03:00.1 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe
04:00.0 Fabric controller: Intel Corporation Omni-Path HFI Silicon 100 Series [discrete] (rev 10)


Installed:
  mpitests-mvapich2-psm2-5.8-1.el9.x86_64    mvapich2-psm2-2.3.6-3.el9.x86_64   


How reproducible:

100%

Steps to Reproduce:
1. bring up the RDMA hosts mentioned above with RHEL9.1 build
2. set up RDMA hosts for mvapich2 benchamrk tests
3. run one of the mvapich2 benchmark with "mpirun_rsh" command, as the following:

timeout --preserve-status --kill-after=5m 3m mpirun_rsh -np 2 -hostfile /root/hfile_one_core PSM2_PKEY=0x8001 mpitests-IMB-MPI1 PingPong -time 1.5



Actual results:

[rdma-qe-14.rdma.lab.eng.rdu2.redhat.com:mpi_rank_0][mv2_psm_err_handler] PSM error handler: Operation timed out : Detected connection timeout: rdma-qe-15
psm_ep_connect failed with error Operation timed out
[rdma-qe-15.rdma.lab.eng.rdu2.redhat.com:mpi_rank_1][mv2_psm_err_handler] PSM error handler: Operation timed out : Detected connection timeout: LID=6:7.0
psm_ep_connect failed with error Operation timed out
[rdma-qe-14.rdma.lab.eng.rdu2.redhat.com:mpi_rank_0][psm_connect_alltoall] psm_connect_alltoall failed
[rdma-qe-15.rdma.lab.eng.rdu2.redhat.com:mpi_rank_1][psm_connect_alltoall] psm_connect_alltoall failed
[rdma-qe-15.rdma.lab.eng.rdu2.redhat.com:mpirun_rsh][signal_processor] Caught signal 15, killing job
[rdma-qe-15.rdma.lab.eng.rdu2.redhat.com:mpirun_rsh][signal_processor] Caught signal 15, killing job
+ [22-07-21 03:20:02] __MPI_check_result 1 mpitests-mvapich2-psm2 IMB-MPI1 PingPong mpirun_rsh /root/hfile_one_core



Expected results:

Normal execution of the benchmarks with stats output


Additional info: 

This same issue exists on DISTRO=RHEL-9.1.0-20220710.3 build, as well
Comment 1 Brian Chae 2023-01-19 09:56:38 UTC 
The benchmarks with "mpirun" were reported as PASS. However, that was erroneous result.
In fact all benchmarks with "mpirun" was also reporting errors, as the following:

All of them reported the following error message:

+ [23-01-18 16:26:01] timeout --preserve-status --kill-after=5m 3m mpirun -hostfile /root/hfile_one_core -np 2 mpitests-IMB-MPI1 PingPong -time 1.5
[rdma-qe-15.rdma.lab.eng.rdu2.redhat.com:mpi_rank_1][mv2_psm_err_handler] PSM error handler: Operation timed out : Detected connection timeout: LID=1:7.0
psm_ep_connect failed with error Operation timed out
[rdma-qe-15.rdma.lab.eng.rdu2.redhat.com:mpi_rank_1][psm_connect_alltoall] psm_connect_alltoall failed
[rdma-qe-14.rdma.lab.eng.rdu2.redhat.com:mpi_rank_0][mv2_psm_err_handler] PSM error handler: Operation timed out : Detected connection timeout: rdma-qe-15
psm_ep_connect failed with error Operation timed out
[rdma-qe-14.rdma.lab.eng.rdu2.redhat.com:mpi_rank_0][psm_connect_alltoall] psm_connect_alltoall failed

In summary, all benchmarks failed for the same reason as stated in this bugzilla headline.
Comment 2 RHEL Program Management 2023-09-21 14:39:26 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 3 RHEL Program Management 2023-09-21 15:05:02 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.