RolandMa1986 有报错，具体如下：
TASK [check-result : ks-devops | Getting ks-sonarqube NodeIp] ******************
changed: [localhost]
TASK [check-result : KubeSphere | Waiting for ks-console] **********************
changed: [localhost]
TASK [check-result : KubeSphere | Waiting for ks-apiserver] ********************
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (30 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (29 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (28 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (27 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (26 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (25 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (24 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (23 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (22 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (21 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (20 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (19 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (18 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (17 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (16 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (15 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (14 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (13 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (12 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (11 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (10 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (9 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (8 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (7 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (6 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (5 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (4 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (3 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (2 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (1 retries left).
fatal: [localhost]: FAILED! => {“attempts”: 30, “changed”: true, “cmd”: “/usr/local/bin/kubectl get pod -n kubesphere-system -o wide | grep ks-apiserver | awk ‘{print $3}’”, “delta”: “0:00:00.095965”, “end”: “2021-11-04 14:57:05.055270”, “rc”: 0, “start”: “2021-11-04 14:57:04.959305”, “stderr”: "", “stderr_lines”: [], “stdout”: “CrashLoopBackOff”, “stdout_lines”: [“CrashLoopBackOff”]}
PLAY RECAP *********************************************************************
localhost : ok=22 changed=14 unreachable=0 failed=1 skipped=14 rescued=0 ignored=0
同时也查看了下ks-api的日志，如下：
W1104 15:39:45.770051 1 client_config.go:615] Neither –kubeconfig nor –master was specified. Using the inClusterConfig. This might not work.
W1104 15:39:45.771340 1 client_config.go:615] Neither –kubeconfig nor –master was specified. Using the inClusterConfig. This might not work.
I1104 15:39:45.967197 1 interface.go:60] start helm repo informer
I1104 15:39:46.008793 1 apiserver.go:356] Start cache objects
I1104 15:39:47.338198 1 apiserver.go:562] Finished caching objects
I1104 15:39:47.338225 1 apiserver.go:278] Start listening on :9090
W1104 15:58:28.087087 1 handler.go:86] websocket: the client is not using the websocket protocol: ‘upgrade’ token not found in ‘Connection’ header
E1104 15:58:29.648600 1 v2.go:105] websocket: close 1001 (going away)
W1104 15:58:29.850082 1 handler.go:86] websocket: the client is not using the websocket protocol: ‘upgrade’ token not found in ‘Connection’ header
W1104 15:58:37.740894 1 terminal.go:137] 1Process exited
E1104 16:00:13.343547 1 v2.go:105] websocket: close 1006 (abnormal closure): unexpected EOF
W1104 16:00:21.356346 1 terminal.go:137] 1Process exited
E1104 16:01:15.223045 1 v2.go:105] websocket: close 1006 (abnormal closure): unexpected EOF
W1104 16:01:23.228005 1 terminal.go:137] 1Process exited
E1104 16:02:18.728752 1 v2.go:105] websocket: close 1006 (abnormal closure): unexpected EOF
W1104 16:02:26.735521 1 terminal.go:137] 1Process exited
E1104 16:03:26.037568 1 v2.go:105] websocket: close 1006 (abnormal closure): unexpected EOF
W1104 16:03:34.042614 1 terminal.go:137] 1Process exited
E1104 16:04:35.981090 1 v2.go:105] websocket: close 1006 (abnormal closure): unexpected EOF
W1104 16:04:43.986783 1 terminal.go:137] 1Process exited
E1104 16:15:59.864094 1 v2.go:105] websocket: close 1006 (abnormal closure): unexpected EOF
W1104 16:16:07.875975 1 terminal.go:137] 1Process exited
W1104 16:16:49.131081 1 handler.go:86] websocket: the client is not using the websocket protocol: ‘upgrade’ token not found in ‘Connection’ header
W1104 16:18:03.960810 1 terminal.go:137] 2command terminated with exit code 137
E1104 16:18:03.960940 1 v2.go:105] read tcp 172.30.1.102:9090->172.30.6.168:46958: use of closed network connection
E1104 16:19:06.475819 1 v2.go:105] websocket: close 1006 (abnormal closure): unexpected EOF
W1104 16:19:14.479704 1 terminal.go:137] 1Process exited
E1104 16:20:09.077557 1 v2.go:105] websocket: close 1006 (abnormal closure): unexpected EOF
W1104 16:20:12.892087 1 handler.go:86] websocket: the client is not using the websocket protocol: ‘upgrade’ token not found in ‘Connection’ header
W1104 16:20:17.082360 1 terminal.go:137] 1Process exited
E1104 16:22:54.994946 1 v2.go:105] websocket: close 1006 (abnormal closure): unexpected EOF
W1104 16:23:02.999543 1 terminal.go:137] 1Process exited
E1104 16:26:40.508035 1 v2.go:105] websocket: close 1001 (going away)
W1104 16:26:48.520828 1 terminal.go:137] 1Process exited
