runbook(park 100): 4 kernel reboots done (nh3-extdev, corviduo-dev, esh-vm-db, pfi-pteradactyl)

This commit is contained in:
vh
2026-10-05 11:09:17 -07:00
parent a808b349b8
commit 912d932917
2 changed files with 5 additions and 3 deletions
@@ -114,8 +114,10 @@ bouncer failing closed on slow LAPI answers. Self-cleared.
- ana-nas (NFS SPOF) and irv-ml1 (Prime: off-limits): out of scope.
**Deferred to a daytime window:**
- reboots to activate new kernels: ana-docker, nh3-dev, nh3-extdev, corviduo-dev, vm-esh-nas, esh-vm-db, plus
pfi-tacticalrmm and pfi-pteradactyl (added later on 10-05). None builds NVIDIA with DKMS.
- reboots to activate new kernels: ~~nh3-extdev, corviduo-dev, esh-vm-db, pfi-pteradactyl~~ (rebooted 2026-10-05
1055–1109 on Prime's word; all came back clean, boot ids changed, 0 failed units). Still pending: ana-docker, nh3-dev,
vm-esh-nas, pfi-tacticalrmm. None builds NVIDIA with DKMS. ⚠ corviduo-dev's Worldtree APIs take ~3 min to answer
`/health` after boot (startup, not a fault); wings on pfi-pteradactyl restores the running game server by itself.
- Docker engine bumps held on ana-docker, nh3-docker, esh-docker-vm, corviduo-dev, nh3-dev, esh-ml1, nh3-ml1, pfi-gx10.
- fv-ml1: ZFS 2.3.9, nvidia-container-toolkit 1.20, and a kernel with an NVIDIA driver that builds on it.
- CrowdSec bouncer `updateMaxFailure` (0 = block on the first failed LAPI pull): infra-ops leans toward ~3.