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:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

System which is ready for Kerberized mounts (.i.e. fully configured, rpc.gssd running, nfs-secure service started...) does not seem to "like" to mount NFSv4 share with anything else than krb5p security flavor.
But it can happen, that the share we want to mount is exported with system authentication only.

right now command:
mount netapp:/vol/vol0 /mnt
- fails because /vol/vol0 is not exported with krb5p security flavor

workaround:
mount -o sec=sys netapp:/vol/vol0 /mnt

Expectations:
mount netapp:/vol/vol0 /mnt
- I would expect mount will try (with nothing specified in /etc/nfsmount.conf) all flavors in this order - krb5p -> if fails then krb5i -> if fails then -> krb5 -> if fails then sys.

Ideally we should somehow "detect" which security flavor the server offers for the requested share. Not sure if that's possible.

Steve D - does this bug make sense to you or do you need clarification?

(In reply to Dave Wysochanski from comment #3)
> Steve D - does this bug make sense to you or do you need clarification?

Nope.... 

Would it be possible to get a binary wireshark network trace?

Hi, there is a RHEL support case #01525032 opened regarding this one.
Please reach there for the required packet trace.