Wan federation doesn't work with FQDN node name #12614
Labels
needs-discussion
Topic needs discussion with the larger Consul maintainers before committing to for a release
theme/federation-usability
Anything related to Federation
type/bug
Feature does not function as expected
Related Topic on Hashicorp Discuss
Connection failure in federation between VMs (primary) and kubernetes
Overview of the Issue
I wanted to federate a consul cluster running in k3s (named:
dc2
) to a consul cluster running on VMs (named:dc1
).The nodes of the VM cluster have a node name in FQDN format (eg
ceph-1.hirsingue.infra.mydomain.fr
) which causes the following error in the logs (dc2
consul server) and prevents the federation from continuing:Reproduction Steps
This should be similar for any cluster type, but in my case :
eg:
ceph-1.hirsingue.infra.mydomain.fr
eg:
consul tls cert create -server -dc dc1 -node ceph-1.hirsingue.infra.mydomain.fr
Consul info for dc1 and dc2 server
DC2 Server info
DC1 Server info
Operating system and Environment details
VMs OS:
Thanks for your help!
The text was updated successfully, but these errors were encountered: