Details
-
Bug
-
Resolution: Unresolved
-
Major
-
7.6.0
-
Couchbase Enterprise Edition build 7.6.0-2176
-
Untriaged
-
Linux x86_64
-
0
-
Unknown
Description
Steps to reproduce
1. Created 1 ec2 instances and 1 node(from couchbase network) clusters
| Cluster 1 | Cluster 2 |
|---|---|
| 1 node cluster Internal couchbase network - 172.23.104.66 |
1 node cluster DNS - ec2-35-173-129-143.compute-1.amazonaws.com Private IP - 172.31.15.218 Public IP - 35.173.129.143 |
2. Did not set the alternate address of the nodes in the cluster
3. Started xdcr from cluster 1 to cluster 2 using public IP - Connection pre-check succeeds and xdcr fails - XDCR failing is expected as the public IP is not configured as the alternate address
4. Started xdcr from cluster 1 to cluster 2 using DNS - Connection pre-check succeeds and xdcr fails - XDCR failing is expected since couchbase is using private ip
5. Set alternate address and attempted XDCR - Connection pre-check succeeds and xdcr succeeds - Works as expected
Note :
ec2-35-173-129-143.compute-1.amazonaws.com:8091 and 35.173.129.143:8091 is accessible
Expected behavior
Connection pre-check should not succeed when public IP was not configured as the alternate address
