Saurabh Wani

RHEL Worker node : ``` [root@worker3 ~]# sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: permissive Mode from config file: permissive...

Uploaded logs in D.948

similar type of issue is also when we there is no network policy applied and Host Network is enabled .GUI of primary fs is not reachable and we apply configmap...

Improvement for future : There should be prerequisite check at operator before restarting driver pods when confimap is changed or applied. It will stop all CSI pod restarts

Observation: pods also restart when secret is created when previous name

closing as issue is fixed in https://github.com/IBM/ibm-spectrum-scale-csi/pull/1180

Another scenario is seen as follows: 1. Apply cm having wrong key , it will generate cso event 2. Apply cm having wrong value , it will generate cso event...