kubelet报错：Orphaned pod “$Pod“ found, but volume paths are still present on disk

1.场景：

容器一直处在 ContainerCreating状态

$ kubectl get pod -n liantiao | grep pushserver
pushserver-69cc66c679-tx2pg                 1/1     Running             0          98d
pushserver-76675b6d94-kqh25                 0/1     ContainerCreating   0          56m

2.查看log describe 并没有发现有效信息

$ kubectl describe pod  pushserver-76675b6d94-kqh25 -n liantiao
Normal  Scheduled  57m   default-scheduler  Successfully assigned liantiao/pushserver-76675b6d94-kqh25 to cn-beijing.10.252.0.120$ kubectl logs pushserver-76675b6d94-nq4bg -n liantiao
Error from server (BadRequest): container "pushserver" in pod "pushserver-76675b6d94-nq4bg" is waiting to start: ContainerCreating

3.显示无法创建，使用 -o wide去目标主机上查看

发现登陆特别慢，我大概猜测应该是节点的问题，无法调度到这个容器上去，

我就删除了这个pod（重启），希望他能调度到别的节点上；但是还是调度到这个节点上了（一直ContainerCreating）

4.k8s组件里面，kubelet是负责启动pod的

查看kubelet 的日志

登陆目标主机

# journalctl -l -u kubelet   #kubelet是被system管理的
Orphaned pod "0009ae9e-d542-11ea-852a-00163e125f5d" found, but volume paths are still present on disk : There were a to
Orphaned pod "0009ae9e-d542-11ea-852a-00163e125f5d" found, but volume paths are still present on disk

有大量报错

参考：https://cloud.tencent.com/developer/article/1385911

一直在刷以下的报错,从错误信息可以推测到，这台计算节点存在一个孤儿Pod,并且该Pod挂载了数据卷(volume)，阻碍了Kubelet对孤儿Pod正常的回收清理。

节点有问题 https://cloud.tencent.com/developer/article/1385911，按照这里的方法删掉了 /var/lib/kubelet/pods/ 下的目录，并重启了systemctl进程

systemctl daemon-reexec:不重新启动的情况下重新启动systemd
执行这个命令是因为我的kubelet是被 systemd管理的

kubelet报错：Orphaned pod “$Pod“ found, but volume paths are still present on disk相关推荐

Orphaned pod found - but volume paths are still present on disk的处理
1. 现象一个问题发现集群内节点非正常移除,被调度为not ready 2. 问题排查查看kubelet日志 # journal -u kubelet -f Jan 21 16:45:44 loc ...
k8s关于Orphaned pod ＜pod_id＞ found，volume paths are still present on disk 的解决方法
问题描述因k8s节点异常关机导致启动后业务Pod重新部署,关机之前的Pod状态已被删除,今天在查看日志时发现在异常关机之前的集群节点Pod是非正常移除的,一直刷报错信息:如下: 问题排查查看系统日 ...
k8s的kubelet报错PLEG is not healthy: pleg was last seen active 3m41.603110188s ago
kubelet报错日志原因一 k8s集群中存在大量状态为Terminating的Pod 解决 NAMESPACE=devops-test rancher kubectl get pod -n ${N ...
【k8s错误解决系列】kubelet报错too many open files
[k8s错误解决系列]kubelet报错too many open files.md release author: ningan123 release time: 2022-08-12 报错日志 # ...
解决kubelet报错：kubelet.go:2183] node “k8s-20-52“ not found
解决kubelet报错:kubelet.go:2183] node "k8s-20-52" not found 由于公司机房服务器重启,k8s其中一个node节点的状态一直为Not ...
node节点kubelet报错 node \“xxxxx“ not found
11月 05 10:58:35 localhost.localdomain kubelet[974]: E1105 10:58:35.108952 974 kubelet.go:2412] " ...
解决argo workflow报错：MountVolume.SetUp failed for volume “docker-sock“ : hostPath type check failed
提交workflow时报错: MountVolume.SetUp failed for volume "docker-sock" : hostPath type check fai ...
ubuntu编译qemu报错：‘ERROR: DTC (libfdt) version = 1.4.0 not present.’
在ubuntu14.04中用源码方式编译安装qemu时,执行/configure步骤提示错误: ./configure ERROR: DTC (libfdt) version >= 1.4.0 ...
K8S离线安装kubeadm报错：conntrack is needed by kubelet
K8S离线安装kubeadm报错:conntrack is needed by kubelet 报错信息: rpm -ivh kubeadm-1.18.20-0.x86_64.rpm kubectl- ...

kubelet报错：Orphaned pod “$Pod“ found, but volume paths are still present on disk

kubelet报错：Orphaned pod “$Pod“ found, but volume paths are still present on disk相关推荐

最新文章

热门文章