systemd version compatibility for OOMPolicy property
Cluster 102486. Data as of
Nothing open on GitHub. Fix merged in #104152 on 6 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #104152. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #104152. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a failure where OOMPolicy=kill is rejected by older systemd versions (notably 249), causing cron and kanban worker dispatch to break. The fix involves negotiating or dropping unsupported transient scope properties based on the running systemd version.
Open issues0
Open PRs0
Fixes on record
-
#104152 fix(process): cron and kanban workers dispatch again on systemd < 253 — drop OOMPolicy from scope argv (#102486, salvage #102357)
files:
tests/tools/test_process_registry.py,tools/process_registry.py
2 PRs closed without merging
From the close comments: superseded by another PR 2
Closed issues · 1
- Closed#102486[Bug]: restart-safe cron worker dispatch fails closed on systemd 249 — OOMPolicy=kill rejected as unknown assignment
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #104152
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 6 Sep 2026