openshift4.5 系统重启后，node处于NotReady状态
[root@bastion ~]# oc get nodes
NAME STATUS ROLES AGE VERSION
master.okd.mengshicheng.io NotReady master,worker 44h v1.18.3
worker1.okd.mengshicheng.io NotReady worker 43h v1.18.3
重新执行：openshift-install wait-for install-complete --log-level=debug --dir=/root/okdinstall
提示：
DEBUG OpenShift Installer 4.5.0-0.okd-2020-10-15-235428
DEBUG Built from commit 63200c80c431b8dbaa06c0cc13282d819bd7e5f8
DEBUG Fetching Install Config...
DEBUG Loading Install Config...
DEBUG Loading SSH Key...
DEBUG Loading Base Domain...
DEBUG Loading Platform...
DEBUG Loading Cluster Name...
DEBUG Loading Base Domain...
DEBUG Loading Platform...
DEBUG Loading Pull Secret...
DEBUG Loading Platform...
DEBUG Using Install Config loaded from state file
DEBUG Reusing previously-fetched Install Config
INFO Waiting up to 30m0s for the cluster at https://api.okd.mengshicheng.io:6443 to initialize...
DEBUG Cluster is initialized
INFO Waiting up to 10m0s for the openshift-console route to be created...
DEBUG Still waiting for the console route: the server is currently unable to handle the request (get routes.route.openshift.io)
DEBUG Still waiting for the console route: the server is currently unable to handle the request (get routes.route.openshift.io)
DEBUG Still waiting for the console route: the server is currently unable to handle the request (get routes.route.openshift.io)
DEBUG Still waiting for the console route: the server is currently unable to handle the request (get routes.route.openshift.io)
DEBUG Still waiting for the console route: the server is currently unable to handle the request (get routes.route.openshift.io)
DEBUG Still waiting for the console route: the server is currently unable to handle the request (get routes.route.openshift.io)
DEBUG Still waiting for the console route: the server is currently unable to handle the request (get routes.route.openshift.io)
DEBUG Still waiting for the console route: the server is currently unable to handle the request (get routes.route.openshift.io)
看起来您的 OpenShift 节点在重启之后处于 NotReady 状态。这可能是由于节点上的某些组件在重启之后无法正常启动导致的。
要解决此问题，您需要对节点进行诊断并根据问题的确切原因进行修复。有几种方法可以帮助您实现这一点：
检查节点的日志以了解可能的问题原因。要检查节点的日志，请使用命令：oc logs node/
检查节点的状态，看看哪些组件处于不正常状态。要检查节点的状态，请使用命令：oc describe node/
重新启动节点上的组件，以便尝试解决问题。要重新启动节点上的组件，请使用命令：oc rollout restart node/