Failing to start atomic-openshift-node service on RHEL atomic hosts

Solution In Progress - Updated -

Issue

Failing to start atomic-openshift-node service on RHEL atomic hosts with the error messages below:

Dec 02 15:17:06 app01.example.com systemd[1]: Started atomic-openshift-node-dep.service.
Dec 02 15:17:06 app01.example.com systemd[1]: Starting atomic-openshift-node-dep.service...
Dec 02 15:17:06 app01.example.com systemd[1]: Starting atomic-openshift-node.service...
Dec 02 15:17:06 app01.example.com dockerd-current[6716]: time="2018-12-02T15:17:06.419480926-05:00" level=error msg="Handler for DELETE /v1.26/containers/atomic-openshift-node?force=1 returned error: No such container: atomic-openshift-node"
Dec 02 15:17:06 app01.example.com dockerd-current[6716]: time="2018-12-02T15:17:06.420606339-05:00" level=error msg="Handler for DELETE /v1.26/containers/atomic-openshift-node returned error: No such container: atomic-openshift-node"
Dec 02 15:17:06 app01.example.com atomic-openshift-node[15584]: Error response from daemon: No such container: atomic-openshift-node Dec 02 15:17:06 app01.example.com dockerd-current[6716]: time="2018-12-02T15:17:06.455027500-05:00" level=error msg="Handler for POST /v1.26/containers/create?name=atomic-openshift-node returned error: lstat /var/lib/docker/overla
y2/f0a3d3729509a9228434570f29d1862fb101a0ccf5e5c358da12c0dd23847fff: no such file or directory"
Dec 02 15:17:06 app01.example.com dockerd-current[6716]: time="2018-12-02T15:17:06.455454718-05:00" level=error msg="Handler for POST /v1.26/containers/create returned error: lstat /var/lib/docker/overlay2/f0a3d3729509a9228434570f
29d1862fb101a0ccf5e5c358da12c0dd23847fff: no such file or directory"
Dec 02 15:17:06 app01.example.com atomic-openshift-node[15606]: /usr/bin/docker-current: Error response from daemon: lstat /var/lib/docker/overlay2/f0a3d3729509a9228434570f29d1862fb101a0ccf5e5c358da12c0dd23847fff: no such file or directory.
Dec 02 15:17:06 app01.example.com atomic-openshift-node[15606]: See '/usr/bin/docker-current run --help'.
Dec 02 15:17:06 app01.example.com systemd[1]: atomic-openshift-node.service: main process exited, code=exited, status=127/n/a Dec 02 15:17:16 app01.example.com dockerd-current[6716]: time="2018-12-02T15:17:16.455697217-05:00" level=error msg="Handler for POST /v1.26/containers/atomic-openshift-node/stop returned error: No such container: atomic-openshift-node"
Dec 02 15:17:16 app01.example.com dockerd-current[6716]: time="2018-12-02T15:17:16.456144242-05:00" level=error msg="Handler for POST /v1.26/containers/atomic-openshift-node/stop returned error: No such container: atomic-openshift-node"
Dec 02 15:17:16 app01.example.com atomic-openshift-node[15621]: Error response from daemon: No such container: atomic-openshift-node Dec 02 15:17:16 app01.example.com systemd[1]: atomic-openshift-node.service: control process exited, code=exited status=1 Dec 02 15:17:16 app01.example.com systemd[1]: Failed to start atomic-openshift-node.service.
Dec 02 15:17:16 app01.example.com systemd[1]: Unit atomic-openshift-node.service entered failed state.
Dec 02 15:17:16 app01.example.com systemd[1]: atomic-openshift-node.service failed.

Environment

OCP 3.x
RHEL Atomic with docker

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In