-
Notifications
You must be signed in to change notification settings - Fork 547
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
安装新集群的时候报错:[ETCDConfigureModule] Health check on exist etcd #2316
Labels
bug
Something isn't working
Comments
想了想,打算自己加etcd的配置文件。看了一下kubekey生成etcd配置文件的template。
这里有些变量名称,还得斟酌一下,怕填错。 有没有大佬一起填一下这个变量 |
把etcdname和相对应的ip改掉就行 |
多谢, 我用最新的pre release的3.1.2安装就没问题了. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is version of KubeKey has the issue?
v3.0.13
What is your os environment?
centos7
KubeKey config file
A clear and concise description of what happend.
[ETCDConfigureModule] Health check on exist etcd
Relevant log output
我看了一下源码,到了ETCDConfigureModule。
应该就是到了上图红框里这部分。
因为是新建集群,那么我们就认为是走的handleNewCluster
handleNewCluster的源码如下:
existETCDHealthCheck 按道理应该是这个handleNewCluster里放到restart后才执行的才对吧。新建集群,在ETCDConfigureModule之前执行了InstallETCDBinaryModule,那么代表etcd是安装了,但是InstallETCDBinaryModule并没有生成 etcd.env。所以接下来在handleNewCluster即ConfigureModule中的执行顺序应该是
其实 existETCDHealthCheck,在新建集群是不是都没必要了。
然后我看了一下etcd.service
配置文件在 /etc/etcd.env
查了一下这个,文件不存在。
配置文件不存在,就代表InstallETCDBinaryModule安装etcd之后,是无法启动etcd的,导致后面ETCDConfigureModule中existETCDHealthCheck是会报错的。因为etcd没启动。
看一下当前节点etcd的状态
那么问题出来了,这个问题出现的原因是 在没用生成 etcd.env的前提下,检查了etcd的健康度。
是否可以出一个紧急的版本修复一下这问题?
The text was updated successfully, but these errors were encountered: