night build 2026-11-14: the N100's first night kernel removal read (D82: 1 of 2), close-out — report, status, register
gates / gates (push) Successful in 2m8s

Reads only on the N100 and demo-hp; no box changed, nothing released.

Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
admin committed 2026-11-15 06:41:21 +01:00
1 parent 5da5b05192
commit fffbb40ce0
17 files changed
+830 -4

No files matched your search

+1
View File
@@ -55,3 +55,4 @@ what happened, who noticed, and the register row it became. Prose here is not a
- **2026-11-05..07 — the nightly Proxmox update step refused three nights in a row.** `proxmox-grub` 2.12-9+pmx4 needs `grub-efi-amd64` of the same version; the update wrapper put `proxmox-grub` in the Proxmox group (its boot-package rule matched only names that START with `grub`), so the whole step was refused (R6) and 34 Proxmox updates waited; an `os_update_failed` mail each morning. Apps not touched. Agent 0.172.1 puts `proxmox-grub` with the boot packages; it reaches the box by the operator's vouch and two signed jobs. Register: fixed in the session (size rule), recorded in the agent's CHANGELOG. Evidence: `audits/demo-check-2026-11-07/n100-pve-step-R6.txt`. (CC)
- **2026-11-10 — every place that holds data was measured (read-only; the space list).** Host system disk 38.09 of 100.86 GB (38 %), 4.6 GiB more than on 10-15: the box holds 8 kernels (8.15 GB) and none was ever removed → R-1368. The agent's self-update folder holds 48 old binaries (724 MB) and there are 11 old agent copies beside the binary (155 MB) → R-1368. The host journal sits at its cap (4.28 GB, 74 files, oldest entry 10-04) → R-1367. The three whole-box copies of 2026-07-28 still lie on the system disk (17.59 GB) → R-1087; four template archives (2.56 GB) → R-1368. On the USB drive, `backups/offsite-restore` holds 1.65 GB of two apps that are not installed any more → R-1372. Nothing was deleted or changed. Table: `audits/space-list-2026-11-10/TABLE.md`. (CC)
- **2026-11-14 — the clock is right again, repaired by the product.** When the box took agent 0.174.0 and its root files (11:36 and 11:51 UTC), the new „profile refresh" found the old security profile of the time service, loaded the right one and started the service: the clock stepped forward 32.7 s (offset to DooPlex −32.55 s → +0.18 s; still so 2.5 hours later). Nine seconds after the step the controller read a new boot and recreated Radarr, Sonarr and qBittorrent once (each down for a few seconds; all healthy). A dry run says tonight's night removes 6 of the 8 kernels. Register: R-1301 and R-1388 closed, R-1395 (the controller and the clock step), R-1368 (the kernels — read the night of 11-15). Evidence: `audits/release-2a-2026-11-14/D/` (`09`, `13`, `13b`, `14`). (CC)
- **2026-11-15 — the box removed its old kernels by itself, the first time.** At 05:58 CET, at the end of the night's update run (the Proxmox step applied 12 packages first), the clean-up purged 6 of 8 kernel packages in 35 s and kept 7.0.14-26 and the running 7.0.14-28: 6.81 GB gained, 65.1 GB free after, 0 left-over paths. The default kernel and the pinned file did not change; 0 failed units, 9 of 9 containers healthy, the clock +0.06 s to DooPlex; the hub's „Kernel step” cell reads „cleaned”. Nothing was done by hand. Register: R-1368 (D82: 1 of 2 nights). Evidence: `audits/night-build-2026-11-14/E/`. (CC, read-only)