跳转到主内容

由于容器映像损坏,Trident 节点 Pod 无法启动 trident orchestrator:不存在此文件或目录

Views:
29
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

适用于

  • Trident
  • Kubernetes 和 Red Hat OpenShift 

问题

Trident 节点 pod 无法在特定的 Kubernetes worker 节点上启动,而所有其他节点上的 Trident pod 都正常运行。 

Pod 进入 CrashLoopBackOff 状态,但从未变为 Ready(就绪)。问题被隔离到单个节点。 

在 pod 事件或容器运行时日志中 观察到 以下错误:

Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "/trident_orchestrator": stat /trident_orchestrator: no such file or directory: unknown

其他相关日志行:

main.go:176 "Error connecting to CSI driver" err="context deadline exceeded"
connection.go:253 "Still connecting" address="unix:///plugin/csi.sock"

其他观察结果: 

  • Trident 控制器 pod 正在运行且运行正常 

  • Trident 后端处于联机状态 

  • PVC 配置适用于其他节点 

  • 仅一个(或一小部分)worker 节点受影响 

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.