rockylinux9安装到etcd的时候报错，系统版本9.0、9.3
myrex781 opened this issue · 0 comments
What happened? 发生了什么问题？
TASK [etcd : 开启etcd服务] ******************************************************************************************************************************
fatal: [10.5.0.6]: FAILED! => {"changed": true, "cmd": "systemctl daemon-reload && systemctl restart etcd", "delta": "0:01:30.188002", "end": "2024-07-16 16:40:59.436447", "msg": "non-zero return code", "rc": 1, "start": "2024-07-16 16:39:29.248445", "stderr": "Job for etcd.service failed because a timeout was exceeded.\nSee "systemctl status etcd.service" and "journalctl -xeu etcd.service" for details.", "stderr_lines": ["Job for etcd.service failed because a timeout was exceeded.", "See "systemctl status etcd.service" and "journalctl -xeu etcd.service" for details."], "stdout": "", "stdout_lines": []}
...ignoring
fatal: [10.5.0.5]: FAILED! => {"changed": true, "cmd": "systemctl daemon-reload && systemctl restart etcd", "delta": "0:01:30.188523", "end": "2024-07-16 16:40:59.438008", "msg": "non-zero return code", "rc": 1, "start": "2024-07-16 16:39:29.249485", "stderr": "Job for etcd.service failed because a timeout was exceeded.\nSee "systemctl status etcd.service" and "journalctl -xeu etcd.service" for details.", "stderr_lines": ["Job for etcd.service failed because a timeout was exceeded.", "See "systemctl status etcd.service" and "journalctl -xeu etcd.service" for details."], "stdout": "", "stdout_lines": []}
...ignoring
fatal: [10.5.0.4]: FAILED! => {"changed": true, "cmd": "systemctl daemon-reload && systemctl restart etcd", "delta": "0:01:30.334919", "end": "2024-07-16 16:40:59.572377", "msg": "non-zero return code", "rc": 1, "start": "2024-07-16 16:39:29.237458", "stderr": "Job for etcd.service failed because a timeout was exceeded.\nSee "systemctl status etcd.service" and "journalctl -xeu etcd.service" for details.", "stderr_lines": ["Job for etcd.service failed because a timeout was exceeded.", "See "systemctl status etcd.service" and "journalctl -xeu etcd.service" for details."], "stdout": "", "stdout_lines": []}
...ignoring
FAILED - RETRYING: [10.5.0.6]: 以轮询的方式等待服务同步完成 (8 retries left).
FAILED - RETRYING: [10.5.0.4]: 以轮询的方式等待服务同步完成 (8 retries left).
FAILED - RETRYING: [10.5.0.5]: 以轮询的方式等待服务同步完成 (8 retries left).
FAILED - RETRYING: [10.5.0.6]: 以轮询的方式等待服务同步完成 (7 retries left).
FAILED - RETRYING: [10.5.0.4]: 以轮询的方式等待服务同步完成 (7 retries left).
FAILED - RETRYING: [10.5.0.5]: 以轮询的方式等待服务同步完成 (7 retries left).
FAILED - RETRYING: [10.5.0.6]: 以轮询的方式等待服务同步完成 (6 retries left).
FAILED - RETRYING: [10.5.0.4]: 以轮询的方式等待服务同步完成 (6 retries left).
FAILED - RETRYING: [10.5.0.5]: 以轮询的方式等待服务同步完成 (6 retries left).
FAILED - RETRYING: [10.5.0.6]: 以轮询的方式等待服务同步完成 (5 retries left).
FAILED - RETRYING: [10.5.0.4]: 以轮询的方式等待服务同步完成 (5 retries left).
FAILED - RETRYING: [10.5.0.5]: 以轮询的方式等待服务同步完成 (5 retries left).
FAILED - RETRYING: [10.5.0.6]: 以轮询的方式等待服务同步完成 (4 retries left).
FAILED - RETRYING: [10.5.0.4]: 以轮询的方式等待服务同步完成 (4 retries left).
FAILED - RETRYING: [10.5.0.5]: 以轮询的方式等待服务同步完成 (4 retries left).
FAILED - RETRYING: [10.5.0.6]: 以轮询的方式等待服务同步完成 (3 retries left).
FAILED - RETRYING: [10.5.0.4]: 以轮询的方式等待服务同步完成 (3 retries left).
FAILED - RETRYING: [10.5.0.5]: 以轮询的方式等待服务同步完成 (3 retries left).
FAILED - RETRYING: [10.5.0.6]: 以轮询的方式等待服务同步完成 (2 retries left).
FAILED - RETRYING: [10.5.0.4]: 以轮询的方式等待服务同步完成 (2 retries left).
FAILED - RETRYING: [10.5.0.5]: 以轮询的方式等待服务同步完成 (2 retries left).
FAILED - RETRYING: [10.5.0.6]: 以轮询的方式等待服务同步完成 (1 retries left).
FAILED - RETRYING: [10.5.0.4]: 以轮询的方式等待服务同步完成 (1 retries left).
FAILED - RETRYING: [10.5.0.5]: 以轮询的方式等待服务同步完成 (1 retries left).
TASK [etcd : 以轮询的方式等待服务同步完成] **************************************************************************************************************
fatal: [10.5.0.6]: FAILED! => {"attempts": 8, "changed": true, "cmd": "systemctl is-active etcd.service", "delta": "0:00:00.007616", "end": "2024-07-16 16:42:05.043772", "msg": "non-zero return code", "rc": 3, "start": "2024-07-16 16:42:05.036156", "stderr": "", "stderr_lines": [], "stdout": "activating", "stdout_lines": ["activating"]}
fatal: [10.5.0.4]: FAILED! => {"attempts": 8, "changed": true, "cmd": "systemctl is-active etcd.service", "delta": "0:00:00.008946", "end": "2024-07-16 16:42:05.166524", "msg": "non-zero return code", "rc": 3, "start": "2024-07-16 16:42:05.157578", "stderr": "", "stderr_lines": [], "stdout": "activating", "stdout_lines": ["activating"]}
fatal: [10.5.0.5]: FAILED! => {"attempts": 8, "changed": true, "cmd": "systemctl is-active etcd.service", "delta": "0:00:00.008970", "end": "2024-07-16 16:42:05.266242", "msg": "non-zero return code", "rc": 3, "start": "2024-07-16 16:42:05.257272", "stderr": "", "stderr_lines": [], "stdout": "activating", "stdout_lines": ["activating"]}
What did you expect to happen? 期望的结果是什么？
功能正常
How can we reproduce it (as minimally and precisely as possible)? 尽可能最小化、精确地描述如何复现问题
系统版本rockylinux9
kubeasz版本3.6.4
Anything else we need to know? 其他需要说明的情况
No response
Kubernetes version k8s 版本
Kubeasz version
OS version 操作系统版本
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output hereRocky Linux release 9.0 (Blue Onyx)
Linux k8s-master-01 5.14.0-70.13.1.el9_0.x86_64 #1 SMP PREEMPT Wed May 25 21:01:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux