myxce/.wolf/bugs/bug-1961.md

id	status	status_updated	status_note	component	severity	timestamp	last_seen	occurrences	files	tags	related	gitea_issue	gitea_synced_status	gitea_synced_hash
bug-1961	open	2026-10-10	newly logged	apiserver	wrong-result	2026-10-10T10:16:04Z	2026-10-10T10:16:04Z	1	src/frontend/apiserver/controllers/hosts.go	apiserver hosts		392	open	7371293540aa

bug-1961: apiserver ControlHost writes a second response after validateHost rejected the request

Description

Observed: (source reading; follow-up of the 2026-10-10 P0 fixes (bug-1936..1957)) Reported by the bug-1949 fix: validateHost (controllers/hosts.go) writes a 403 via ReturnError without aborting and ControlHost continues and writes another response (today masked by the route's RequirePermission).

Expected: A rejected host control stops after the first error response. Impact: Wrong result / noise: double responses, possible action after a rejection if the route guard changes. Found by: follow-up of the 2026-10-10 P0 fixes (bug-1936..1957)

Environment

• OS: no /etc/os-release; Docker container; NixOS kernel; kernel Linux 6.18.33 x86_64
• libc: glibc 2.42-47 (interpreter /nix/store/wb6rhpznjfczwlwx23zmdrrw74bayxw4-glibc-2.42-47/lib/ld-linux-x86-64.so.2)
• Toolchain: gcc (GCC) 15.2.0, meson 1.9.1
• Build: asan (xce.build)
• Code: scheduler-framework @ 19be145d-dirty
• Deployment: any (found by source reading; confirmed by the RED test of the fix)

Reproduction

1. Call ControlHost so that validateHost rejects (see the handler) with the route guard removed in a unit test; two writes occur.

• Frequency: deterministic (by code reading; confirmed by the RED test of the fix)
• Evidence: the code sites quoted in Description; no logs kept.

Root cause

TODO: required for fixed/partial

Fix

TODO: required for fixed/partial

Verification

• Test: TODO: name + file; RED before the fix, GREEN after
• Suites: TODO: suite results and build profile
• Live: TODO: soak/deploy run, or n/a and why

References

• Related: none