server health error="context deadline exceeded" error="rpc error getting client"

Warnings and Errors always... when setting up new Consul cluster, using terraform. Nothing special, following Hashicorp learning pattern. Does not matter if one of 3 vm's the warning always appears.

Size = "Standard_B2s"
publisher = "Canonical"
offer = "0001-com-ubuntu-server-focal"
sku = "20_04-lts-gen2"
version = "latest"

config.json
```
{
"node_name": "consul-server-0",
"advertise_addr": "4.196.98.18",
"bind_addr": "0.0.0.0",
"client_addr": "0.0.0.0",
"data_dir": "/opt/consul/data",
"log_file": "/opt/consul/logs/consul.log",
"log_level": "DEBUG",
"server": true,
"bootstrap_expect": 1,
"retry_join": [
"10.0.1.4"
],
"service": [
{
"name": "consul"
}
],
"ui_config": [
{
"enabled": true
}
],
"connect": {
"enabled": true
},
"leave_on_terminate": true,
"rejoin_after_leave": true,
"verify_server_hostname": false
}
```

consul.service

```
[Unit]
Description=Consul
Documentation=https://www.consul.io/docs/
Wants=network-online.target
After=network-online.target

[Service]
ExecStart=/opt/consul/consul agent -config-file /opt/consul/config.json -config-dir=/opt/consul
ExecReload=/bin/kill -HUP $MAINPID
KillMode=process
Restart=on-failure
RestartSec=5s
StartLimitBurst=1
StartLimitInterval=0
TimeoutStartSec=30s
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target
```

Start by reproducing the warning with the supplied config.json and consul.service on the Ubuntu Azure VMs, then inspect the Consul logs and cluster connectivity around the reported deadline and RPC errors. Compare the setup with the referenced HashiCorp learning pattern; done means identifying the cause and documenting a verified configuration or deployment fix.

Written by the indexing model from the issue text.