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.
DescriptionMark Williamson
2023-08-14 17:26:06 UTC
Description of problem:
Server exports a disk to two hosts via NFS (/etc/export shown):
/foo host1(ro,sync,no_subtree_check) host2(ro,sync,no_subtree_check)
On boot up of server we see in the nfs-server.service logs:
exportfs: Failed to resolve host1
exportfs: Failed to resolve host2
If one restarts the nfs-server.service, post boot, it resolves the two hosts and everything works.
Version-Release number of selected component (if applicable):
How reproducible:
Every reboot
Steps to Reproduce:
1. Reboot machine
2.
3.
Actual results:
exportfs: Failed to resolve host1
exportfs: Failed to resolve host2
Expected results:
host{1,2} are resolved and the nfs export works
Additional info:
Could be related: https://bugzilla.redhat.com/show_bug.cgi?id=1409012
(In reply to Mark Williamson from comment #0)
> ...
> Additional info:
> Could be related: https://bugzilla.redhat.com/show_bug.cgi?id=1409012
The above bug 1409012 is to add "network-online" as nfs-server dependencies (ensure the network is completely up before the NFS server is started) and this is not changed in rhel9 for now:
[root@rhel-9-latest ~]# systemctl cat nfs-server | grep network-online
Wants=rpcbind.socket network-online.target
After=network-online.target local-fs.target
[root@rhel-9-latest ~]# systemctl list-dependencies nfs-server
nfs-server.service
○ ├─auth-rpcgss-module.service
○ ├─nfs-idmapd.service
○ ├─nfs-mountd.service
○ ├─nfsdcld.service
○ ├─proc-fs-nfsd.mount
● ├─rpc-statd-notify.service
○ ├─rpc-statd.service
● ├─rpcbind.socket
● ├─system.slice
● ├─network-online.target <<<<<<<<<
● │ └─NetworkManager-wait-online.service
● └─network.target
[root@rhel-9-latest ~]# rpm -q nfs-utils
nfs-utils-2.5.4-20.el9.x86_64
[root@rhel-9-latest ~]#
We have a testcase and it works well. Maybe some other configs cause the failure in your environment.
Thank you for looking into this.
Someone had disabled NetworkManager-wait-online.service on the server because it was timing-out/failing at startup, hence was causing this issue. I am going to experiment with Environment=NM_ONLINE_TIMEOUT= for that service.
Please consider this bug report closed.
Thanks,
Mark
Description of problem: Server exports a disk to two hosts via NFS (/etc/export shown): /foo host1(ro,sync,no_subtree_check) host2(ro,sync,no_subtree_check) On boot up of server we see in the nfs-server.service logs: exportfs: Failed to resolve host1 exportfs: Failed to resolve host2 If one restarts the nfs-server.service, post boot, it resolves the two hosts and everything works. Version-Release number of selected component (if applicable): How reproducible: Every reboot Steps to Reproduce: 1. Reboot machine 2. 3. Actual results: exportfs: Failed to resolve host1 exportfs: Failed to resolve host2 Expected results: host{1,2} are resolved and the nfs export works Additional info: Could be related: https://bugzilla.redhat.com/show_bug.cgi?id=1409012