kelseyhightower / consul-on-kubernetes

Running HashiCorp's Consul on Kubernetes
Apache License 2.0
601 stars 183 forks source link

No cluster leader #42

Open itsecforu opened 4 years ago

itsecforu commented 4 years ago

Hello. Did everything according to your instructions, but unfortunately nothing works

if i try to get list peers

consul operator raft -list-peers -token=e986a3da-f69d-4d82-b497-cbc0cb382596 Operator "raft" subcommand failed: Unexpected response code: 500 (No cluster leader)

List of pods seems ok:

kubectl get pods NAME READY STATUS RESTARTS AGE consul-1-587bf84975-xv8pb 1/1 Running 0 3d1h consul-2-9c7bcb99b-75dpw 1/1 Running 0 3d1h consul-3-5699d494b8-twd2s 1/1 Running 0 3d1h

If i write kubectl pport forward ( f.e consul-2) ,I see only one under which I indicated

# consul members Node Address Status Type Build Protocol DC Segment worker-2 10.233.33.42:8301 alive server 0.7.2 2 devsecops <all>

Logs say the same thing:

2019/12/09 13:45:52 [ERR] agent: failed to sync remote state: No cluster leader 2019/12/09 13:45:56 [ERR] agent: coordinate update error: No cluster leader 2019/12/09 13:46:23 [ERR] agent: failed to sync remote state: No cluster leader 2019/12/09 13:46:27 [ERR] agent: coordinate update error: No cluster leader 2019/12/09 13:46:54 [ERR] agent: coordinate update error: No cluster leader 2019/12/09 13:46:59 [ERR] agent: failed to sync remote state: No cluster leader 2019/12/09 13:47:20 [ERR] agent: coordinate update error: No cluster leader 2019/12/09 13:47:22 [ERR] agent: failed to sync remote state: No cluster leader 2019/12/09 13:47:46 [ERR] agent: failed to sync remote state: No cluster leader 2019/12/09 13:47:49 [ERR] agent: coordinate update error: No cluster leader 2019/12/09 13:48:13 [ERR] agent: coordinate update error: No cluster leader 2019/12/09 13:48:16 [ERR] agent: failed to sync remote state: No cluster leader

2

UI doesnt work too

3

I hope u will help me ! Thx

itsecforu commented 4 years ago

no ideas?