When I execute the command kubectl migrate simple k8s-node2 I get status StartError
I'm sure nfs is properly configured and has r/w permissions
I think the migration was successful, but the restore is not normal
I need your help badly and Merry Christmas to you too! !
root@k8s-master:~# kubectl get nodes -o wide --show-labels
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME LABELS
k8s-master Ready master 33h v1.19.0-beta.0.1010+a94a66e8033cf4-dirty 11.0.1.136 <none> Ubuntu 20.04 LTS 5.4.0-26-generic containerd://Unknown beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=k8s-master,kubernetes.io/os=linux,node-role.kubernetes.io/master=
k8s-node1 Ready <none> 33h v1.19.0-beta.0.1010+a94a66e8033cf4-dirty 11.0.1.137 <none> Ubuntu 20.04 LTS 5.4.0-26-generic containerd://Unknown beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=k8s-node1,kubernetes.io/os=linux
k8s-node2 Ready <none> 33h v1.19.0-beta.0.1010+a94a66e8033cf4-dirty 11.0.1.138 <none> Ubuntu 20.04 LTS 5.15.0-56-generic containerd://Unknown beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=k8s-node2,kubernetes.io/os=linux
root@k8s-node1:~# criu -V
Version: 3.14
root@k8s-node1:~# criu check
Looks good.
root@k8s-node1:~# criu check --all
Warn (criu/cr-check.c:1230): clone3() with set_tid not supported
Error (criu/cr-check.c:1272): Time namespaces are not supported
Looks good but some kernel features are missing
which, depending on your process tree, may cause
dump or restore failure.
root@k8s-node1:~#
root@k8s-node2:~# criu -V
Version: 3.14
root@k8s-node2:~# criu check
Looks good.
root@k8s-node2:~# criu check --all
Looks good.
root@k8s-node1:~# containerd --version
WARN[2022-12-29T10:07:56.161416754+08:00] This customized containerd is only for CI test, DO NOT use it for distribution.
containerd github.com/containerd/containerd e5ffc7a4-TEST
root@k8s-node2:~# containerd --version
WARN[2022-12-29T10:07:42.305625776+08:00] This customized containerd is only for CI test, DO NOT use it for distribution.
containerd github.com/containerd/containerd e5ffc7a4-TEST
Problem Summary and Conjectures
I think there is a problem with the connection between criu and containerd, because there is a problem with the resore process。
Hi @vutuong :
Problem Description
When I execute the command
kubectl migrate simple k8s-node2
I get statusStartError
I'm sure nfs is properly configured and has r/w permissions I think the migration was successful, but the restore is not normal I need your help badly and Merry Christmas to you too! !When I check the nfs path is like this
Below is my execution process
root@k8s-node2:~# journalctl -xe -u kubelet -f
When I run the command
crictl ps -a
on the migrated node, I found that many pods have been created, but the status isExited
make run
go run ./api-server/cmd/main.go
what did i do?
I created a pod with 1.yaml, as follows
and then run command
host environment
Problem Summary and Conjectures
I think there is a problem with the connection between criu and containerd, because there is a problem with the resore process。
I really need your help, thank you! !
Thanks, PaperDragon