Verified this bug with openshift v3.7.27, still reproduced.

# journalctl -f  -u atomic-openshift-node.service 
<--snip-->
Jan 29 02:03:03 ip-172-18-2-97.ec2.internal systemd[1]: Starting atomic-openshift-node.service...
Jan 29 02:03:04 ip-172-18-2-97.ec2.internal atomic-openshift-node[60575]: Error response from daemon: No such container: atomic-openshift-node
Jan 29 02:03:08 ip-172-18-2-97.ec2.internal atomic-openshift-node[60585]: Error: invalid argument "3 --disable=proxy" for --loglevel=3 --disable=proxy: strconv.ParseInt: parsing "3 --disable=proxy": invalid syntax



# cat /etc/sysconfig/atomic-openshift-node
OPTIONS=--loglevel=3 --disable=proxy
CONFIG_FILE=/etc/origin/node/node-config.yaml
IMAGE_VERSION=v3.7.27


# docker images
REPOSITORY                                                  TAG                 IMAGE ID            CREATED             SIZE
registry.reg-aws.openshift.com:443/openshift3/node          v3.7.27             9afbe5c76fe2        29 hours ago        1.303 GB

In v3.7.29-1

Verified this bug with openshift-ansible-3.7.29-1.git.0.e1bfc35.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.7.29


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:0636