recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

review(5): §4 cron T0 MISS — busybox crond non-functional as non-root (A5-7 OPEN)
Some checks failed
continuous-integration/drone/push Build is failing
Details

Browse Source 
Cold-verified at 23:11Z: T0 (23:04Z) was missed; no upgrader-cron.log created.
busybox crond with -c dir requires root for setuid; silently skips all jobs as
non-root 'loops' user. Confirmed by both T0 miss and a * * * * * control probe
(waited through 23:09+23:10, nothing fired).

V9 PASS stands. Gate M5 remains open pending a working cron mechanism + re-fire.
A5-7 filed in BACKLOG-5. BUILDER-INBOX sent.
This commit is contained in:
autonomic-bot
2026-06-01 23:13:01 +00:00
parent 4ff208d0b6
commit dc12153f1b
3 changed files with 106 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
machine-docs/REVIEW-5.md
View File

@ -685,3 +685,29 @@ review). The RESULT artifacts are preserved on disk.
**V8a: PASS (with noted gap)** — core functionality (automated lifecycle, run-to-completion,
log artifacts) all confirmed. The session self-termination is a known behavior gap, not a blocking
defect for V8a's primary purpose (weekly cron automation).
---
## §4 cron T0 fire: FAIL — 2026-06-01T23:11Z
Finding: A5-7. The §4 weekly cron mechanism (busybox crond in tmux session `cc-ci-crond`) does NOT
execute jobs. T0 (23:04Z) was missed and no job ever fires.
**Cold-verified evidence:**
- T0=23:04Z; checked at 23:06Z and 23:11Z: no `/srv/cc-ci/.cc-ci-logs/upgrader-cron.log` exists.
- `crond.log` (153 bytes) last modified 22:08:44 UTC — only startup messages, no job-execution entries.
- `python3 launch-upgrader.py status` at 23:07Z → "stopped" (no session started by cron at 23:04Z).
- Control probe: added `* * * * *` test entry, waited through 23:09 and 23:10 UTC — no fire.
**Root cause confirmed:** busybox crond with `-c dir` requires root to call `setgid/setuid` before
executing jobs. Running as non-root user `loops`, all jobs are silently skipped.
**Gate status:** The §4 cron install requires "verify the cron-equivalent path end-to-end; confirm
real first fire at T0." T0 missed. The plan says "if it did NOT fire (PATH, login, mechanism), fix
and re-verify." The mechanism is wrong; a fix is required.
**§4 cron: FAIL** @2026-06-01T23:11Z — busybox crond non-functional; T0 missed. Filed as A5-7.
The gate claim (M5 CLAIMED) remains OPEN pending a working re-installation and T0 equivalent fire.
Note on V9: V9 (cleanup) PASS is NOT affected by this finding — the cleanup evidence was separately
cold-verified at 22:13Z and holds. Only the §4 cron first-fire is broken.