Bug 1998836

Summary: openmpi runtime error on armv7hl
Product: [Fedora] Fedora Reporter: david08741
Component: openmpiAssignee: Doug Ledford <dledford>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 36CC: dakingun, dledford, hladky.jiri, orion, pkfed
Target Milestone: ---   
Target Release: ---   
Hardware: armv7hl   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-25 15:55:07 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:
Bug Depends On:    
Bug Blocks: 485251    

Description david08741 2021-08-29 09:43:28 UTC
Description of problem:
During running test for BOUT++, openmpi errors on armv7hl

Traceback (most recent call last):
  File "/builddir/build/BUILD/BOUT++-v4.4.0/build_openmpi/tests/integrated/test-invpar/./runtest", line 49, in <module>
    s, out = launch_safe(
  File "/usr/lib/python3.10/site-packages/boututils/run_wrapper.py", line 291, in launch_safe
    raise RuntimeError(
RuntimeError: Run failed with 1.
Command was:
./test_invpar 'input=ballooning(exp(-y*y)*cos(z)*gauss(x,0.2))' test_location=CELL_ZLOW
Output was
[buildvm-a32-26.iad2.fedoraproject.org:15111] OPAL ERROR: Unreachable in file ext3x_client.c at line 112
*** An error occurred in MPI_Init
*** on a NULL communicator
*** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
***    and potentially your MPI job)
[buildvm-a32-26.iad2.fedoraproject.org:15111] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed!
--------------------------------------------------------------------------
Primary job  terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
--------------------------------------------------------------------------
[buildvm-a32-26.iad2.fedoraproject.org:15106] PMIX ERROR: UNREACHABLE in file ptl_tcp_component.c at line 1801
[buildvm-a32-26.iad2.fedoraproject.org:15106] PMIX ERROR: UNREACHABLE in file ptl_tcp_component.c at line 1849
[buildvm-a32-26.iad2.fedoraproject.org:15106] PMIX ERROR: UNREACHABLE in file ptl_tcp_component.c at line 1801
[buildvm-a32-26.iad2.fedoraproject.org:15106] PMIX ERROR: UNREACHABLE in file ptl_tcp_component.c at line 1849
--------------------------------------------------------------------------
mpirun detected that one or more processes exited with non-zero status, thus causing
the job to be terminated. The first process to do so was:
  Process name: [[5033,1],1]
  Exit code:    1
--------------------------------------------------------------------------

Version-Release number of selected component (if applicable):
DEBUG util.py:446:   openmpi                                 armv7hl  4.1.1-3.fc35             build  2.1 M

How reproducible:
Not sure, I think sometimes

Steps to Reproduce:
1. try to build bout++ on armv7hl

Actual results:
openmpi errors, see above

Expected results:
No errors

Additional info:
I don't think having openmpi on armv7 is important

Comment 1 Ben Cotton 2022-02-08 21:43:28 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 2 Ben Cotton 2023-04-25 16:44:06 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ludek Smid 2023-05-25 15:55:07 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.