https://github.com/openshift/ose/pull/1033
The PR is not merged yet, so move it back to "MODIFIED".
In v3.6.173.0.103-1
Verified this bug with openshift-ansible-3.6.173.0.103-1.git.0.dcf417c.el7.noarch, and PASS. Setting openshift_node_env_vars={"OPTIONS": "--loglevel=3 --disable=proxy"} in inventory host file, trigger a docker containerized install. The setting is written into /etc/sysconfig/atomic-openshift-node. # cat /etc/sysconfig/atomic-openshift-node OPTIONS=--loglevel=3 --disable=proxy CONFIG_FILE=/etc/origin/node/node-config.yaml IMAGE_VERSION=v3.6.173.0.103 node service is running well. BTW, once set the above option to node config file, pod would fail to be deployed. # oc get po NAME READY STATUS RESTARTS AGE router-1-deploy 0/1 Error 0 29m # oc logs router-1-deploy error: couldn't get deployment router-1: Get https://172.31.0.1:443/api/v1/namespaces/default/replicationcontrollers/router-1: dial tcp 172.31.0.1:443: getsockopt: no route to host
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:1106