I am installing Openshift 3.11 version cluster on my Centos 7.8 VMS. The configuration is that there are three Centos VMs (one master node + two worker nodes). I have configured my inventory file also and ‘prerequisites.yml’ playbook also ran successfully. But when I am running the playbook ‘deploy_cluster.yml’, then it is generating errors as follows —-
[WARNING]: Module invocation had junk after the JSON data: Error in atexit._run_exitfuncs: Traceback (most recent call last): File
"/usr/lib64/python2.7/atexit.py", line 24, in _run_exitfuncs func(*targs, **kargs) File
"/tmp/ansible_oc_obj_payload_A0Bg8i/ansible_oc_obj_payload.zip/ansible/modules/oc_obj.py", line 1257, in cleanup AttributeError:
'NoneType' object has no attribute 'path' Error in sys.exitfunc: Traceback (most recent call last): File
"/usr/lib64/python2.7/atexit.py", line 24, in _run_exitfuncs func(*targs, **kargs) File
"/tmp/ansible_oc_obj_payload_A0Bg8i/ansible_oc_obj_payload.zip/ansible/modules/oc_obj.py", line 1257, in cleanup AttributeError:
'NoneType' object has no attribute 'path'
At the end, the installer is failing.
TASK [openshift_control_plane : Report control plane errors] ******************************************************************************
fatal: [kubernetus]: FAILED! => {"changed": false, "msg": "Control plane pods didn't come up"}
NO MORE HOSTS LEFT ************************************************************************************************************************
PLAY RECAP ********************************************************************************************************************************
kubernetus : ok=293 changed=45 unreachable=0 failed=1 skipped=235 rescued=0 ignored=1
kubernetus1 : ok=103 changed=15 unreachable=0 failed=0 skipped=88 rescued=0 ignored=0
kubernetus2 : ok=103 changed=15 unreachable=0 failed=0 skipped=88 rescued=0 ignored=0
localhost : ok=11 changed=0 unreachable=0 failed=0 skipped=5 rescued=0 ignored=0
INSTALLER STATUS **************************************************************************************************************************
Initialization : Complete (0:08:28)
Health Check : Complete (0:02:42)
Node Bootstrap Preparation : Complete (1:02:37)
etcd Install : Complete (0:13:03)
Master Install : In Progress (1:43:59)
This phase can be restarted by running: playbooks/openshift-master/config.yml
Failure summary:
1. Hosts: kubernetus
Play: Configure masters
Task: Report control plane errors
Message: Control plane pods didn't come up
For this, I even checked ‘/var/spool/abrt’ directory but found the same error message —
‘NoneType’ object has no attribute ‘path’
I have also found out the following logs —-
Jun 23 15:57:49 kubernetus origin-node: I0623 15:57:49.898598 35114 container_manager_linux.go:428] [ContainerManager]: Discovered runtime cgroups name: /system.slice/docker.service
Jun 23 15:57:58 kubernetus python: ansible-oc_obj Invoked with files=None kind=pod force=False all_namespaces=None field_selector=None namespace=kube-system delete_after=False kubeconfig=/etc/origin/master/admin.kubeconfig content=None state=list debug=False selector=None name=master-api-kubernetus
Jun 23 15:58:01 kubernetus python: detected unhandled Python exception in '/root/.ansible/tmp/ansible-tmp-1592908072.81-35221-114985355081512/AnsiballZ_oc_obj.py'
Jun 23 15:58:07 kubernetus python: communication with ABRT daemon failed: timed out
Jun 23 15:58:08 kubernetus abrt-server: Email address of sender was not specified. Would you like to do so now? If not, 'user@localhost' is to be used [y/N]
Jun 23 15:58:08 kubernetus abrt-server: Email address of receiver was not specified. Would you like to do so now? If not, 'root@localhost' is to be used [y/N]
Jun 23 15:58:08 kubernetus abrt-server: Undefined variable outside of [[ ]] bracket
Jun 23 15:58:08 kubernetus abrt-server: Sending an email...
Jun 23 15:58:08 kubernetus abrt-server: Sending a notification email to: root@localhost
Jun 23 15:58:09 kubernetus abrt-server: Email was sent to: root@localhost
I am not able to figure out what is the issue ? Can anybody help me in this ?
2
Answers
Try to Move your environment to higher specifications.
Try to use at least 2vcpu and RAM 8GB for cluster machines (Master + Infra 1, Compute 1) !
resources might be an issue as mentioned, also make sure you are using a version of ansible that is compatible with the installer playbooks