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 2140648 - ypxfrd is not using a static port as configured in /etc/sysconfig/network .
Summary: ypxfrd is not using a static port as configured in /etc/sysconfig/network .
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rpcbind
Version: 8.6
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: Yongcheng Yang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-07 13:52 UTC by Alok Sharma
Modified: 2023-09-23 11:19 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-23 11:19:16 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-7903 0 None Migrated None 2023-09-23 11:19:10 UTC
Red Hat Issue Tracker RHELPLAN-138520 0 None None None 2022-11-07 14:21:00 UTC

Description Alok Sharma 2022-11-07 13:52:00 UTC
Description of problem:

ypxfrd is not using a static port as configured in /etc/sysconfig/network .

Version-Release number of selected component (if applicable):
ypserv-4.1-1.el8.x86_64
RHEL8.6

How reproducible:

Steps to Reproduce:

- From my testbox:
=======
1. Configure NIS server on RHEL8.6 machine

2. Add below in "/etc/sysconfig/network"
-----------
# Created by anaconda
NISDOMAIN = rh8nis.local  #<== change NIS domain a per the environment
YPSERV_ARGS="-p 834"
YPXFRD_ARGS="-p 835"   
----------

Actual results:

 ypxfrd bound to some other port but not on static configured one.
=======
. # rpcinfo -p 
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100009    1   udp   1010  yppasswdd
    100009    1   tcp   1010  yppasswdd
    100007    3   udp   1017  ypbind
    100007    2   udp   1017  ypbind
    100007    1   udp   1017  ypbind
    100007    3   tcp   1017  ypbind
    100007    2   tcp   1017  ypbind
    100007    1   tcp   1017  ypbind
    100004    2   udp    834  ypserv
    100004    1   udp    834  ypserv
    100004    2   tcp    834  ypserv
    100004    1   tcp    834  ypserv
 600100069    1   udp    836  fypxfrd #<== different from static configured port
 600100069    1   tcp    836  fypxfrd
=========


Expected results:

ypxfrd should bind to the port 835 as configured in "/etc/sysconfig/network"

Additional info:

- Also, tried with selinux in permissive mode but results were same in RHEL8.6

- I have tried to configure the same on RHEL7.9 to verify and observed that it is working as expected i.e bound to the static configured port:

- From RHEL7.9 testbox
-------------------
[root@nis ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.9 (Maipo)

[root@nis ~]# cat /etc/sysconfig/network
# Created by anaconda
NISDOMAIN = nis.master.com
YPSERV_ARGS="-p 834"
YPXFRD_ARGS="-p 835"  <=======

[root@nis ~]# getenforce 
Permissive
[root@nis ~]# rpcinfo -p
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100009    1   udp    788  yppasswdd
    100007    2   udp    857  ypbind
    100007    1   udp    857  ypbind
    100007    2   tcp    860  ypbind
    100007    1   tcp    860  ypbind
 600100069    1   udp    835  fypxfrd <========
 600100069    1   tcp    835  fypxfrd
    100004    2   udp    834  ypserv
    100004    1   udp    834  ypserv
    100004    2   tcp    834  ypserv
    100004    1   tcp    834  ypserv
[root@nis ~]# 
-------------------

Comment 1 Ondřej Sloup 2022-11-27 17:33:55 UTC
I'm currently working on the issue and could not reproduce it in the 1MT-RHEL-8.6.0-released.
I used this Google Doc guide (https://docs.google.com/document/d/1-qs5sV-boZs0hfti1viQlsGo2MI0e0C1BpD_0MMIfzs) for NIS setup with turned off firewall and the ports were successfully changed after configuration.
Can you please provide more info about the issue?

Comment 5 Ondřej Sloup 2023-01-27 14:28:35 UTC
I suppose that the bug is in rpcbind component and needs to be rebased so this bug can be fixed. After updating the rpcbind package to 1.2.6, the bug is resolved.

Comment 16 RHEL Program Management 2023-09-23 11:17:07 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 17 RHEL Program Management 2023-09-23 11:19:16 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.