docs(buglog): log P0 defects from the 2026-10-10 review (bug-1936..bug-1952)

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

2026-10-10 08:15:28 +00:00

2 KiB

Raw Blame History

status

status_updated

status_note

component

severity

timestamp

last_seen

occurrences

files

bug-1941: xce_controller refuses kill/stop/resume of running jobs on hosts whose status is not exactly OK

Description

Observed: (source reading, .kiro/reviews/project-gap-review-2026-10-10.md (P0); to be confirmed by a failing test before the fix)

/* FIXME: better method to check host status */
if (w->ep && w->host.status == 0) {      /* src/controller/job.c:2145-2156 */

Any other status bit (CLOSED_BY_ADMIN, BUSY, UNAVAIL...) makes the control request fail.

Expected: Jobs on a closed (or otherwise flagged but connected) host can be killed, stopped and resumed; a host that is not connected gives a clear error. Impact: Users and admins cannot kill jobs on a host closed for maintenance. Found by: review: .kiro/reviews/project-gap-review-2026-10-10.md (P0)

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 @ 94472ee3-dirty
Deployment: any (found by source reading; the failing test that confirms it is named in Verification)

Reproduction

Run a job on host h, close h, kill the job.
The kill is refused.

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