Skip to content

Commit 408e3ea

Browse files
authored
no such host 550000 error asz hci
1 parent 257bf41 commit 408e3ea

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

articles/azure-arc/resource-bridge/troubleshoot-resource-bridge.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -166,16 +166,6 @@ When trying to set the configuration for Arc resource bridge, you might receive
166166

167167
This occurs when a `.local` path is provided for a configuration setting, such as proxy, dns, datastore or management endpoint (such as vCenter). Arc resource bridge appliance VM uses Azure Linux OS, which doesn't support `.local` by default. A workaround could be to provide the IP address where applicable.
168168

169-
### Action failed - no such host
170-
171-
When deploying Arc resource bridge, if you receive an error with `errorCode` as `PostOperationsError` and `errorResponse` as code `GuestInternetConnectivityError` and `no such host`, then the error may be caused by the appliance VM IPs not having reachability to the endpoint specified in the error.
172-
173-
Error example:
174-
175-
`{ _errorCode_: _PostOperationsError_, _errorResponse_: _{\n\_message\_: \_{\\n  \\\_code\\\_: \\\_GuestInternetConnectivityError\\\_,\\n  \\\_message\\\_: \\\_Not able to connect to http://aszhcitest01.company.org:55000. Error returned: action failed after 5 attempts: Get \\\\\\\_http://aszhcitest01.company.org:55000\\\\\\\_: dial tcp: lookup aszhcitest01.company.org: on 127.0.0.53:53: no such host. Arc Resource Bridge network and internet connectivity validation failed: cloud-agent-connectivity-test. 1. Please check your networking setup and ensure the URLs mentioned in : https://aka.ms/AAla73m are reachable from the Appliance VM.   2. Check firewall/proxy settings`
176-
177-
In the example, the appliance VM IPs are not able to access `http://aszhcitest01.company.org:55000`. Please work with your network administrator to grant the proper access to the appliance VM IPs.
178-
179169
### Azure Arc resource bridge is unreachable
180170

181171
Azure Arc resource bridge runs a Kubernetes cluster, and its control plane requires a static IP address. The IP address is specified in the `infra.yaml` file. If the IP address is assigned from a DHCP server, the address can change if it's not reserved. Rebooting the Azure Arc resource bridge or VM can trigger an IP address change and result in failing services.
@@ -255,6 +245,16 @@ Resource move of Arc resource bridge isn't currently supported. You'll need to d
255245

256246
For general help resolving issues related to Azure Arc-enabled VMs on Azure Stack HCI, see [Troubleshoot Azure Arc-enabled virtual machines](/azure-stack/hci/manage/troubleshoot-arc-enabled-vms).
257247

248+
### Action failed - no such host
249+
250+
When deploying Arc resource bridge, if you receive an error with `errorCode` as `PostOperationsError` and `errorResponse` as code `GuestInternetConnectivityError` and `no such host`, then the error may be caused by the appliance VM IPs not having reachability to the endpoint specified in the error.
251+
252+
Error example:
253+
254+
`{ _errorCode_: _PostOperationsError_, _errorResponse_: _{\n\_message\_: \_{\\n  \\\_code\\\_: \\\_GuestInternetConnectivityError\\\_,\\n  \\\_message\\\_: \\\_Not able to connect to http://aszhcitest01.company.org:55000. Error returned: action failed after 5 attempts: Get \\\\\\\_http://aszhcitest01.company.org:55000\\\\\\\_: dial tcp: lookup aszhcitest01.company.org: on 127.0.0.53:53: no such host. Arc Resource Bridge network and internet connectivity validation failed: cloud-agent-connectivity-test. 1. Please check your networking setup and ensure the URLs mentioned in : https://aka.ms/AAla73m are reachable from the Appliance VM.   2. Check firewall/proxy settings`
255+
256+
In the example, the appliance VM IPs are not able to access `http://aszhcitest01.company.org:55000`. Please work with your network administrator to grant the proper access to the appliance VM IPs.
257+
258258
### Authentication handshake failure
259259

260260
When running an `az arcappliance` command, you might see a connection error: `authentication handshake failed: x509: certificate signed by unknown authority`

0 commit comments

Comments
 (0)