unable to read config file: open /etc/origin/node/resolv.conf: no such file or directory

Solution In Progress - Updated -

Issue

Aug 22 15:38:47 master.examplecom atomic-openshift-node[30443]: F0822 15:38:47.529156   30443 start_node.go:140] could not start DNS, unable to read config file: open /etc/origin/node/resolv.conf: no such file or directory
Aug 22 15:38:47 master.example.com systemd[1]: atomic-openshift-node.service: main process exited, code=exited, status=255/n/a
Aug 22 15:38:47 master.example.com systemd[1]: Failed to start OpenShift Node.
Aug 22 15:38:47 master.example.com systemd[1]: Unit atomic-openshift-node.service entered failed state.
Aug 22 15:38:47 master.example.com systemd[1]: atomic-openshift-node.service failed.
Aug 22 15:38:52 master.example.com systemd[1]: atomic-openshift-node.service holdoff time over, scheduling restart.
Aug 22 15:38:52 master.example.com systemd[1]: Starting OpenShift Node...
  • Unable to install OpenShift

Environment

  • Red Hat OpenShift Container Platform
    • 3.6+

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