Sandro

Oh yes :)) we had the same concern and opted out to install the operator for our application teams and went back to the normal install for them :) I...

> @Numblesix yes, we are considering the same here. For big companies having multi-tenant clusters in production it's a huge concern. So we are considering uninstalling the operator and get...

@balaramesh yes useChap was set to true in the backend-config :) Ill try to get a reproducer then ill open a case :) Now the issue solved it self by...

So i couldnt reproduce myself but the issue happend again strangly on the same node again. I checked the file and CHAP Creds are set correct. Trying to move and...

I also noted that when i restart the pod on another node i always get this msg in the events: `Multi-Attach error for volume "pvc-38c3d63c-472c-4f15-94e7-90a8cae49acf" Volume is already exclusively attached...

Today i also found this issue in the Logs: `MountVolume.MountDevice failed for volume "pvc-62d2061e-7a19-4ba0-99ad-a470d638499d" : rpc error: code = Internal desc = iSCSI login failed using CHAP`

Seems my issue was: https://netapp-trident.readthedocs.io/en/stable-v21.04/kubernetes/operations/tasks/worker.html#iscsi I had more then `MD5` in my `iscsid.conf` even tough my Backend is an onTAP System it still had issues. Maybe those "issues" should be...

sure :) , i applied the change now to 3 of 4 cluster and i will see if everything works better now Config before: ``` iscsid.startup = /bin/systemctl start iscsid.socket...

Maybe also interesting my Netapp is running `NetApp Release 9.6P1`

So usually those Errors `error decrypting iscsi username` always apeared while doing an OpenShift update. Today no Issue, so i really think that onTAP Users should also only rely on...