Closed rabin-io closed 3 months ago
Yes, multipathing is required. You'll run into issues otherwise if any failover/maintenance occurs on the storage system. Therefore recent versions of Trident enforce multipathing.
You can set this via MachineConfig. The only setting Trident needs in multipath.conf is find_multipaths no
. An example MachineConfig is provided here (please refer to the one for multipathing!): https://docs.netapp.com/us-en/netapp-solutions/containers/rh-os-n_overview_trident.html#iscsi
Thank you for the (quick) clarification.
Describe the bug $subect
Environment I'm testing Trident on top of OpenShift, and started to test iSCSI (on-san) support as a backend for Virtual Machines (OpenShift Virtualization).
To Reproduce Create a VM and an add a disk using the iSCSI storage class.
Expected behavior Should just work. But I get an error message
Additional context Enabling multipathd on the host, does resolve this issue, but I'm wondering if enabling
multipathd
is required for iSCSI, or it is just a config on the TridentBackEnd config?