mountOptions in storageClass ignored

[bdols]

Description

I create a storageClass with mountOptions for noatime but it is mounted with relatime:

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  annotations:
    cas.openebs.io/config: |
      - name: StorageType
        value: "device"
      - name: FSType
        value: "xfs"
    k8s.inky.com/type: storage-definitions
    openebs.io/cas-type: local
  creationTimestamp: "2023-10-25T18:19:33Z"
  labels:
    kustomize.toolkit.fluxcd.io/name: storageclasses
    kustomize.toolkit.fluxcd.io/namespace: flux-system
  name: openebs-device-xfs
  resourceVersion: "95634991"
  uid: 64d0034c-b0cb-4d5f-be10-5af3161cdedc
mountOptions:
- rw
- noatime
provisioner: openebs.io/local
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer

Expected Behavior

the volume is mounted with noatime

Current Behavior

the volume is mounted with relatime:
$ mount | grep data
/dev/nvme1n1 on /usr/share/elasticsearch/data type xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota)

note other mount points are mounted with noatime, with no user supplied configuration, such as:
$ mount |grep noatime
/dev/nvme0n1p1 on /mnt/elastic-internal/scripts type xfs (ro,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota)

Possible Solution

Steps to Reproduce

Screenshots

Your Environment

This is EKS 1.27 with Elastic Operator 2.9.

Labels:            openebs.io/cas-type=local-device
Annotations:       local.openebs.io/blockdeviceclaim: bdc-pvc-4fc79c72-73c7-4afe-986d-8955ed5ba384
                   pv.kubernetes.io/provisioned-by: openebs.io/local
Finalizers:        [kubernetes.io/pv-protection]
StorageClass:      openebs-device-xfs
Status:            Bound
Claim:             prod-es-api/elasticsearch-data-elastic-es-data-im4gn-0
Reclaim Policy:    Delete
Access Modes:      RWO
VolumeMode:        Filesystem
Capacity:          6480Gi
Node Affinity:
  Required Terms:
    Term 0:        kubernetes.io/hostname in [ip-10-1-1-1.ec2.internal]
Message:
Source:
    Type:  LocalVolume (a persistent volume backed by local storage on a node)
    Path:  /dev/disk/by-id/nvme-Amazon_EC2_NVMe_Instance_Storage_AWS2237581B2AD77D83C
Events:    <none>

and the PVC:

Namespace:     prod-es-api
StorageClass:  openebs-device-xfs
Status:        Bound
Volume:        pvc-4fc79c72-73c7-4afe-986d-8955ed5ba384
Labels:        common.k8s.elastic.co/type=elasticsearch
               elasticsearch.k8s.elastic.co/cluster-name=elastic
               elasticsearch.k8s.elastic.co/statefulset-name=elastic-es-data-im4gn
Annotations:   pv.kubernetes.io/bind-completed: yes
               pv.kubernetes.io/bound-by-controller: yes
               volume.beta.kubernetes.io/storage-provisioner: openebs.io/local
               volume.kubernetes.io/selected-node: ip-10-1-1-1.ec2.internal
               volume.kubernetes.io/storage-provisioner: openebs.io/local
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      6480Gi
Access Modes:  RWO
VolumeMode:    Filesystem
Used By:       elastic-es-data-im4gn-0
Events:
  Type    Reason                 Age                   From                                                                                                Message
  ----    ------                 ----                  ----                                                                                                -------
  Normal  WaitForPodScheduled    34m (x321 over 114m)  persistentvolume-controller                                                                         waiting for pod elastic-es-data-im4gn-0 to be scheduled
  Normal  Provisioning           32m                   openebs.io/local_openebs-localpv-provisioner-7c8d9f689f-6gfl2_6a76a399-7ab8-4cb0-a6e6-66edfad57585  External provisioner is provisioning volume for claim "prod-es-api/elasticsearch-data-elastic-es-data-im4gn-0"
  Normal  ProvisioningSucceeded  32m                   openebs.io/local_openebs-localpv-provisioner-7c8d9f689f-6gfl2_6a76a399-7ab8-4cb0-a6e6-66edfad57585  Successfully provisioned volume pvc-4fc79c72-73c7-4afe-986d-8955ed5ba384

kernel: 5.10.186-179.751.amzn2.aarch64
Linux ip-10-1-1-1.ec2.internal 5.10.192-183.736.amzn2.aarch64 #1 SMP Wed Sep 6 21:15:30 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

santized NDM logs:

