myxce/.wolf/bugs/bug-1905.md
Rongsong Shen 6e631caa22
fix: scheduler empty-resreq JOB_UPDATE crash (bug-1904); xcecli jobs list rejection text (bug-1906)
bug-1904: both scheduler JOB_UPDATE paths parsed "" as-is:
parse_resreq() returns success with a PRIMARY container whose body is
NULL, and apply_job_task_count() wrote through it. Use ingest's default
("type == any") instead.

bug-1906: xcecli jobs list sent local selection-parse errors through
ExtractErrorMessage, which strips brackets and the quoted selection;
report them as written.

Also logs bug-1905 (xcecd_virtual ignores kill of a running job). All
three found by job-array-one-based-index task 10.2's live REST flow.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-01 14:48:50 +00:00

59 lines
2.8 KiB
Markdown

---
id: "bug-1905"
status: "open"
status_updated: "2026-10-01"
status_note: "newly logged"
component: "worker"
severity: "wrong-result"
timestamp: "2026-10-01T14:32:18Z"
last_seen: "2026-10-01T14:32:18Z"
occurrences: 1
files: ["src/worker/src/controller_connector.c", "src/worker/src/xcecd_dbus_manager.c"]
tags: ["virtual-cluster", "job-control", "kill"]
related: []
---
# bug-1905: xcecd_virtual ignores kill of a running job: job keeps RUN until its sleep time elapses
## Description
**Observed:**
```
14:17:47,625 controller_connector.c:1546 Received job control request to send SIGINFO for job ID: 1-0-1790864259-0
14:17:47,625 controller_connector.c:1610 Job control task handled directly for job ID: 1-0-1790864259-0
14:27:40,008 xcecd_worker_utils.c:847 Sleep time 600 >= 600 seconds elapsed for worker 1009 (job 1-0-1790864259-0)
ctrl-1: on_job_finish job finish jobid 1-0-1790864259-0 exit code 0
```
`xcecli jobs kill` of a RUN job (plain `sleep 600`, and array elements `arr3[2]`, `arr3[3]`) is accepted (apiserver: `overallStatus accepted`, SIGTERM) and reaches the virtual worker, but the job stays RUN and finishes DONE with exit 0 when its sleep time elapses. Killing a PEND job works (EXIT).
**Expected:** the virtual worker ends a killed running job as EXITED with exit code 128+signal on its next poll (the `killed_signal` branch in `xcecd_dbus_manager.c:259-262`).
**Impact:** kill of running jobs cannot be exercised on virtual-worker deployments (tests, soaks); the real worker path (`ipc_master_send_job_signal`) is not affected by this record.
**Found by:** spec task (job-array-one-based-index task 10.2 live REST flow)
## 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 (src/build.jai)
- Code: scheduler-framework @ 6439e585-dirty
- Deployment: 3-node HA (xce-deploy-ha) + scheduler + apiserver + one xcecd_virtual worker, single host
## Reproduction
1. Deploy with xce-deploy-ha and `start-all.sh`; `xcecli login -u admin -p admin --url http://localhost:8080`.
2. `xcecli jobs submit -J plain2 sleep 600 </dev/null`; wait until `xcecli jobs list` shows RUN.
3. `xcecli jobs kill <id> </dev/null`; `xcecli jobs list -a <id>` still shows RUN, and the job ends DONE after 600 s.
- Frequency: deterministic (3/3 kills of running jobs, 2026-10-01)
- Evidence: /home/claude/tmp/bug-1905/kill-trace.log
## 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