HA Consul leaves all Swarm nodes in Pending state #2320
I set up a 3 node consul cluster as follows.
Then I ran the
They are running on the private network so I created an internal loadbalancer.
Then I created 3 swarm nodes as follows:
To make sure it was accessible I ran
Then I created 3 swarm managers as follows
and I did the same to join the 3 nodes to the cluster.
Now when I
Tailing the logs of the manager I see that a new manager is elected every minute or so. Consul knows that the nodes exist because I can see them in the UI view.
I'm fairly sure this is a problem with HA consul because I have run single node consul before with swarm and everything works just fine.
I've googled about everything I can but I haven't been able to find a solution. Any help would be appreciated.
EDIT: I have tried the same thing with the official consul image by running this command :
The results are the same. Swarm still has all three nodes stuck in a pending state.
The text was updated successfully, but these errors were encountered:
I was able to bypass this issue for the most part by creating nodes with the following command:
Just by adding the
I can now run HA consul and HA swarm but I still think this is an issue and not an optimal solution.
Thanks @mixman! The ELB seems to have been the problem. Before I had a CNAME point to the ELB that I had made. I seem to have fixed it by changing it from a CNAME pointing to an ELB to an A record pointing to the private IP's of the consul nodes. Then when I was running the swarm managers/nodes I simply put
Closing this as it seems to be a consul issue and not a swarm issue.