Consul 1.8 - Error during WAN federation

Hi, I connected two Datacenters with WAN Gateways. Services are connecting correctly across the Datacenters. I followed this procedure: https://www.consul.io/docs/connect/wan-federation-via-mesh-gateways

However I am seeing the following messages in the log.
Any idea what is causing these errors ?

2020-06-29T15:29:21.131Z [ERROR] agent.server.memberlist.wan: memberlist: Failed to send ping: node name does not encode a datacenter: consul-c2s-as-1d.platform.comcast.net.openstacklocal.as
2020-06-29T15:29:21.635Z [ERROR] agent.server.memberlist.wan: memberlist: Push/Pull with consul-c2s-as-1d.platform.comcast.net.openstacklocal.as failed: node name does not encode a datacenter: consul-c2s-as-1d.platform.comcast.net.openstacklocal.as

Here is the output of ‘consul members’ from both datacenters:

======================= HA =========================================
[root@consul-c1s-ho-1d consul_poc]# consul members -wan
Node Address Status Type Build Protocol DC Segment
consul-c1s-ho-1d.platform.company.net.openstacklocal.ho 6.18.17.143:8302 alive server 1.8.0 2 ho
consul-c2s-as-1d.platform.company.net.openstacklocal.as 6.17.1.85:8302 alive server 1.8.0 2 as

[root@consul-c1s-ho-1d consul_poc]# consul members
Node Address Status Type Build Protocol DC Segment
consul-c1s-ho-1d.platform.company.net.openstacklocal 6.18.17.143:8301 alive server 1.8.0 2 ho
consul-c1s-ho-2d.platform.company.net.openstacklocal 6.18.16.170:8301 alive server 1.8.0 2 ho
consul-c1c-ho-3d.platform.company.net.openstacklocal 6.18.17.77:8301 alive client 1.8.0 2 ho
consul-c1c-ho-4d.platform.company.net.openstacklocal 6.18.18.30:8301 alive client 1.8.0 2 ho

======================= AS =========================================

[root@consul-c2s-as-2d consul_poc]# consul members -wan
Node Address Status Type Build Protocol DC Segment
consul-c1s-ho-2d.platform.company.net.openstacklocal.ho 6.18.16.170:8302 alive server 1.8.0 2 ho
consul-c2s-as-2d.platform.company.net.openstacklocal.as 6.17.1.175:8302 alive server 1.8.0 2 as

[root@consul-c2s-as-2d consul_poc]# consul members
Node Address Status Type Build Protocol DC Segment
consul-c2s-as-1d.platform.company.net.openstacklocal 6.17.1.85:8301 alive server 1.8.0 2 as
consul-c2s-as-2d.platform.company.net.openstacklocal 6.17.1.175:8301 alive server 1.8.0 2 as
consul-c2c-as-3d.platform.company.net.openstacklocal 6.17.2.11:8301 alive client 1.8.0 2 as
consul-c2c-as-4d.platform.company.net.openstacklocal 6.17.2.139:8301 alive client 1.8.0 2 as

Hi @pfridm01,

I am facing the same error too.

Did you find any reason as to why its occurring ?

I suspect it is because it looks like either your node names or datacenter names contain the “.” (dot) character.

Node names and datacenter names should not contain the “.” (dot) character. For backwards compatibility with the historical lack of validation on node names we do not enforce this constraint. Many parts of consul will work just fine with dots in either of those places but it will definitely be an issue if you do service discovery through DNS, use Connect, or use Mesh Gateways as you have discovered.

Hi @rboyer,

The node name can contain dot (.) because it will be FQDN (in many cases).

Should this occurrence of error be changed to info or warning.

I see that presence of those errors do not affect the service discovery or consul connect or Mesh gateway operations in any way so far.

Everything works like a charm.