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.

Description of problem:
The nfs-utils junction support doesn't work due to the fix of Bug 2148353

Pass in nfs-utils-2.5.4-18.el9 https://beaker.engineering.redhat.com/jobs/7941942
Fail in nfs-utils-2.5.4-19.el9 https://beaker.engineering.redhat.com/jobs/7941943

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
# beaker job https://beaker.engineering.redhat.com/jobs/7941943 nfs-utils-2.5.4-19.el9
###
$ nfsref --type=nfs-basic add /mnt/testarea/junction fsqe-r6515-02.fs.lab.eng.bos.redhat.com /
nfsref: Failed to add NFS location metadata to /mnt/testarea/junction: FEDFS_ERR_IO
$ nfsref --type=nfs-basic lookup /mnt/testarea/junction
nfsref: /mnt/testarea/junction is not an nfs-basic junction


Expected results:
# beaker job https://beaker.engineering.redhat.com/jobs/7941942 nfs-utils-2.5.4-18.el9
###
$ nfsref --type=nfs-basic add /mnt/testarea/junction dell-per740-89.rhts.eng.pek2.redhat.com /
Created junction /mnt/testarea/junction
$ nfsref --type=nfs-basic lookup /mnt/testarea/junction
dell-per740-89.rhts.eng.pek2.redhat.com:/

	NFS port:	2049
	Valid for:	0
	Currency:	-1
	Flags:		varsub(false)
	GenFlags:	writable(false), going(false), split(true)
	TransFlags:	rdma(true)
	Class:		simul(0), handle(0), fileid(0)
	Class:		writever(0), change(0), readdir(0)
	Read:		rank(0), order(0)
	Write:		rank(0), order(0)



Additional info:

Here is the problem

--      tmp = open(pathname, O_DIRECTORY);
-+      tmp = open(pathname, O_PATH|O_DIRECTORY);

I remove the O_PATH and everything started to
work... not clear as to way it needed in the
first place. 

I'm working on getting a scratch build.. I
get some goofy Python

This issue has been fixed in nfs-utils-2.5.4-20.el9 now: https://beaker.engineering.redhat.com/jobs/8163907

Looks like a reasonable fix. I think I only added O_PATH in order to make mountd's footprint lighter, but if the reproducer works without that, then it should be fine.

No new issue found from the regression tests against nfs-utils-2.5.4-20.el9

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 (nfs-utils 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:6692