hub (unreleased): the System page shows the kernel clean-up and the security-profile refresh; a clean-up no longer hides a kernel step (R-1383)
gates / gates (push) Successful in 2m20s
gates / gates (push) Successful in 2m20s
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
1 parent
e5c643d73d
commit
68292e40f6
14 files changed
+452
-13
No files matched your search
@@ -670,8 +670,19 @@ until a later step ends `good`.
|
||||
kernel-layer report with outcome `cleaned`; the System page's „Kernel step" cell then reads „cleaned <time ago>", and
|
||||
the report's text (what was removed, kept and gained) is stored but shown nowhere. A refusal or a failure raises the
|
||||
existing operator event „Kernel step on <box> refused/failed: …". „Nothing to remove" and „not run" are log lines
|
||||
on the box only. The report carries no kernel version on purpose: the hub reads that as a kernel step. What is missing
|
||||
is in R-1383 (release 3).
|
||||
on the box only. The report carries no kernel version on purpose: the hub reads that as a kernel step. **Corrected
|
||||
2026-11-14 (night):** the text was shown — as the cell's hover title — and the cell had a defect: a clean-up and a
|
||||
kernel step are both kernel-layer reports, and the cell showed the NEWEST of the two, so a clean-up the night after a
|
||||
kernel fell back replaced the amber „fell_back” line with „cleaned”.
|
||||
- **`[FACT — built, not released: agent `main` after 0.174.0 and hub `main` after v0.181.0, 2026-11-14; R-1383,
|
||||
release 3]`** The clean-up's report carries its own object `kernel_cleanup` (`removed` — package names, `kept` —
|
||||
kernel versions, `bytes_gained`, `leftovers` — a count). It is NOT the `kernel` view: the report still has no `kernel`
|
||||
key and its `release_id` is `kernel-cleanup`, and the hub's `kernelOf` reads only those two — so the names in the new
|
||||
object cannot be read as a step (tested on both sides). The hub keeps the object in the stored report, reads the newest
|
||||
STEP and the newest CLEAN-UP each from its own report (`KernelLineFor`), and the System page has a cell of its own,
|
||||
**„Kernel clean-up”**: „removed 6, kept 2 · 6.0 GiB gained · 3 h ago”, the names in the title; amber when it was
|
||||
refused or failed, or left paths behind. An agent of 0.174.0 sends no object: the cell then reads „cleaned <time
|
||||
ago>” with the report's text as its title. Not seen on a box or a deployed hub.
|
||||
|
||||
**Proven on boxes with the program** (2026-11-14, `audits/release-2a-2026-11-14/D/`): Tester 1 — 3 kernels → 2
|
||||
(`proxmox-kernel-7.0.14-20-pve-signed`), 1.12 GB gained, 8.5 s, nothing else changed, no left-over, the second call
|
||||
@@ -712,8 +723,19 @@ takes nothing from the plan but `dry_run`, F1):
|
||||
4. A parser failure writes no record; the next start tries again.
|
||||
|
||||
**The agent** asks at every start and after a config bundle was installed (a new wrapper may know the mode the old one
|
||||
refused), under the heavy-op gate (up to 12 tries, 5 minutes apart) and never beside an OS-update pass. Nothing goes to
|
||||
the hub (no field exists for it; R-1383).
|
||||
refused), under the heavy-op gate (up to 12 tries, 5 minutes apart) and never beside an OS-update pass. In agent
|
||||
0.174.0 nothing goes to the hub.
|
||||
|
||||
**`[FACT — built, not released: agent `main` after 0.174.0 and hub `main` after v0.181.0, 2026-11-14; R-1383,
|
||||
release 3]` What the hub is told.** Not an OS report: the hub reads a report of a layer it does not know as a GUEST
|
||||
step. The result rides the host report as the stanza `profile_refresh`: `kernel`, `at`, `rewritten` (a count) and
|
||||
`restarted` (unit names) from the ROOT wrapper's own record (`/var/lib/felhom-os-apply/profile-refresh.json`, 0644 —
|
||||
so the box's last refresh is still told after an agent restart), and `last_ask` / `last_ask_at` — how the last ask of
|
||||
this agent process ended (refreshed · not_needed · failed · refused · no_answer). The agent reads one small file and
|
||||
does not call the wrapper for it; a name that is not a plain unit name is dropped. The System page's cell
|
||||
**„Security profiles”** reads „7.0.14-28-pve · 2 rewritten · 18 h ago · restarted chrony.service”; amber, and under
|
||||
„Needs attention”, when the last ask failed or got no answer. A refused ask (an older wrapper, a BYO host) is not a
|
||||
fault. No alarm is raised for a restart: it is shown, not mailed. Not seen on a box or a deployed hub.
|
||||
|
||||
**Measured on demo-hp, both guests running** (`audits/profile-refresh-spike-2026-11-14/`): the fault was reproduced
|
||||
with one planted stale profile (chrony failed with the N100's own error); the refresh took 0.51 s; the same 119
|
||||
|
||||
Reference in new issue
Block a user