Is it mandatory to have SELinux in Enforcing mode while scaling up a Red Hat Enterprise Linux 7 host to RHOCP4.2 cluster?

Issue

• Is it mandatory to have SELinux in Enforcing mode while scaling up a Red Hat Enterprise Linux 7 host to Red Hat OpenShift Container Platform 4.2 cluster?
• While executing the scaleup.yml playbook to add a Red Hat Enterprise Linux 7 compute node to Red Hat OpenShift Container Platform 4.2, it fails with following error.

TASK [openshift_node : Setting sebool container_manage_cgroup] *******************************************************************************************************************************
task path: /usr/share/ansible/openshift-ansible/roles/openshift_node/tasks/config.yml:31
Saturday 28 December 2019  04:11:47 -0700 (0:00:00.384)       0:10:11.527 ***** 
Using module file /usr/lib/python2.7/site-packages/ansible/modules/system/seboolean.py
Pipelining is enabled.
<rhel7-compute-node.example.com> ESTABLISH SSH CONNECTION FOR USER: root
<rhel7-compute-node.example.com> SSH: EXEC ssh -o ControlMaster=auto -o ControlPersist=600s -o StrictHostKeyChecking=no -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o 'User="root"' -o ConnectTimeout=30 -o ControlPath=/root/.ansible/cp/%h-%r rhel7-compute-node.example.com '/bin/sh -c '"'"'/usr/bin/python && sleep 0'"'"''
<rhel7-compute-node.example.com> (1, '\n{"msg": "SELinux is disabled on this host.", "failed": true, "invocation": {"module_args": {"state": true, "persistent": true, "name": "container_manage_cgroup", "ignore_selinux_state": false}}}\n', '')
<rhel7-compute-node.example.com> Failed to connect to the host via ssh: 
fatal: [rhel7-compute-node.example.com]: FAILED! => {
    "changed": false, 
    "invocation": {
        "module_args": {
            "ignore_selinux_state": false, 
            "name": "container_manage_cgroup", 
            "persistent": true, 
            "state": true
        }
    }, 
    "msg": "SELinux is disabled on this host."
}