SAS Viya Deployment Consul Error

[spennato]

I am trying to perform a SAS Viya 3.4 deployment on a single machine and am encountering the following error when trying to deploy from the ansible playbook.

"Unable to determine the address of the Raft leader for the data center in which the Consul agent is running"

I have attached the consul logs for reference.

Any help would be greatly appreciated.

[spennato]

I am trying to perform a SAS Viya 3.4 deployment on a single machine and am encountering the following error when trying to deploy from the ansible playbook.

TASK [consul-x64_redhat_linux_6-yum : Execute confirm consul can be accessed] **************************************************************************************************************************
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.148512", "end": "2019-11-15 18:20:16.837061", "msg": "non-zero return code", "rc": 1, "start": "2019-11-15 18:20:16.688549", "stderr": "Get https://localhost:8501/v1/status/leader: x509: certificate signed by unknown authority\nERROR: Unable to determine the address of the Raft leader for the data center in which the Consul agent is running.", "stderr_lines": ["Get https://localhost:8501/v1/status/leader: x509: certificate signed by unknown authority", "ERROR: Unable to determine the address of the Raft leader for the data center in which the Consul agent is running."], "stdout": "", "stdout_lines": []}

I have attached the consul logs for reference.

Any help would be greatly appreciated.

[alexal]

@spennato ,

Show me the output from "ifconfig" command, please.

[spennato]

ens5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9001
inet 172.30.3.218 netmask 255.255.255.0 broadcast 172.30.3.255
inet6 fe80::ce5:27ff:fea5:7329 prefixlen 64 scopeid 0x20<link>
ether 0e:e5:27:a5:73:29 txqueuelen 1000 (Ethernet)
RX packets 33044503 bytes 48277512575 (44.9 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2956146 bytes 200276283 (190.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 43488 bytes 9650673 (9.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 43488 bytes 9650673 (9.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[dharrell96]

Hi, I think finding the solution to this issue will be specific to your deployment and will require some debugging.  Would you mind opening a track with tech support?

[spennato]

No problem, track has been opened

[Kurt_Bremser]

In order to better keep track of the discussion, I merged the identical questions.