Bug 1957060

Summary: Storage class aws-efs not honoring mountoptions
Product: OpenShift Container Platform Reporter: DzungDo <ddo>
Component: StorageAssignee: Tomas Smetana <tsmetana>
Storage sub component: Storage QA Contact: Chao Yang <chaoyang>
Status: CLOSED WONTFIX Docs Contact:
Severity: low    
Priority: low CC: aos-bugs
Version: 3.11.0   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-17 10:08:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description DzungDo 2021-05-04 23:39:49 UTC
Description of problem:

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

How reproducible:

Steps to Reproduce:
1. Deploy aws-efs provisioner 
2. Set mount options under "mountOptions:"
3. Deploy a pod with a PVC and provisioner will provision a PV
4. Run the command to check for nfs mount on the pod: oc rsh -n <NS> <POD> /bin/sh -c 'mount | grep nfs'

Actual results:
<EFS_ID>.amazonaws.com:/<PATH> on <MOUNT_POINT> type nfs4 (rw,relatime,vers=4.1,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=<IP>,local_lock=none,addr=<IP>)

Expected results:
Should show the NFS mount options specified in the StorageClass

Image version for the EFS provisioner pod:

Comment 1 Tomas Smetana 2021-05-06 11:02:59 UTC
The AWS EFS provisioner in 3.11 was a tech-preview feature. The upstream for this external provisioner is long gone, so without some *very strong* business justification why is this required in 3.11, this is not going to be fixed.