With either no dataLIF setting, or just a specific IP address, Trident will still create sessions to the HA Pair partner's iSCSI LIF as well. Multipathing needs to be enabled, or there will be issues ...With either no dataLIF setting, or just a specific IP address, Trident will still create sessions to the HA Pair partner's iSCSI LIF as well. Multipathing needs to be enabled, or there will be issues with handling of the PVC, since errors about the remaining disk devices can crop up. The option was mainly meant for NFS, since, when using multiple LIFs in the SVM, you may want to specify the IP that normally runs on the node with the aggregate of the PVC volume.
Applies to Trident for Openshift/Kubernetes Issue When running a tridentctl backend update command to apply changes to the definition, the following error occurs: USER@HOSTNAME:~/trident-installer$ tr...Applies to Trident for Openshift/Kubernetes Issue When running a tridentctl backend update command to apply changes to the definition, the following error occurs: USER@HOSTNAME:~/trident-installer$ tridentctl update backend ontapsan_<IP_ADDR> -f <NEW_BACKEND>.json -n trident Error: could not update backend ontapsan_<IP_ADDR>: Unable to find key (400 Bad Request) command terminated with exit code 1
