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.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (libvma bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:6449
RHEL-9.3.0-20230803.31 has "libvma-9.8.20-3.el9.x86_64 & libvma-utils-9.8.20-3.el9.x86_64" and vma tests passed. Therefore, moving this to "Verified". $ grep DISTRO /etc/motd | uniq | tr -d " " DISTRO=RHEL-9.3.0-20230803.31 $ cat /etc/redhat-release Red Hat Enterprise Linux release 9.3 Beta (Plow) $ uname -r 5.14.0-348.el9.x86_64 $ rpm -q rdma-core openmpi mpitests-openmpi ucx libvma libvma-utils rdma-core-46.0-1.el9.x86_64 openmpi-4.1.1-7.el9.x86_64 mpitests-openmpi-7.1-2.el9.x86_64 ucx-1.14.1-1.el9.1.x86_64 libvma-9.8.20-3.el9.x86_64 libvma-utils-9.8.20-3.el9.x86_64 $ vma test results on rdma-qe-40/rdma-qe-41 & Beaker job J:8150503: 5.14.0-348.el9.x86_64, rdma-core-46.0-1.el9, mlx5, ib0, ConnectX-7 & mlx5_0 Result | Status | Test ---------+--------+------------------------------------ PASS | 0 | sockperf pingpong multicast PASS | 0 | sockperf throughput multicast PASS | 0 | sockperf throughput unicast PASS | 0 | sockperf pingpong unicast PASS | 0 | sockperf (100 sockets) pingpong multicast PASS | 0 | sockperf (100 sockets) pingpong unicast PASS | 0 | sockperf pingpong multicast pkey/vlan PASS | 0 | sockperf pingpong unicast pkey/vlan Checking for failures and known issues: no test failures vma test results on rdma-qe-40/rdma-qe-41 & Beaker job J:8150503: 5.14.0-348.el9.x86_64, rdma-core-46.0-1.el9, mlx5, roce.45, ConnectX-7 & mlx5_1 Result | Status | Test ---------+--------+------------------------------------ PASS | 0 | sockperf pingpong multicast PASS | 0 | sockperf throughput multicast PASS | 0 | sockperf throughput unicast PASS | 0 | sockperf pingpong unicast PASS | 0 | sockperf (100 sockets) pingpong multicast PASS | 0 | sockperf (100 sockets) pingpong unicast PASS | 0 | sockperf pingpong multicast pkey/vlan PASS | 0 | sockperf pingpong unicast pkey/vlan Checking for failures and known issues: no test failures