---
id: "bug-1860"
status: "fixed"
status_updated: "2026-09-27"
status_note: "c69705ae: controller is ground truth on rejoin; controller refuses non-PEND dispatch and re-sends state; scheduler adopts controller allocation on RUN update"
component: "controller"
severity: "unknown"
timestamp: "2026-09-24T14:38:03Z"
last_seen: "2026-09-24T14:38:03Z"
occurrences: 1
files: ["src/scheduler/src/core_events.c", "src/controller/sched.c", "src/controller/resync.c"]
tags: ["scheduler", "controller", "resync", "ha", "divergence", "design"]
related: []
fix_commits: ["c69705ae"]
legacy: true
gitea_issue: 279
gitea_synced_status: "fixed"
gitea_synced_hash: "92556ffb1968"
---

# bug-1860: Scheduler keeps a job RUN (with allocation) forever after the controller requeued it to PEND while…

## Description
Scheduler keeps a job RUN (with allocation) forever after the controller requeued it to PEND while the scheduler was disconnected: scheduler.log 'JOBS_PUSH: refusing resync state 0x1 for jobid ... -- existing job is RUN with a real allocation on record' on rejoin; job never redispatched (seen in bug-1859's chaotic soak)

## Environment
_Not recorded (migrated from buglog.json)._

## Reproduction
_Not recorded (migrated from buglog.json)._

## Root cause
core_events.c JOBS_PUSH bug-1812 guard refuses any non-terminal resync state that would drop a real allocation, to protect against a committed snapshot racing the scheduler's own fresh dispatch. It cannot tell that race apart from a genuine, committed controller-side requeue (e.g. resync 'unrecognized' -> record_job_reconcile_pending_fact) that happened while the scheduler was disconnected, and JOBS_PUSH carries no per-job freshness (commit LSN/version) to decide. Needs a design decision (e.g. per-job last-modified LSN in the push).

## Fix
_Not recorded (migrated from buglog.json)._

## Verification
_Not recorded (migrated from buglog.json)._

## References
- Gitea: #279