#read-write-many with iSCSI ontap-san

1 messages · Page 1 of 1 (latest)

cosmic meteor
#

my environment
OS RHEL 9.4
Rancher RKE2 v1.30.6
Trident version 24.10.0
using iSCSI
3 x CP/etcd nodes
3 x worker nodes
things appear to be working except when I have to reboot a worker node
the pod moves to next available worker node but volume stays stuck with the old node and things get messy
anyone else have had this issue?
maybe if I have read-write-many this will not be an issue? but is that supported with iSCSI backend with ontap-san

cosmic meteor
#

when I try to create a PVC with read-write-many this is the error:

#

Warning ProvisioningFailed 9s (x2 over 17s) csi.trident.netapp.io_trident-controller- failed to provision volume with StorageClass "ontap-san": rpc error: code = InvalidArgument desc = no available storage for access modes: [ReadWriteMany]

gloomy nimbus
#

Which filesystem are you using on your iSCSI LUN?

#

because for read-write-many on SAN you need a cluster filesystem otherwise you will lose data

covert delta