From 1284b7c8398533db4a9ff58bc06ff627e17d316b Mon Sep 17 00:00:00 2001 From: Weiwei Date: Thu, 26 Dec 2024 10:10:34 +0800 Subject: [PATCH] docs: supply docs of installation error (#1192) Signed-off-by: zwwhdls --- docs/en/administration/troubleshooting-cases.md | 9 +++++++++ docs/zh_cn/administration/troubleshooting-cases.md | 9 +++++++++ 2 files changed, 18 insertions(+) diff --git a/docs/en/administration/troubleshooting-cases.md b/docs/en/administration/troubleshooting-cases.md index 7431b1fdaa..7b2decc97e 100644 --- a/docs/en/administration/troubleshooting-cases.md +++ b/docs/en/administration/troubleshooting-cases.md @@ -19,6 +19,15 @@ Above error message shows that the CSI Driver named `csi.juicefs.com` isn't foun If you used `mount pod` mode, follow these steps to troubleshoot: * Run `kubectl get csidrivers.storage.k8s.io` and check if `csi.juicefs.com` actually missing, if that is indeed the case, CSI Driver isn't installed at all, head to [Installation](../getting_started.md). +* Check if the rootdir of kubelet is the same as the one specified in the CSI Driver DaemonSet, if they are different, the CSI Driver won't be registered successfully. Please reconfigure it or reinstall JuiceFS CSI Node, For more details, see [Installation](../getting_started.md). + + ```shell + # Check kubelet rootdir + ps -ef | grep kubelet | grep root-dir + # check kubelet rootdir in CSI Node + kubectl -n kube-system get ds juicefs-csi-node -oyaml | grep csi.juicefs.com + ``` + * If `csi.juicefs.com` already exists in the above `csidrivers` list, that means CSI Driver is installed, the problem is with CSI Node, check its status: * Before troubleshooting, navigate to [check CSI Node](./troubleshooting.md#check-csi-node) to see a list of helpful commands; * A CSI Node Pod is expected on the node where the application Pod is running, if [scheduling strategy](../guide/resource-optimization.md#csi-node-node-selector) has been configured for the CSI Node DaemonSet, or the node itself is [tainted](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration), CSI Node may be missing on some worker nodes, causing the "driver not found" issue; diff --git a/docs/zh_cn/administration/troubleshooting-cases.md b/docs/zh_cn/administration/troubleshooting-cases.md index f25d3f3cb5..ab060461d7 100644 --- a/docs/zh_cn/administration/troubleshooting-cases.md +++ b/docs/zh_cn/administration/troubleshooting-cases.md @@ -19,6 +19,15 @@ kubernetes.io/csi: attacher.MountDevice failed to create newCsiDriverClient: dri 若使用的是 Mount Pod 模式，遵循以下步骤进行排查： * 运行 `kubectl get csidrivers.storage.k8s.io`，如果输出的中确没有 `csi.juicefs.com` 字样，说明 CSI 驱动并未安装，仔细回顾[「安装 JuiceFS CSI 驱动」](../getting_started.md)； +* 检查 kubelet 的根目录与 CSI Node 的配置是否一致，如果不一致，会导致 CSI Node 无法正常注册，请修复 CSI Node 的配置，或者重新安装，参考[「安装 JuiceFS CSI 驱动」](../getting_started.md)； + + ```shell + # kubelet 根目录 + ps -ef | grep kubelet | grep root-dir + # CSI Node 配置 + kubectl -n kube-system get ds juicefs-csi-node -oyaml | grep csi.juicefs.com + ``` + * 如果上方的 `csidrivers` 列表中存在 `csi.juicefs.com`，那么说明 CSI 驱动已经安装，问题出在 CSI Node，检查 CSI Node 是否正常运作： * 排查开始前，可以简单阅读[检查 CSI Node](./troubleshooting.md#check-csi-node)，代码示范里有一些快捷命令可供参考； * 关注应用 Pod 所在节点，检查节点是否正常运行着 CSI Node，如果为 CSI Node 这个 DaemonSet 组件配置了[调度策略](../guide/resource-optimization.md#csi-node-node-selector)，或者节点本身存在[「污点」](https://kubernetes.io/zh-cn/docs/concepts/scheduling-eviction/taint-and-toleration)，都有可能造成 CSI Node 容器缺失，造成该错误；