From ecbb0cc4799a4000d020d35d33822bc819caccee Mon Sep 17 00:00:00 2001 From: kisfenyo Date: Tue, 3 Nov 2026 04:13:52 +0100 Subject: [PATCH] REPORT: 2026-11-02 night, R-1302, commit only --- REPORT.md | 29 +++-------------------------- 1 file changed, 3 insertions(+), 26 deletions(-) diff --git a/REPORT.md b/REPORT.md index 3ef6bbc..cb37fc2 100644 --- a/REPORT.md +++ b/REPORT.md @@ -1,28 +1,5 @@ -# REPORT — v0.171.0 released and vouched: a controller that runs but does not answer is restarted (R-1344, 2026-10-30, attended) +# REPORT — 2026-11-02 night: R-1302, commit only (no release) -**Plain words first.** The night's health log showed that a busy night (backups, dumps, updates) never makes the -controller miss even one health check — the slowest answer was 0.3 s against a 5 s limit. So the agent no longer only -alarms about a controller that runs but does not answer: 2 minutes after the alarm it restarts it, unless the -controller is busy with a backup, a restore or an update, or the restart brake holds. +**Plain words.** Nothing was released. A new box no longer logs „investigate the loss" for a grant it simply never had; a grant that existed and vanished still does. -## Commits - -| Commit | CI (job id) | What | -|---|---|---| -| `bd18347` | 2532 green | `controllerUnresponsiveRestart` = 10 sweeps; `restartUnresponsive` (busy file, then the brake); the brake and the restart record shared with the not-running restart (`supervisorBrakeAllows`, `recordSupervisorRestart`); stanza `unresponsive_restart_after_s`, `unresponsive_restart_at`. Tests red first (build failure, then 3 behaviour failures); 7 mutants, one survivor (the count reset after a restart) pinned by a new assertion. | -| `84726c9` | (read at the close-out) | v0.171.0 heading; `pinned.day0_agent` = 0.171.0. | - -## Release - -- `release-agent.sh 0.171.0` from a clean clone of `bd18347`: sha256 `c888ca7ba22a1f689059081575814a725e2edcecbb6bcc56829e9d9de88202a5`, - bundle `95f977f6dc827185f2b5a2aa9e1c829db41a9f425d49eb40f317286d13c83d2b`, tag `v0.171.0`, verified by download. -- configs/ unchanged → one signed `agent_update` per box (Tester 1, demo-hp, demo-felhom): all COMPLETED and - „update committed" (10:12–10:20 CET); no new error lines. -- Vouched by the operator 2026-10-30 10:47:36 CET (the save took 132 ms — felhom.eu R-1346, hub 0.178.0). - -## Live proof (Tester 1, controller 0.349.0) - -`docker kill --signal=SIGSTOP felhom-controller` 09:24:50 UTC → Docker „unhealthy" 09:26:36 → the agent's alarm -09:29:21 (6 sweeps) → „the controller does not answer — restarting the bootstrap unit" 09:31:22 (10 sweeps) → healthy -09:31:24. The hub mailed `controller_unresponsive_restart` and `controller_unresponsive` (09:42:56, with the next report) -and not `controller_restarted_by_agent`. Evidence: felhom.eu `documentation/audits/release-2026-10-30/p1-r1344/`. +`50eeccc`, CI job 2552 green. `/store-grant-seen.json` remembers which tiers held their grant; a first grant logs INFO and reports healthy; a doubt (no file path, an unreadable or corrupt file) keeps the ERROR. Tests `TestR1302_*` (`cmd/felhom-agent/storegrant_test.go`), seen failing before the code existed and on four mutants. Not seen live: it needs a release and the operator's vouch. A box updated to it records its tiers at the first healthy probe, so a loss in the one probe before that reads as a first grant.