问题求助：openshift 3.11 离线安装 Control plane pods didn't come up

Windows的vmwaer上发布虚拟机离线安装openshift311部署步骤参考的是https://blog.csdn.net/Hlroliu/article/details/104821776基础配置，软件包安装，镜像下载均已部署好，通过了检查项，在安装部署时一直卡在以下界面TASK [openshift_control_plane : Wait for control plane p...

Hlroliu

1653人浏览 · 2020-04-09 16:29:07

Hlroliu · 2020-04-09 16:29:07 发布

Windows的vmwaer上发布虚拟机离线安装openshift311

部署步骤参考的是https://blog.csdn.net/Hlroliu/article/details/104821776
基础配置，软件包安装，镜像下载均已部署好，通过了检查项，在安装部署时一直卡在以下界面

TASK [openshift_control_plane : Wait for control plane pods to appear
FAILED - RETRYING: Wait for control plane pods to appear (60 retries left).
FAILED - RETRYING: Wait for control plane pods to appear (59 retries left).
FAILED - RETRYING: Wait for control plane pods to appear (58 retries left).
FAILED - RETRYING: Wait for control plane pods to appear (57 retries left).
FAILED - RETRYING: Wait for control plane pods to appear (56 retries left).
FAILED - RETRYING: Wait for control plane pods to appear (55 retries left).
FAILED - RETRYING: Wait for control plane pods to appear (54 retries left).
...........
failed: [openshift1] (item=etcd) => {"attempts": 60, "changed": false, "item": "etcd", "msg": {"cmd": "/usr/bin/oc get pod master-etcd-openshift1 -o json -n kube-system", "results": [{}], "returncode": 1, "stderr": "The connection to the server openshift1:8443 was refused - did you specify the right host or port?\n", "stdout": ""}}
..........
TASK [openshift_control_plane : Report control plane errors] *************************************************
fatal: [openshift1]: FAILED! => {"changed": false, "msg": "Control plane pods didn't come up"}

在这里插入图片描述
防火墙iptables配置文件中已经允许了8443端口

主要的参数配置如下：

在这里插入图片描述
ansible的版本

]# ansible --version
ansible 2.6.14
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.5 (default, Apr 11 2018, 07:36:10) [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)]

docker版本

]# docker version
Client:
 Version:         1.13.1
 API version:     1.26
 Package version: docker-1.13.1-109.gitcccb291.el7.centos.x86_64
 Go version:      go1.10.3
 Git commit:      cccb291/1.13.1
 Built:           Tue Mar  3 17:21:24 2020
 OS/Arch:         linux/amd64

Server:
 Version:         1.13.1
 API version:     1.26 (minimum version 1.12)
 Package version: docker-1.13.1-109.gitcccb291.el7.centos.x86_64
 Go version:      go1.10.3
 Git commit:      cccb291/1.13.1
 Built:           Tue Mar  3 17:21:24 2020
 OS/Arch:         linux/amd64
 Experimental:    false

docker仓库配置
[root@openshift1 ~]# cat /etc/containers/registries.conf

# This is a system-wide configuration file used to
# keep track of registries for various container backends.
# It adheres to TOML format and does not support recursive
# lists of registries.

# The default location for this configuration file is /etc/containers/registries.conf.

# The only valid categories are: 'registries.search', 'registries.insecure', 
# and 'registries.block'.

[registries.search]
registries = ['192.168.10.21:5000']

# If you need to access insecure registries, add the registry's fully-qualified name.
# An insecure registry is one that does not have a valid SSL certificate or only does HTTP.
[registries.insecure]
registries = ['192.168.10.21:5000']


# If you need to block pull access from a registry, uncomment the section below
# and add the registries fully-qualified name.
#
# Docker only
[registries.block]
registries = ['registry.access.redhat.com']

麻烦各位大神抽空看看，能否处理下这个问题。