本人在安装KubeSphere2.1.1的multi-node集群1个master+2个node时,一直靠在以下界面:
TASK [common : debug] **********************************************************
ok: [localhost] => {
“msg”: [
“1. check the storage configuration and storage server”,
“2. make sure the DNS address in /etc/resolv.conf is available.”,
“3. execute ‘helm del –purge ks-minio && kubectl delete job -n kubesphere-system ks-minio-make-bucket-job’”,
“4. Restart the installer pod in kubesphere-system namespace”
]
}
TASK [common : fail] ***********************************************************
fatal: [localhost]: FAILED! => {“changed”: false, “msg”: “It is suggested to refer to the above methods for troubleshooting problems .”}
PLAY RECAP *********************************************************************
localhost : ok=33 changed=27 unreachable=0 failed=1 skipped=75 rescued=0 ignored=7
经过各种检查发现minio的pod状态间断性出现CrashLoopBackOff,时而是running,查看详情,信息如下:
Events:
Type Reason Age From Message
Warning FailedScheduling 42m (x3 over 42m) default-scheduler pod has unbound immediate PersistentVolumeClaims (repeated 2 times)
Normal Scheduled 42m default-scheduler Successfully assigned kubesphere-system/minio-845b7bd867-z5×77 to k8sphere03
Normal Killing 37m (x3 over 41m) kubelet, k8sphere03 Container minio failed liveness probe, will be restarted
Normal Created 36m (x4 over 42m) kubelet, k8sphere03 Created container minio
Normal Started 36m (x4 over 42m) kubelet, k8sphere03 Started container minio
Normal Pulled 17m (x10 over 42m) kubelet, k8sphere03 Container image “minio/minio:RELEASE.2019-08-07T01-59-21Z” already present on machine
Warning Unhealthy 7m15s (x35 over 42m) kubelet, k8sphere03 Liveness probe failed: HTTP probe failed with statuscode: 503
Warning BackOff 2m19s (x85 over 28m) kubelet, k8sphere03 Back-off restarting failed container
[root@k8sphere01 kubesphere]#
查看日志
kubectl describe pods -n kubesphere-system minio-make-bucket-job-4xcss
Events:
Type Reason Age From Message
Normal Scheduled 48m default-scheduler Successfully assigned kubesphere-system/minio-make-bucket-job-4xcss to k8sphere02
Normal Pulled 9m35s (x6 over 48m) kubelet, k8sphere02 Container image “minio/mc:RELEASE.2019-08-07T23-14-43Z” already present on machine
Normal Created 9m35s (x6 over 48m) kubelet, k8sphere02 Created container minio-mc
Normal Started 9m34s (x6 over 48m) kubelet, k8sphere02 Started container minio-mc
Warning BackOff 2m2s (x16 over 33m) kubelet, k8sphere02 Back-off restarting failed container
[root@k8sphere01 kubesphere]#
稍等后,又自动好了!!!
折腾好久后,终于看到一个帖子提出了将openpitrix的安装标识改为false,然后卸载之前的安装版本,重新安装就成功了。
但现在openpitrix是没有启动的,请教以下几个问题:
1、为啥开启openpitrix,就无法安装下去,该怎么去核查无法安装的具体原因?
2、接下来应该怎么来安装openpitrix?
谢谢