From d29ecbd64c8ec1bfc2a266899c915d07988260f8 Mon Sep 17 00:00:00 2001 From: Hongbin Lu Date: Sun, 2 Sep 2018 22:16:22 +0000 Subject: [PATCH] Run etcd on controller node only In before, etcd container is launched in compute node if kuryr is enabled. This logic breaks the all-in-one setup in which the etcd cluster is configured with two members (controller and compute) but it actually has one member only. However, even if kuryr is enabled, running etcd in compute node is not the common practice and kuryr has changed its devstack plugin to run etcd on controller only [1]. [1] https://review.openstack.org/#/c/514815/ Closes-Bug: #1790415 Change-Id: I701d495675178c3ed8ec1f00b31d09f198b38a6f --- ansible/roles/etcd/defaults/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ansible/roles/etcd/defaults/main.yml b/ansible/roles/etcd/defaults/main.yml index dec8eb24cf..5f2f6a1667 100644 --- a/ansible/roles/etcd/defaults/main.yml +++ b/ansible/roles/etcd/defaults/main.yml @@ -37,4 +37,4 @@ etcd_image_full: "{{ etcd_image }}:{{ etcd_tag }}" etcd_dimensions: "{{ default_container_dimensions }}" # List of hosts running etcd. -etcd_hosts: "{{ groups['control'] + (groups['compute'] if enable_kuryr | bool else []) }}" +etcd_hosts: "{{ groups['control'] }}"