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.
NetApp storage appliances serving NFSv4 are advised to check their configuration
Note that features can be enabled or disabled on a per-minor version basis when using NetApp storage appliances that serve NFSv4.
It is recommended to verify the configuration to ensure that the appropriate features are enabled as desired, for example by using the following Data ONTAP command:
vserver nfs show -vserver <vserver-name> -fields v4.0-acl,v4.0-read-delegation,v4.0-write-delegation,v4.0-referrals,v4.0-migration,v4.1-referrals,v4.1-migration,v4.1-acl,v4.1-read-delegation,v4.1-write-delegation
Description of problem:
Mount the Netapp NFS server with latest RHEL-7.4 client using NFS version 4.1 (which is default). Calling "nfs4_getfacl" always gets failed and emit error "Operation to request attribute not supported.".
Version-Release number of selected component (if applicable):
Start from the first RTT compose of 7.4 (sorry for the delay)
7.4-20170330.1 with kernel 3.10.0-632.el7
How reproducible:
100% easy
Steps to Reproduce:
1. See following.
Actual results:
### Only failed with version *4.1* (or NFSv3) ###
[root@hp-dl385pg8-01 ~]# mount -t nfs netapp-pnfs-02.rhts.eng.pek2.redhat.com:/export/qe-test /mnt/
[root@hp-dl385pg8-01 ~]# nfsstat -m
/mnt from netapp-pnfs-02.rhts.eng.pek2.redhat.com:/export/qe-test
Flags: rw,relatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=null,clientaddr=10.73.4.253,local_lock=none,addr=10.73.4.5
[root@hp-dl385pg8-01 ~]# touch /mnt/test
[root@hp-dl385pg8-01 ~]# nfs4_getfacl /mnt/
Operation to request attribute not supported.
[root@hp-dl385pg8-01 ~]# nfs4_getfacl /mnt/test
Operation to request attribute not supported.
[root@hp-dl385pg8-01 ~]# echo $?
1
[root@hp-dl385pg8-01 ~]# nfs4_setfacl -a "A::OWNER@:RW" /mnt/test
Operation to request attribute not supported.
Failed to instantiate ACL.
[root@hp-dl385pg8-01 ~]# echo $?
1
[root@hp-dl385pg8-01 ~]#
Expected results: Success like NFSv4.0:
### Mounting with version *4.0* acts OK ###
[root@hp-dl385pg8-01 ~]# mount -t nfs netapp-pnfs-02.rhts.eng.pek2.redhat.com:/export/qe-test /mnt/ -o vers=4
[root@hp-dl385pg8-01 ~]# nfsstat -m
/mnt from netapp-pnfs-02.rhts.eng.pek2.redhat.com:/export/qe-test
Flags: rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.73.4.253,local_lock=none,addr=10.73.4.5
[root@hp-dl385pg8-01 ~]# touch /mnt/test
[root@hp-dl385pg8-01 ~]# nfs4_setfacl -a "A::OWNER@:RW" /mnt/test
[root@hp-dl385pg8-01 ~]# nfs4_getfacl /mnt/
A::OWNER@:rwaDxtTnNcCy
A:g:GROUP@:rwaDxtTnNcy
A::EVERYONE@:rwaDxtTnNcy
[root@hp-dl385pg8-01 ~]#
Additional info:
1. Just set component "kernel" as the "nfs4-acl-tools doesn't change (all are "0.3.3-15.el7")
2. I'm not sure whether it's our netapp server's issue. However using the same server, the RHEL-7.3 is OK, mounting with NFSv4.0 is OK.
Also asked Andy Adamson about this here: https://bugzilla.redhat.com/show_bug.cgi?id=1375259#c28
We should document this somewhere in case we have users with the same configuration. Seems like it would be an easy mistake to make.
Also, is there any objection to making this bug public?
(In reply to J. Bruce Fields from comment #7)
> Also, is there any objection to making this bug public?
No objection for me. I file this bug for "kernel" at first and it contains "private" group by default.
Just removing group "private". Feel free to go ahead making your comments public if necessary. Thanks!
Comment 10Steve Whitehouse
2017-05-17 11:19:54 UTC
I've added a release note in the appropriate field above with copy & paste from comment #8. Please review and update as necessary. We should definitely get the docs updated too, so I've added a suitable key word above.
This is sound more like a server configuration problem to me.
and by no means is this a regression since the same failures
happen with 7.3.
This should not be a blocker!
Comment 12Steve Whitehouse
2017-05-17 13:26:29 UTC
They do, but in 7.3 the default was not 4.1, so we do need to investigate the implications carefully
(In reply to Steve Dickson from comment #15)
> not sure what is needed here and why this is a blocker???
(According to Comment #10) this one is to add "Release Note" in case
customers has the same netapp configuration issue, i.e., the netapp
server's ACLs for v4.1 is disabled by default.