Space fixes released: agent 0.173.0 vouched, controller 0.352.0 global floor, hub 0.180.0 live; evidence, rows, status, report
gates / gates (push) Successful in 2m1s
gates / gates (push) Successful in 2m1s
The close-out of the attended release run of 2026-11-10 (afternoon). - Evidence: documentation/audits/release-space-fixes-2026-11-10/ (agent, controller, hub) and the hub row after the fallback-kernel test. - Rows: dated lines on R-1368, R-1371, R-1301, R-1353. 236 open before and after; opened 0, closed 0. - Capability map: dated notes under C13 and G5; no status changed. - disk-full runbook and 16 §14: the self-update folder is PROVEN as a product path on three test boxes. - STATUS: new "Updated" paragraph; the old one moved to STATUS-HISTORY. - REPORT-release-space-fixes-2026-11-10.md: wrong claims first, one deviation (the hub deploy ran before CI for the manifest-bump commit was read), what stays not proven. Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
1 parent
d0a54c2f8e
commit
bcc73b428d
40 files changed
+1037
-59
No files matched your search
@@ -278,7 +278,7 @@ The alarms, by short name:
|
||||
| H9 | old kernels | each approved kernel | none today. Ruled: keep the running one, the one before it and the newest (decision 286, `11-os-updates.md` §5.11.1). Proven by hand, not built | nobody today | host disk; later `os_update_stale` |
|
||||
| H10 | the EFI partition | a boot-loader update | 1.07 GB, 1 % used | none needed | none (R-1371) |
|
||||
| H11 | the host package cache | each OS update | emptied in each run | the update wrapper | host disk |
|
||||
| H12 | the agent's self-update folder | each agent update | none on a released agent; one binary after the next agent release (in source, R-1368) | the agent, after that release | host disk |
|
||||
| H12 | the agent's self-update folder | each agent update | the running version's binary, and the file of a failed update until the next good one (about 16 MB each; measured 2026-11-10 on three boxes, R-1368) | the agent, at the end of each good update | host disk |
|
||||
| H13 | old agent binaries | `.prev`: one file. `.bak-*`: each re-run of the installer | none for `.bak-*` (R-1368) | nobody | host disk |
|
||||
| H14 | wrapper state and previous config bundles | each bundle | the last 3 | the wrapper | host disk |
|
||||
| H15 | host `/tmp` and `/var/tmp` | nothing that lasts | `/tmp` is in memory: half of memory | systemd, after 10 and 30 days | none for `/tmp` (R-1371) |
|
||||
@@ -408,7 +408,7 @@ below 200 GB — refuse, or warn (R-1370). demo-hp (128 GB) stays as a test box.
|
||||
| Nobody watches the guest's root disk (G1, G13, G16). It is 4–5 % used today; app definitions lie on it | R-1371 |
|
||||
| No alarm for the EFI partition (H10) or for the places in memory (H15, G15, G17) | R-1371 |
|
||||
| A drive in the backup role reports as `usb` or `local-dir`. So the household gets the `storage_fill` mail for a drive it must not clean by hand | R-1371 |
|
||||
| The hub's first list for a household still holds `storage_fill_critical`. It is replaced when the box sends its own list. Not measured on the running hub in the 2026-11-10 run | R-1371 |
|
||||
| The hub's first list for a household still holds `storage_fill_critical`. It is replaced when the box sends its own list. **Not measured on the running hub:** the release run of 2026-11-10 deployed the hub that blocks the host-disk alarm at send time, but the pages that show a household's list refuse a token („session only"), and no test alarm was made. The proof is the tests and the deployed commit (`audits/release-space-fixes-2026-11-10/hub/`) | R-1371 |
|
||||
| Helper images carry no version; the guest's journal has no stated cap; off-site restores have no limit | R-1372 |
|
||||
| Old kernels: the keep rule is ruled and proven by hand, not built | `11-os-updates.md` §5.11.1 |
|
||||
| The parts of the host disk with no limit and no cleaner (H4, H5, H6, H13) | R-1087, R-1368 |
|
||||
|
||||
@@ -229,6 +229,8 @@
|
||||
|
||||
**Gap / roadmap (as written):** **Nothing warned before this.** The only prior signal was the healthcheck's generic `health_degraded` at 90%, for REGISTERED STORAGE PATHS ONLY — it never looked at the docker area or the system-data area, never gave a free-byte figure and never named a drive. **The two event types already existed with NO PRODUCER** (`disk_warning`/`disk_critical`: allowlisted, copy'd, in `DefaultEnabledEvents`, checkbox'd) — the **sixth** *built-but-never-wired* instance here; this ships their producer rather than a seventh near-duplicate type. **Two threshold terms, whichever trips first, and the live proof vindicated the design:** the critical crossing fired on the FREE-BYTE term (1.7 GB) at only **91%** used — a percentage-only rule would have missed it. The hub's generic `customerMessages` entries were REMOVED, because `FormatCustomerEmail` prefers the entry over the message and would discard the label and figures. **Known gap → R-177:** there is no operator-triggerable run-now path; the check is daily 03:30 + once at startup, so confirming a cleared warning on a support call needs a controller restart or a wait
|
||||
|
||||
**Noted 2026-11-10 (release run):** on a box with one data volume the watch counted that volume twice. Seen on scratch guest 9202 with one real fill: the old controller logged TWO warnings for it, under two names (`audits/release-space-fixes-2026-11-10/controller/03-crossing-on-0.350.0.txt`); the fixed controller logged ONE warning, and cleared it without a message when the file was removed (`04-rc1-on-9202.txt`). On the three test boxes the watch now checks 2 filesystems, was 3 (`09-fs-identity-after.txt`). 9202 has no hub, so no mail was sent; one mail for one fill is proven by the box's own record, not by a mailbox. Still open: the guest's root disk has no watcher (R-1371).
|
||||
|
||||
---
|
||||
|
||||
<a id="c14"></a>
|
||||
|
||||
@@ -91,6 +91,8 @@
|
||||
|
||||
**Gap / roadmap (as written):** Remote-customer proof pending → R-1
|
||||
|
||||
**Noted 2026-11-10 (release run):** the agent now removes old downloaded binaries after a good update: 49, 48 and 33 files became 1 on demo-hp, the N100 and Tester 1. A rollback after that clean-up was proven on Tester 1: a signed update to the older version, one crash 9 seconds into the 60-second dwell, and the wrapper put the previous binary back in the same second (`audits/release-space-fixes-2026-11-10/agent/07-rollback-proof.txt`). This is one crash, not a crash loop.
|
||||
|
||||
---
|
||||
|
||||
<a id="g6"></a>
|
||||
|
||||
Reference in new issue
Block a user