I ve got some iscsi PVCs that were | NetApp | Page 1

copper vault Oct 7, 2022, 9:54 PM

#

If you are using a recent version of Trident then bouncing the pod with the volume attachment should fix that issue.

#

The iSCSI dataLIFs used in the volume attachment are determined when the volume publish call is made to the Trident controller

bright lintel Oct 7, 2022, 10:03 PM

#

Currently running 21.01.1. PVC originally created by whatever was current in June of 2020 (if that matters).

copper vault Oct 7, 2022, 10:29 PM

#

okay, I'm not sure about the behavior of that Trident version. It is going to be outside of limited support in 01/23 so you might consider upgrading Trident. https://mysupport.netapp.com/site/info/trident-support

#

If a dataLIF is specified for that volume in the backend config used to provision that volume then you may be stuck with a single path connection until you upgrade Trident.

#

Did you try bouncing the pod to see if it started using multiple dataLIFs?

#I ve got some iscsi PVCs that were