Skip to main content
NetApp Knowledge Base

Trident-controller keeps restarting due to termination of trident-main container

  1. Last updated
    Dec 17, 2024
  2. Save as PDF
Views:
61
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:
12/17/2024, 12:47:37 AM

Applies to

  • Astra Trident
  • Security-Enhanced Linux (SELinux) is not enabled

Issue

  • Trident-controller keeps restarting after run into CrashLoopBackOff state
  • No related error can be found in the trident-controller and/or trident-controller-previous log, but it has shut down

time="<TIMESTAMP>" level=info msg="Shutting down."

  • trident-controller-sidecar-csi-attacher and/or trident-controller-previous-sidecar-csi-attacher log indicates Lost connection to CSI driver

E1211 06:40:27.149543       1 connection.go:208] "Lost connection" address="unix:///var/lib/csi/sockets/pluginproxy/csi.sock"
E1211 06:40:27.149760       1 connection.go:116] "Lost connection to CSI driver, exiting"

  • Command kubectl describe pod trident-controller-<UUID> -n trident indicates csi-attacher is terminated after trident-main terminated with Exit Code 0

Containers:
  trident-main:
  ..
    Last State:     Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Wed, 11 Dec 2024 06:34:23 +0000
      Finished:     Wed, 11 Dec 2024 06:40:22 +0000
    Ready:          True
    Restart Count:  1
    Liveness:       exec [tridentctl -s 127.0.0.1:8000 version] delay=120s timeout=90s period=120s #success=1 #failure=2   ..
  csi-attacher:
  ..
    Last State:     Terminated
      Reason:       Error
      Message:      Lost connection to CSI driver, exiting
      Exit Code:    1
      Started:      Wed, 11 Dec 2024 06:34:26 +0000
      Finished:     Wed, 11 Dec 2024 06:40:27 +0000

 

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.