karmada controller and scheduler status always CrashLoopBackOff

[ayewwww]

What happened: 1 leaderelection.go:255] failed to acquire lease karmada-system/karmada-controller-manager

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Karmada version: 1.9
• k8s 1.26
• kubectl-karmada or karmadactl version (the result of kubectl-karmada version or karmadactl version):
• Others:

[ayewwww]

[ayewwww]

[zhzhuang-zju]

@ayewwww Looks like it crashed shortly after installing, maybe some resources are not initialized properly, can you describe how you installed Karmada?

[chaosi-zju]

hi, please use kubectl logs -f etcd-0 -n karmada-system to check the etcd log at that time, there should be some problem with etcd at that time, for example, the request processing exceeded 5 seconds.

[ayewwww]

@ayewwww看起来它在安装后不久就崩溃了，也许一些资源没有正确初始化，你能描述一下你是如何安装 Karmada 的吗？ offline installation， command：kubectl karmada init --crds /$HOME/crds.tar.gz

[ayewwww]

hi, please use kubectl logs -f etcd-0 -n karmada-system to check the etcd log at that time, there should be some problem with etcd at that time, for example, the request processing exceeded 5 seconds.

etcd appears to have no errors

[ayewwww]

@ayewwww看起来它在安装后不久就崩溃了，也许一些资源没有正确初始化，你能描述一下你是如何安装 Karmada 的吗？ offline installation， command：kubectl karmada init --crds /$HOME/crds.tar.gz

[chaosi-zju]

Can you export full logs of controller、scheduler、etcd to files, and provide it to us?