Bug#1120481: openmpi: need new upstream release to fix PRRTE remote connection management

[Drew Parsons]

Source: openmpi
Version: 5.0.8-10
Severity: serious
Control: forwarded -1 https://github.com/openpmix/openpmix/issues/3717

Upstream pmix discussion of the scotch build failure in Bug#1120413
and pmix's culpability Bug#1120424 led to the conclusion that there is
a bug in PRRTE 3.0.11, which is included with debian's openmpi 5.0.8.

The upstream discussion is at
https://github.com/openpmix/openpmix/issues/3717

scotch build tests of ptscotch fail with errors like
https://buildd.debian.org/status/fetch.php?pkg=scotch&arch=amd64&ver=7.0.10-1exp3&stamp=1762595061&raw=0
test 148
        Start 148: dgpart_1

148: Test command: /usr/bin/mpiexec "-n" "3" "/build/scotch-7.0.10/obj-x86_64-linux-gnu/bin/dgpart" "9" "/build/scotch-7.0.10/src/check/data/bump.grf" "/dev/null" "-vmt"
148: Working Directory: /build/scotch-7.0.10/obj-x86_64-linux-gnu/src/check
148: Test timeout computed to be: 10000000
148: --------------------------------------------------------------------------
148: You requested support for remote tool connections, but no non-loopback
148: interfaces were found after applying any include or exclude directives:
148: 
148:   Include:    NULL
148:   Exclude:    NULL
148:   Available:  lo
148: 
148: Please adjust your include or exclude to allow selection of a
148: non-loopback interface.

The problem occurs when only the loopback lo interface is available,
and no other remote interfaces, which is the case in the chroot
environment of our buildds. An upstream patch applied to pmix
6.0.0+really5.0.9-2 did not resolve it.

The same kind of error is seen in
mumps https://buildd.debian.org/status/fetch.php?pkg=mumps&arch=arm64&ver=5.8.1-1exp1&stamp=1762774445&raw=0
mpi4py https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/mpi4py_4.1.1-1.rbuild.log.gz
hypre is also failing to build, though not reporting its error

PMIx upstream advises (issue#3717) that ultimately the error is
actually in PRRTE 3.0.11, and has been fixed in PRRTE 3.0.12.

OpenMPI 5.0.9 has been released, bringing PRRTE 3.0.12 with it.
In lieu of a separate external prrte package, can we upgrade openmpi
to 5.0.9?

Marking severity: serious since the bug causes many packages to FTBFS.

"Many" actually means *all* packages using openmpi (and testing at
build time), since the bug is triggered by the buildd environment with
loopback lo only (no remote internet access when building debian packages)