I1025 23:10:14.108899       7 eventhandler.go:69] Processing details for /dev/nvme1n1
I1025 23:10:14.109031       7 udevprobe.go:294] device: /dev/nvme1n1, Model: Amazon EC2 NVMe Instance Storage filled by udev probe
I1025 23:10:14.109041       7 udevprobe.go:298] device: /dev/nvme1n1, WWN: nvme.1d0f-4157533232333735383142324144373744383343-416d617a6f6e20454332204e564d6520496e7374616e63652053746f72
616765-00000001 filled by udev probe
I1025 23:10:14.109045       7 udevprobe.go:302] device: /dev/nvme1n1, Serial: AWS22<seria>L filled by udev probe
I1025 23:10:14.109054       7 probe.go:119] details filled by udev probe
I1025 23:10:14.109110       7 sysfsprobe.go:97] blockdevice path: /dev/nvme1n1 capacity :7500000000000 filled by sysfs probe.
I1025 23:10:14.109143       7 sysfsprobe.go:125] blockdevice path: /dev/nvme1n1 logical block size :512 filled by sysfs probe.
I1025 23:10:14.109171       7 sysfsprobe.go:137] blockdevice path: /dev/nvme1n1 physical block size :512 filled by sysfs probe.
I1025 23:10:14.109199       7 sysfsprobe.go:149] blockdevice path: /dev/nvme1n1 hardware sector size :512 filled by sysfs probe.
I1025 23:10:14.109230       7 sysfsprobe.go:160] blockdevice path: /dev/nvme1n1 drive type :SSD filled by sysfs probe.
I1025 23:10:14.109237       7 probe.go:119] details filled by sysfs probe
E1025 23:10:14.109264       7 smartprobe.go:101] map[errorCheckingConditions:the device type is not supported yet, device type: "NVMe"]
I1025 23:10:14.109277       7 probe.go:119] details filled by smart probe
I1025 23:10:14.109435       7 mountprobe.go:134] no mount point found for /dev/nvme1n1. clearing mount points if any
I1025 23:10:14.109444       7 probe.go:119] details filled by mount probe
I1025 23:10:14.116009       7 probe.go:119] details filled by blkid probe
I1025 23:10:14.116031       7 usedbyprobe.go:122] device: /dev/nvme1n1 is not having any zfs partitions
I1025 23:10:14.116111       7 probe.go:119] details filled by used-by probe
I1025 23:10:14.116120       7 probe.go:119] details filled by Custom Tag Probe
I1025 23:10:14.116127       7 addhandler.go:53] device: /dev/nvme1n1 does not exist in cache, the device is now connected to this node
I1025 23:10:14.116146       7 osdiskexcludefilter.go:129] applying os-filter regex ^/dev/nvme0n1(p[0-9]+)?$ on /dev/nvme1n1
I1025 23:10:14.116178       7 osdiskexcludefilter.go:129] applying os-filter regex ^/dev/nvme0n1(p[0-9]+)?$ on /dev/nvme1n1
I1025 23:10:14.116202       7 eventhandler.go:82] Processed details for /dev/nvme1n1
I1025 23:10:14.116211       7 addhandler.go:106] checking if device: /dev/nvme1n1 can be uniquely identified
I1025 23:10:14.116218       7 uuid.go:78] device(/dev/nvme1n1) has a WWN, using WWN: nvme.1d0f-4157533232333735383142324144373744383343-416d617a6f6e20454332204e564d6520496e7374616e6365
2053746f72616765-00000001 and Serial: AWS22<serial_id>
I1025 23:10:14.116228       7 uuid.go:101] generated uuid: blockdevice-<uuid> for device: /dev/nvme1n1
I1025 23:10:14.116234       7 addhandler.go:141] uuid: blockdevice-<uuid>  has been generated for device: /dev/nvme1n1
I1025 23:10:14.116238       7 addhandler.go:47] device: /dev/nvme1n1 already exists in cache, the event was likely generated by a partition table re-read or a change in some of the dev
ices was detected
E1025 23:10:14.120697       7 blockdevicestore.go:143] Unable to get blockdevice object : blockdevices.openebs.io "blockdevice-e1f2aeeae9fb6815dddc93c1d810ca84" not found
I1025 23:10:14.120716       7 addhandler.go:147] device: /dev/nvme1n1, uuid: blockdevice-e1f2aeeae9fb6815dddc93c1d810ca84 not found in etcd
I1025 23:10:14.120721       7 addhandler.go:271] creating block device resource for device: /dev/nvme1n1 with uuid: blockdevice-e1f2aeeae9fb6815dddc93c1d810ca84
I1025 23:10:14.131932       7 blockdevicestore.go:45] eventcode=ndm.blockdevice.create.success msg=Created blockdevice object in etcd rname=blockdevice-e1f2aeeae9fb6815dddc93c1d810ca84

[avishnu]

@niladrih please take a look at this .

[github-actions]

Issues go stale after 90d of inactivity. Please comment or re-open the issue if you are still interested in getting this issue fixed.