From d81a7410e21a5b540aceb41e34554ee3bc14312d Mon Sep 17 00:00:00 2001 From: YueGuobin Date: Sat, 25 Apr 2026 15:55:37 +0800 Subject: [PATCH] docs: remove misleading Controller Hostname Unreachable section This section was misleading - the actual root cause is host=0.0.0.0 causing controller to register as 127.0.0.1, not hostname resolution. Co-Authored-By: Claude Opus 4.6 --- docs/features/compute-controller-setup.md | 19 ------------------- 1 file changed, 19 deletions(-) diff --git a/docs/features/compute-controller-setup.md b/docs/features/compute-controller-setup.md index d5049fb00..75f4a66c8 100644 --- a/docs/features/compute-controller-setup.md +++ b/docs/features/compute-controller-setup.md @@ -112,22 +112,3 @@ Cannot get an IP address on same subnet: No common subnet for compute X (control 4. Verify both machines are on the same network and can ping each other 5. Check firewall rules allow TCP/UDP communication on required ports -### Controller Hostname Unreachable - -If the controller machine uses a hostname defined in `/etc/hosts` (e.g., `guobin.localhost`), and the compute node reports: - -``` -Cannot get an IP address on same subnet: No common subnet for compute X (controller) and Y -``` - -1. **Symptom**: The controller's hostname resolves to an IP that is unreachable from the compute node -2. **Root Cause**: The `/etc/hosts` entry for the controller's hostname points to a stale or unreachable IP address -3. **Solution**: - - Ensure the controller's hostname in `/etc/hosts` resolves to the correct, reachable IP address - - Example (correct): - ``` - 192.168.1.104 guobin.localhost - ``` - - If the machine's IP is dynamic (DHCP), consider: - - Setting a DHCP static lease on the router for a fixed IP - - Using mDNS (`.local` domain) if supported by the compute node