From 070e9992f26e12857812606fad2dec460458a6ea Mon Sep 17 00:00:00 2001 From: "lei.chen" Date: Tue, 1 Sep 2026 15:26:33 +0000 Subject: [PATCH] fix(apiserver): restore pending_reason in JOB_DEFAULT_COLUMN (merge regression) The scheduler-framework merge (3b6f53bb) dropped ac6131d's "pending_reason" from models.JobInfo JOB_DEFAULT_COLUMN during conflict resolution (took theirs). Default job queries returned pending_reason:null even though the scheduler attaches reasons, the controller stores them on job->pend_reasons, and the apiserver's in-memory store has them. Found during the 2026-09-01 full job cluster verification: scheduler P1 TIME_WINDOW/HOST_UNAVAIL reasons confirmed end-to-end via controller set_preason/apiserver hook debug logs and apiserver dataset-push debug logs; only the default query column selection was missing. Verified after the fix: night queue (window closed) -> main_reason:8 time_window; all workers stopped -> main_reason:9 host_unavail with per-host details. Co-Authored-By: Claude Code --- src/frontend/apiserver/models/jobs.go | 1 + 1 file changed, 1 insertion(+) diff --git a/src/frontend/apiserver/models/jobs.go b/src/frontend/apiserver/models/jobs.go index 050d2e94..5fef00b7 100644 --- a/src/frontend/apiserver/models/jobs.go +++ b/src/frontend/apiserver/models/jobs.go @@ -206,6 +206,7 @@ var JOB_DEFAULT_COLUMN = []string{ "job_name", "command", "submit_time", + "pending_reason", } var ARRAY_JOB_DEFAULT_COLUMN = []string{