While doing single machine deployment I am facing the error below 2019-11-05 19:31:03,991 p=22387 u=root | fatal: [deployTarget]: FAILED! => {"changed": true, "cmd": ["bash", "-c", "source /opt/sas/viya/config/consul.conf && /opt/sas/viya/home/bin/sas-bootstrap-config status leader"], "delta": "0:00:00.203617", "end": "2019-11-05 19:31:03.940516", "msg": "non-zero return code", "rc": 1, "start": "2019-11-05 19:31:03.736899", "stderr": "level=error command=\"status leader\" successful=false msg=\"Unable to status leader\" err=\"Get https://localhost:8501/v1/status/leader: dial tcp [::1]:8501: connect: connection refused\"\nERROR: Unable to determine the address of the Raft leader for the data center in which the Consul agent is running.", "stderr_lines": ["level=error command=\"status leader\" successful=false msg=\"Unable to status leader\" err=\"Get https://localhost:8501/v1/status/leader: dial tcp [::1]:8501: connect: connection refused\"", "ERROR: Unable to determine the address of the Raft leader for the data center in which the Consul agent is running."], "stdout": "", "stdout_lines": []} 2019-11-05 19:31:03,994 p=22387 u=root | NO MORE HOSTS LEFT ************************************************************* 2019-11-05 19:31:03,996 p=22387 u=root | PLAY RECAP ********************************************************************* 2019-11-05 19:31:03,997 p=22387 u=root | deployTarget : ok=237 changed=83 unreachable=0 failed=1 2019-11-05 19:31:03,997 p=22387 u=root | localhost : ok=14 changed=1 unreachable=0 failed=0 2019-11-05 21:15:08,107 passlib.registry registered 'md5_crypt' handler: <class 'passlib.handlers.md5_crypt.md5_crypt'> 2019-11-05 21:15:08,911 p=10886 u=root | deployTarget | SUCCESS | rc=0 >> In Consul log I can see "==> bind_addr cannot be empty". I confirmed and I have added "consul_bind_adapter = eth0 in inventory.ini file.
... View more
