clawdie/layered-soul
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

skill(freebsd): add re-register-with-mother after upgrade (step 8)

Browse source 
The node OS version changed after the upgrade, but the mother hive_nodes
row still shows the old freebsd_version. Re-running the probe + node_register
makes the upgrade visible to the scheduler.

Renumbered: 8→9 (vulnerability audit).
This commit is contained in:
Sam & Claude 2026-06-25 11:55:28 +02:00
parent 524a3c3153
commit bcb769f2e0
1 changed files with 14 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
skills/freebsd-os-upgrade/SKILL.md
View file

@ -122,7 +122,20 @@ pkg update -f && pkg upgrade # ports packages (separate from base here)
PostgreSQL bump needs no dump/restore (restart/reboot to load new binaries). PostgreSQL bump needs no dump/restore (restart/reboot to load new binaries).
7. **Upgrade the jails** — the host upgrade does NOT touch them. Do this after 7. **Upgrade the jails** — the host upgrade does NOT touch them. Do this after
the host is on the new kernel. See *Jails* below. the host is on the new kernel. See *Jails* below.
8. **Vulnerability audit**: if `pkg audit` still flags packages (host or jails), 8. **Re-register with mother** — the node's OS version changed. Re-run the
hardware probe and push the updated profile so the mother's hive_nodes row
reflects the new `freebsd_version`. If COLIBRI_AUTOSPAWN is active, the
daemon will re-spawn zot on the next tick and the RPC prompt includes
node_register; otherwise run the probe + MCP call manually:
```sh
clawdie-hw-probe | jq .freebsd_version # confirm 15.1
# Re-run node_register via the MCP boundary (or let autospawn handle it)
```
This is what makes the upgrade visible to the scheduler — without it,
the mother still thinks the node is on the old release.
9. **Vulnerability audit**: if `pkg audit` still flags packages (host or jails),
do not imply the upgrade failed — the upgrade completed; unrelated packages do not imply the upgrade failed — the upgrade completed; unrelated packages
remain vulnerable until fixed versions land. (Wording in the reference.) remain vulnerable until fixed versions land. (Wording in the reference.)