Skip to main content
NetApp Knowledge Base

Trident does not update iSCSI connections when iSCSI LIFs are added to an SVM

  1. Last updated
  2. Save as PDF
Views:
100
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Applies to

  • Astra Trident for Openshift and Kubernetes
  • ontap-san-* driver

Issue

After specifying new iSCSI LIFs in the SVM that is being used by a Trident backend, the already connected ontap-san(-economy) PVCs do not update their iSCSI login paths automatically.
This is usually used to attempt a live change from an old set of ONTAP nodes to a new set (HA Pair), not just when expanding the storage clustre by adding new nodes.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.