[YSQL] YB-Tablet advertising itself with `rpc_bind_addresses` even when `server_broadcast_addresses` is defined

[pasquale95]

Jira Link: DB-19238

Description

Hi,
I'm experiencing the following problem when trying to run a YugabyteDB cluster with TLS. Specifically, when I run a YugabyteDB Tablet with the following command:

bin/yb-tserver \
    --tserver_master_addrs=machine1.cloud.com:7100,machine2.cloud.com:7100,machine3.cloud.com:7100 \
    --server_broadcast_addresses=machine4.cloud.com:9100 \
    --rpc_bind_addresses=0.0.0.0:9100 \
    --webserver_port=9000 \
    --pgsql_proxy_bind_address=0.0.0.0:5433 \
    --pgsql_proxy_webserver_port=13001 \
    --redis_proxy_bind_address=0.0.0.0:6379 \
    --redis_proxy_webserver_port=11001 \
    --cql_proxy_bind_address=0.0.0.0:9042 \
    --cql_proxy_webserver_port=12001 \
    --minloglevel=0 \
    --stderrthreshold=0 \
    --yb_enable_read_committed_isolation=true \
    --fs_data_dirs=/var/data \
    --allow_insecure_connections=false \
    --use_node_to_node_encryption=true \
    --use_client_to_server_encryption=true \
    --dump_certificate_entries \
    --certs_dir=/var/tls

and then I try to run the following initialisation command:

ysqlsh -h machine4.cloud.com -p 5433 -U yugabyte -f /var/ybinit/01-yb-init.sql

I get the following error:

ysqlsh: FATAL:  Handshake failed: Network error (yb/rpc/secure_stream.cc:1109): Endpoint does not match, address: 0.0.0.0, hostname: 0.0.0.0

The only way to get around this problem for now is to set:

--rpc_bind_addresses=machine4.cloud.com:9100

But this prevents from binding the port to all the network interfaces. Per my understanding and according to the documentation, this shouldn't happen if I set server_broadcast_addresses. I don't get why ysqlsh receives 0.0.0.0 as endpoint.

Issue Type

kind/bug

Warning: Please confirm that this issue does not contain any sensitive information

• I confirm this issue does not contain any sensitive information.

[Adityakk9031]

.take