浏览代码

Attempt to fix containerized node start failure with Docker 1.10.

It appears that in some situations (can't reliably reproduce yet), node
will fail to start. This appears to be related to the node-dep service
and possibly it's environment file.

This file is also an EnvironmentFile for the node service, but it's only
created by the node-dep service, and it looks like it may try to read
it's environment before the node-dep service has fully started and
created the file.

Workaround with a an explicit service start.
Devan Goodwin 9 年之前
父节点
当前提交
a7b4676ee4
共有 1 个文件被更改,包括 4 次插入0 次删除
  1. 4 0
      roles/openshift_node/tasks/main.yml

+ 4 - 0
roles/openshift_node/tasks/main.yml

@@ -110,6 +110,10 @@
   changed_when: false
   when: openshift.common.is_containerized | bool
 
+- name: Start and enable node dep
+  service: name={{ openshift.common.service_type }}-node-dep enabled=yes state=started
+  when: openshift.common.is_containerized | bool
+
 - name: Start and enable node
   service: name={{ openshift.common.service_type }}-node enabled=yes state=started
   register: node_start_result