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.

+++ This bug was initially created as a clone of Bug #2107650 +++


--- Additional comment from Dave Wysochanski on 2022-08-01 13:20:00 UTC ---

SteveD - it looks like you took this into upstream: https://lore.kernel.org/all/fd568705-8036-b556-5a43-9fb59b4cddd4@redhat.com/
Are there any further development concerns or are we just waiting on QE ack for the right RHEL8 release?

--- Additional comment from Steve Dickson on 2022-08-01 13:48:48 UTC ---

(In reply to Dave Wysochanski from comment #2)
> SteveD - it looks like you took this into upstream:
> https://lore.kernel.org/all/fd568705-8036-b556-5a43-9fb59b4cddd4@redhat.com/
> Are there any further development concerns or are we just waiting on QE ack
> for the right RHEL8 release?
I just asked for it rhel8.7

commit d81c89c161521c619e5863cd44714094ba14e4b9 (tag: libtirpc-1-3-3-rc3)
Author: Roberto Bergantinos Corpas <rbergant>
Date:   Thu Jul 14 15:54:21 2022 -0400

    rpcb_clnt.c add mechanism to try v2 protocol first

This should be fixed with the rebase bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2118157

*** This bug has been marked as a duplicate of bug 2118157 ***