Etcd container failed to start in all-in-one setup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In a all-in-one setup with etcd enabled, the etcd container failed to start. Below is the logs:
+ sudo -E kolla_set_configs
INFO:__
INFO:__
INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
INFO:__
++ cat /run_command
+ CMD=etcd
+ ARGS=
+ [[ ! -n '' ]]
+ . kolla_extend_start
++ [[ ! -d /var/log/kolla/etcd ]]
+++ stat -c %a /var/log/kolla/etcd
++ [[ 755 != \7\5\5 ]]
+++ stat -c %U /var/lib/etcd/
++ [[ etcd != \e\t\c\d ]]
+ echo 'Running command: '\''etcd'\'''
Running command: 'etcd'
+ exec etcd
2018-09-02 20:04:44.944380 I | pkg/flags: recognized and used environment variable ETCD_ADVERTISE_
2018-09-02 20:04:44.944468 I | pkg/flags: recognized and used environment variable ETCD_DATA_
2018-09-02 20:04:44.944493 I | pkg/flags: recognized and used environment variable ETCD_INITIAL_
2018-09-02 20:04:44.944515 I | pkg/flags: recognized and used environment variable ETCD_INITIAL_
2018-09-02 20:04:44.944532 I | pkg/flags: recognized and used environment variable ETCD_INITIAL_
2018-09-02 20:04:44.944548 I | pkg/flags: recognized and used environment variable ETCD_INITIAL_
2018-09-02 20:04:44.944565 I | pkg/flags: recognized and used environment variable ETCD_LISTEN_
2018-09-02 20:04:44.944583 I | pkg/flags: recognized and used environment variable ETCD_LISTEN_
2018-09-02 20:04:44.944607 I | pkg/flags: recognized and used environment variable ETCD_NAME=primary
2018-09-02 20:04:44.944651 W | pkg/flags: unrecognized environment variable ETCD_OUT_
2018-09-02 20:04:44.944697 I | etcdmain: etcd Version: 3.2.17
2018-09-02 20:04:44.944722 I | etcdmain: Git SHA: Not provided (use ./build instead of go build)
2018-09-02 20:04:44.944743 I | etcdmain: Go Version: go1.10
2018-09-02 20:04:44.944760 I | etcdmain: Go OS/Arch: linux/amd64
2018-09-02 20:04:44.944773 I | etcdmain: setting maximum number of CPUs to 8, total number of available CPUs is 8
2018-09-02 20:04:44.946547 N | etcdmain: the server is already initialized as member before, starting as etcd member...
2018-09-02 20:04:44.946837 I | embed: listening for peers on http://
2018-09-02 20:04:44.946918 I | embed: listening for client requests on 158.69.94.91:2379
2018-09-02 20:04:44.959634 I | etcdmain: --initial-cluster must include primary=http://
Reviewed: https:/ /review. openstack. org/599265 /git.openstack. org/cgit/ openstack/ kolla-ansible/ commit/ ?id=d29ecbd64c8 ec1bfc2a266899c 915d07988260f8
Committed: https:/
Submitter: Zuul
Branch: master
commit d29ecbd64c8ec1b fc2a266899c915d 07988260f8
Author: Hongbin Lu <email address hidden>
Date: Sun Sep 2 22:16:22 2018 +0000
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 3ed8ec1f00b31d0 9f198b38a6f
Change-Id: I701d495675178c