NODES.md: mark ghost nodes def, dev inactive

The unassigned def/dev nodes were being iterated every 5 min by
agent-health.sh (via netvm-registry.py active_nodes()), producing a
perpetual FAIL -> kill -9 -> CRITICAL loop since they can never
"recover". fleet-alert-check.sh iterates the same registry, so this
also stops ghost-node alert noise. The dev registry row itself came
from another session's uncommitted work; this commit keeps their row
and marks it inactive rather than provisioning a node nobody asked
for.

Session: sidechat/chromebox-fixes
This commit is contained in:
operator-main
2026-10-04 22:47:02 +00:00
parent 76f854da6b
commit 3d5fbe5aeb
+2 -1
View File
@@ -12,4 +12,5 @@ Unified naming: node == agent == profile == API account.
Profiles preserved, sessions persisted (muse). WireGuard identities renamed. Profiles preserved, sessions persisted (muse). WireGuard identities renamed.
| 646 | warp-646 | 104.28.195.181 | 9430 | active | 646 (phone_otp, first Meta Account option) | | 646 | warp-646 | 104.28.195.181 | 9430 | active | 646 (phone_otp, first Meta Account option) |
| opm | warp-opm | 104.28.195.181 | 9440 | active | opm (yourfriendnico@proton.me, email_otp, Nico Parada) | | opm | warp-opm | 104.28.195.181 | 9440 | active | opm (yourfriendnico@proton.me, email_otp, Nico Parada) |
| def | warp-def | 104.28.195.181 | 9450 | active | (unassigned) | | def | warp-def | 104.28.195.181 | 9450 | inactive | (unassigned) |
| dev | warp-dev | 104.28.195.181 | 9460 | inactive | (unassigned) |