---
id: "bug-1942"
status: "open"
status_updated: "2026-10-10"
status_note: "newly logged"
component: "controller"
severity: "wrong-result"
timestamp: "2026-10-10T08:14:51Z"
last_seen: "2026-10-10T08:14:51Z"
occurrences: 1
files: ["src/controller/job.c"]
tags: ["controller", "job-control", "parallel"]
related: []
---

# bug-1942: xce_controller sends job control of a multi-host job only to its first host

## Description
**Observed:** (source reading, `.kiro/reviews/project-gap-review-2026-10-10.md` (P0); to be confirmed by a failing test before the fix)
Job control is routed to `allocs[0]->host` only (`src/controller/job.c:2126-2131`).

**Expected:** Signals reach every host of the job (or the job's launcher is documented to fan them out and does so).
**Impact:** Suspending or killing a multi-host job can leave its tasks on other hosts running.
**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
1. Run a 2-host job (e.g. `/xce-test-multihost`), stop it.
2. Tasks on the second host keep running.
- 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