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 1394720 - Local ISO domain is inaccessible on el7.3
Summary: Local ISO domain is inaccessible on el7.3
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nfs-utils
Version: 7.3
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: Yongcheng Yang
URL:
Whiteboard:
Depends On:
Blocks: 1393798
TreeView+ depends on / blocked
 
Reported: 2016-11-14 10:11 UTC by Nikolai Sednev
Modified: 2021-04-15 12:09 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-15 07:28:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1264387 0 unspecified CLOSED change to use lockd.conf instead of sysconfig to set module lockd parameters 2021-02-22 00:41:40 UTC

Internal Links: 1264387

Description Nikolai Sednev 2016-11-14 10:11:39 UTC 
Description of problem:
Cloning from https://bugzilla.redhat.com/show_bug.cgi?id=1393798.
The issue is well described in https://bugzilla.redhat.com/show_bug.cgi?id=1393798#c0 and https://bugzilla.redhat.com/show_bug.cgi?id=1393798#c3
The work around also documented in https://access.redhat.com/solutions/2761021.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1.Follow the steps from https://bugzilla.redhat.com/show_bug.cgi?id=1393798.
2.
3.

Actual results:
# netstat -tulnp|grep '32769\|32803'
Will return nothing in this case.

Expected results:
tcp        0      0 0.0.0.0:32803           0.0.0.0:*               LISTEN      -                   
udp        0      0 0.0.0.0:32769           0.0.0.0:*                           - 


Additional info:
Comment 3 Yongcheng Yang 2016-12-23 07:56:24 UTC 
As Bug #1264387 Comment #10 said, "how lockd kernel parameters are set will be changing in 7.3".

As a result, the previous setting (i.e. LOCKD_TCPPORT=32803 LOCKD_UDPPORT=32769) in /etc/sysconfig/nfs won't effect after updating beyond nfs-utils-1.3.0-0.26.el7 and rebooting.

Steps to Reproduce:
1. echo -e "LOCKD_TCPPORT=32803 \nLOCKD_UDPPORT=32769" > /etc/sysconfig/nfs
2. update nfs-utils beyond 1.3.0-0.26.el7 and reboot
3. netstat -tulnp | grep '32769\|32803'

Additional info:
The workaround is to update previous setting into the new introduced configure file /etc/modprobe.d/lockd.conf


(In reply to CAPELLE Benoit from Bug #1393798 comment #0)
> Description of problem:
> Red Hat released RHEL 7.3
> 
> Package nfs-utils was upgraded from nfs-utils-1.3.0-0.21.el7_2.1 to
> nfs-utils-1.3.0-0.33.el7
> 
> NFS lockd parameters have now to be set in a new file:
> $ rpm -qi --changelog nfs-utils
> ...
> * Mon May 16 2016 Steve Dickson <steved> 1.3.0-0.26
> ...
> - lockd: added lockd.conf to set module parameters (bz 1264387)
> ...
> 
> /usr/share/ovirt-engine/setup/plugins/ovirt-engine-setup/ovirt-engine/system/
> nfs.py is setting NFS lockd ports in file /etc/sysconfig/nfs
> LOCKD_TCPPORT=32803
> LOCKD_UDPPORT=32769
> 
> /usr/share/ovirt-engine/firewalld/ovirt-engine/ovirt-nfs.xml.in is setting
> NFS lockd ports
> ...
>     <port protocol="udp" port="32769"/>
>     <port protocol="tcp" port="32803"/>
> ...
> 
> NFS lockd won't use parameters set in /etc/sysconfig/nfs. After rebooting,
> lockd is not listening on TCP port 32803 and UDP port 32769. Clients can get
> stuck if trying to acquire lock as firewall is filtering ports.
> 
> Version-Release number of selected component (if applicable):
> RHEL 7.3
> ovirt-engine-setup-plugin-ovirt-engine-4.0.4.4-1.el7
> nfs-utils-1.3.0-0.33.el7
> 
> How reproducible:
> Upgrade to RHEL 7.3. Reboot and check open TCP/UDP ports
> 
> Steps to Reproduce:
> 1. yum update
> 2. reboot
> 3. netstat -tulnp|grep '32769\|32803'
> 
> Actual results:
> null
> 
> 
> Expected results:
> tcp        0      0 0.0.0.0:32803           0.0.0.0:*               LISTEN  
> -                   
> udp        0      0 0.0.0.0:32769           0.0.0.0:*                       
> - 
> 
> Additional info:
> Setting NFS lockd ports in /etc/modprobe.d/lockd.conf resolves the issue:
> options lockd nlm_tcpport=32803
> options lockd nlm_udpport=32769
Comment 7 RHEL Program Management 2021-01-15 07:28:34 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.