OpenShift 4.10→4.11→4.12.2升级Worker节点Degraded故障求助
OpenShift 4.x Worker节点升级停滞(Degraded状态)解决步骤
问题背景
集群从4.10.x→4.11.x→4.12.2升级时,worker0节点因磁盘实际osImageURL与期望的rendered-worker配置不符被标记为Degraded,手动执行/run/bin/machine-config-daemon pivot失败,出现"找不到repo目录"或"镜像校验和长度无效"报错。
解决操作步骤
1. 确认节点镜像配置信息
- 登录worker0节点,查看MCD日志确认期望镜像SHA:
oc adm node-logs worker0 -u machine-config-daemon - 查看当前节点的实际osImageURL配置:
cat /etc/machine-config-daemon/currentconfig
2. 清理MCD缓存与残留文件
- 删除pivot操作残留目录:
rm -rf /var/lib/machine-config-daemon/pivot - 移除旧的不匹配镜像:
podman rmi quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:73b311468554ffe8bdd0dd51df7dafd7a791a16c3147374cc7b28f0d3d7fcc17 - 重启MCD服务:
systemctl restart machine-config-daemon
3. 手动指定期望镜像执行Pivot
- 直接指定期望镜像SHA执行pivot命令:
/run/bin/machine-config-daemon pivot --to-image quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:f454144d2c32aa6fd99b8c68082f59554751282865dce6a866916d3c75fb02ee - 若仍报校验错误,先手动拉取期望镜像:
再重新执行上述pivot命令。podman pull quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:f454144d2c32aa6fd99b8c68082f59554751282865dce6a866916d3c75fb02ee
4. 验证节点恢复状态
- 检查节点状态:
oc get nodes worker0 - 确认节点Degraded状态消除:
oc describe node worker0 | grep -A5 Conditions - 实时监控MCD日志,确认无报错:
oc adm node-logs worker0 -u machine-config-daemon -f
内容的提问来源于stack exchange,提问作者Steven Schader
相关产品推荐
相关产品推荐

