After deleting log file it is not getting recreated

[saurabhwani5]

Describe the bug

A clear and concise description of what the bug is.

How to Reproduce?

Please list the steps to help development teams reproduce the behavior

1. Install CSI 2.9.0 with following Images.

[root@saurabh-csi-master ~]#
[root@saurabh-csi-master ~]# oc get pods
NAME                                                  READY   STATUS    RESTARTS   AGE
ibm-spectrum-scale-csi-5s96m                          3/3     Running   0          45m
ibm-spectrum-scale-csi-attacher-5885c459cb-2srvj      1/1     Running   0          45m
ibm-spectrum-scale-csi-attacher-5885c459cb-rcq59      1/1     Running   0          45m
ibm-spectrum-scale-csi-c96j6                          3/3     Running   0          45m
ibm-spectrum-scale-csi-operator-56b47dfc95-78r6n      1/1     Running   0          70m
ibm-spectrum-scale-csi-provisioner-6b69d67cff-2jxc7   1/1     Running   0          45m
ibm-spectrum-scale-csi-resizer-6cc9f547d-qqzsx        1/1     Running   0          45m
ibm-spectrum-scale-csi-snapshotter-6cf9b7d69b-vnqb8   1/1     Running   0          45m
[root@saurabh-csi-master ~]#
[root@saurabh-csi-master ~]# oc get cso
NAME                     VERSION   SUCCESS
ibm-spectrum-scale-csi   2.9.0     True
[root@saurabh-csi-master ~]# oc describe pod | grep quay
    Image:         quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:b6108b3a146c53d74ff4195e0805390b1901bf3541327a753691c9035d0b07ef
    Image ID:      quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:5aca20a03b2d15c1184f22c1506c4f3948d9dcdef3fd518cb04eebcc8558b4da
  Normal  Pulled     45m   kubelet            Container image "quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:b6108b3a146c53d74ff4195e0805390b1901bf3541327a753691c9035d0b07ef" already present on machine
    Image:         quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:b6108b3a146c53d74ff4195e0805390b1901bf3541327a753691c9035d0b07ef
    Image ID:      quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:5aca20a03b2d15c1184f22c1506c4f3948d9dcdef3fd518cb04eebcc8558b4da
  Normal  Pulled     45m   kubelet            Container image "quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:b6108b3a146c53d74ff4195e0805390b1901bf3541327a753691c9035d0b07ef" already present on machine
    Image:         quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-operator@sha256:f8daa3676003498ac3d7027b070568ddef2f0181396ef1772b1389d431a51874
    Image ID:      quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-operator@sha256:1da1d4a01255ccf8d2476883e3d427490d03e9627a3a5b4a8245b5e7d4718988
      CSI_DRIVER_IMAGE:      quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:b6108b3a146c53d74ff4195e0805390b1901bf3541327a753691c9035d0b07ef
[root@saurabh-csi-master ~]#

2. Delete the log file from the worker node of the following path. [root@saurabh-csi-worker-2 ~]# rm -rf /var/log/scalecsilogs/ibm-spectrum-scale-csi.logs
3. Try to create PVC or any resources to generate logs.
4. Check if the log file is getting recreated or not.

Expected behavior

A log file should be created if it is missing when driver is writing the logs.

Observation :

Log file is getting recreated whenever driver pods restarts , in the case when driver pods is not getting restarted and log file is missing then log file won't be created