search

hashicorp / terraform-google-consul

A Terraform Module for how to run Consul on Google Cloud using Terraform and Packer
Apache License 2.0
94 stars 90 forks source link

Error: 'wrong datacenter' when start consul #19

Closed darkslategrey closed 6 years ago

darkslategrey commented 6 years ago

Context:

- terraform-google-consul: 0.0.3
- consul version : 1.1.0

error : 

    2018/06/11 23:43:33 [ERR] agent: failed to sync remote state: No cluster leader
    2018/06/11 23:43:40 [ERR] agent: Coordinate update error: No cluster leader
    2018/06/11 23:44:02 [ERR] memberlist: Failed push/pull merge: Member 'consul-server-1' part of wrong datacenter 'europe-west1-b' from=172.27.3.3:54738
    2018/06/11 23:44:03 [ERR] agent: failed to sync remote state: No cluster leader
    2018/06/11 23:44:08 [ERR] agent: Coordinate update error: No cluster leader
    2018/06/11 23:44:30 [ERR] agent: failed to sync remote state: No cluster leader

Looks like the datacenter format ('europe-west1-b') is not correct

josh-padnick commented 6 years ago

Thanks for this report. I believe the issue is that we previously tested with single-zone Instance Groups, whereas I'm guessing you're using multi-zonal Instance Groups. Nevertheless, your change in #20 will work for either, so I'll merge that now.