Skip to main content
NetApp Stage KB

Trident crashes from version 21.07 with Cloud ONTAP

Last Updated:

Applies to

  • Trident for Kubernetes/Openshift 21.07.0 up to 22.01.0
  • Cloud ONTAP (CVO)  9


When attempting to provision a Trident volume after upgrading to 21.07, 21.10 or 22.01, with a Backend on Cloud ONTAP, the following errors are seen at the end of the "previous" log of the trident-controller:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1a7e867]
The trident controller pod restarts within 5 minutes (triggered by the operator), not providing the PVC.

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.
Case Citation