github-actions[bot] commented on issue #11460: URL: https://github.com/apache/cloudstack/issues/11460#issuecomment-6216743403
## ๐ฏ Triage report `bind.interface` only configures server-side (Jetty) socket binding; the HTTP client used for inter-node cluster communication (`ClusterServiceServletImpl`) ignores it and uses the OS default route, causing connection timeouts in VRF/multi-homed management server setups. The reporter identified the root cause and proposed a concrete fix using a custom `ConnectionSocketFactory` with `setLocalAddress()`. ### ๐ Assessment | Dimension | Value | Reasoning | |---|---|---| | **Type** | `type:bug` | Existing config option (`bind.interface`) does not behave as documented/expected for client connections. | | **Component** | `component:management-server`, `component:networking` | Affects management server cluster communication / HTTP client networking. | | **Severity** | `Severity:Major` | Breaks cluster communication entirely in VRF/multi-homed deployments, but only affects that specific (non-default) configuration. | | **Labels** | type:bug, component:management-server, component:networking, Severity:Major | See above | | **Coding agent** | Needs more info | Root cause and a draft diff are provided, but the fix needs validation (reporter noted standard Java HttpClient APIs don't cleanly support VRF-aware binding) and test coverage in a VRF environment, which is hard to automate/verify without real infra. | ### ๐ Similar issues No similar open issues were found in search. <details><summary>๐ก Notes and suggestions</summary> - Reporter's own follow-up comments indicate the originally suggested `setLocalAddress()`-based diff may not fully solve the problem for VRF scenarios, since plain socket binding doesn't make the socket VRF-aware in Java without lower-level hacks (e.g., `SO_BINDTODEVICE` via JNI/shell). - Relevant files: `framework/cluster/src/main/java/com/cloud/cluster/ClusterServiceServletImpl.java` (client), `client/src/main/java/org/apache/cloudstack/ServerDaemon.java` (server-side binding works correctly, can be used as a reference). - A maintainer with networking/Java expertise should confirm whether `SO_BINDTODEVICE` (via a native helper) is required for true VRF awareness, or if binding to the local IP address is sufficient for non-VRF multi-homed setups. - Issue has been open since Aug 2025 and was auto-flagged stale; still appears valid and unresolved. </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/38908853463) ยท sonnet50 107.4K ยท [โท](https://github.com/search?q=repo%3Aapache%2Fcloudstack+%22gh-aw-workflow-call-id%3A+apache%2Fcloudstack%2Fdaily-issue-triage%22&type=issues) > <details> <summary>Add this agentic workflows to your repo</summary> To install this agentic workflow, run ``` gh aw add githubnext/agentics/workflows/daily-issue-triage.md@d7c1dc4b72b00607a67caaffdcc216cb64379cf9 ``` </details> <!-- gh-aw-agentic-workflow: Daily Issue Triage, engine: copilot, version: 1.0.52, model: claude-sonnet-5, id: 38908853463, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/38908853463 --> <!-- gh-aw-workflow-call-id: apache/cloudstack/daily-issue-triage --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
