docs(buglog): log follow-ups of the P0 fixes (bug-1958..bug-1966)

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Rongsong Shen 2026-10-10 10:16:33 +00:00
parent 19be145d6f
commit 7b77ce9c1d
Signed by untrusted user: rshen
GPG key ID: 80533536B0EB651C
10 changed files with 659 additions and 0 deletions

49
.wolf/bugs/bug-1961.md Normal file
View file

@ -0,0 +1,49 @@
---
id: "bug-1961"
status: "open"
status_updated: "2026-10-10"
status_note: "newly logged"
component: "apiserver"
severity: "wrong-result"
timestamp: "2026-10-10T10:16:04Z"
last_seen: "2026-10-10T10:16:04Z"
occurrences: 1
files: ["src/frontend/apiserver/controllers/hosts.go"]
tags: ["apiserver", "hosts"]
related: []
---
# 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