Judge the machine's own networking beside what its modules run (hq ADR 0241) #51

Merged
mesh-admin merged 4 commits from feat/machine-network-health into main 2026-10-07 18:16:09 +00:00
Contributor

hq ADR 0241, to-be 48 §10 (Phase F), engine half.

  • internal/network: every 30 s, five parts — resolv.conf vs the uplink holder's declared file (writer named from header / backup / running client / link target), names through each listed resolver (mesh name A + AAAA must be NOERROR-empty per issue 262, public name A, within the file's own timeout, asked concurrently over raw UDP), tunnel handshake with the hub (wg latest-handshakes + allowed-ips, never dump), bus link, default route. Unhealthy on the 2nd failing look, healthy on the 1st passing. Reads only.
  • link.Health gains network; Queue.Linked().
  • Drill: TestDrill… run in a throwaway alpine container (rewrite as FortiClient does, write back) — passed; its statements are the controller's replay testdata.
  • Rollout: this first, then mesh-controller (which reads the field leniently).

check-here: merge-gate PASS (4 of 4 compose), repo-check PASS.

hq ADR 0241, to-be 48 §10 (Phase F), engine half. - internal/network: every 30 s, five parts — resolv.conf vs the uplink holder's declared file (writer named from header / backup / running client / link target), names through each listed resolver (mesh name A + AAAA must be NOERROR-empty per issue 262, public name A, within the file's own timeout, asked concurrently over raw UDP), tunnel handshake with the hub (wg latest-handshakes + allowed-ips, never dump), bus link, default route. Unhealthy on the 2nd failing look, healthy on the 1st passing. Reads only. - link.Health gains `network`; Queue.Linked(). - Drill: TestDrill… run in a throwaway alpine container (rewrite as FortiClient does, write back) — passed; its statements are the controller's replay testdata. - Rollout: this first, then mesh-controller (which reads the field leniently). check-here: merge-gate PASS (4 of 4 compose), repo-check PASS.
mesh-admin added 4 commits 2026-10-07 17:04:53 +00:00
A VPN client rewrote the laptop's resolver file and every mesh name failed
while each module read healthy: nothing asked the machine. The engine now
looks every 30 s at the resolver file the uplink holder declared (naming
the program that rewrote it), the names through each listed resolver
(NXDOMAIN for a mesh name's IPv6 address is a finding, issue 262), the
tunnel's handshake with the hub, the bus and the default route; a part is
unhealthy on its second failing look, and the statement carries it.
The judge's tests run against files and fakes; the drill runs it against a
real resolver file and real resolvers, rewritten as the VPN client does,
and records the statements the controller's replay raises and clears from.
The liveness loop's ticker drifts; a look skipped for a few milliseconds
would wait a whole further tick.
Hold the network statement's field names on the engine's side (hq ADR 0241)
mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery delivered
mesh/delivery-group group feat/machine-network-health closed: a member was closed before the group merged
f8ef2de91d
Author
Contributor

Delivery novox/mesh-host@f8ef2de91d03 — delivered since 2026-10-07T18:21:04Z

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host

Group feat/machine-network-health, in order:

Machines

  • mesh-host on ace: passed — healthy 3 times over 2m33s
  • mesh-host on the rest running it: sent

Transitions

  • 2026-10-07 17:05 (new) → proposed (announced): novox/mesh-host#51's head announced
  • 2026-10-07 17:07 proposed → checked (checked): the verdict names this commit
  • 2026-10-07 17:07 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-07 18:16 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-07 18:16 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
  • 2026-10-07 18:21 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-host@f8ef2de91d03` — **delivered** since 2026-10-07T18:21:04Z **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host **Group** `feat/machine-network-health`, in order: - novox/mesh-controller@b8bbf9c79fd8 before novox/mesh-host@f8ef2de91d03: built by - novox/mesh-host@f8ef2de91d03 before novox/mesh-controller@b8bbf9c79fd8: engine before controller **Machines** - mesh-host on ace: passed — healthy 3 times over 2m33s - mesh-host on the rest running it: sent **Transitions** - 2026-10-07 17:05 (new) → proposed (announced): novox/mesh-host#51's head announced - 2026-10-07 17:07 proposed → checked (checked): the verdict names this commit - 2026-10-07 17:07 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-07 18:16 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-07 18:16 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path - 2026-10-07 18:21 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Author
Contributor

Merge check at f8ef2de9

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
  • mesh/repo-check: PASS — its merge-check.sh passed

Change plan — builds mesh-host → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host

Run by the build seat on shanks as build-1791392711587036375 (builds --log build-1791392711587036375).

--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-07T17:03:39Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-07T17:03:39Z

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
--- its merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-host/cmd/mesh-bootstrap	1.012s
ok  	github.com/novox/mesh-host/cmd/mesh-host	1.377s
ok  	github.com/novox/mesh-host/examples	1.020s
ok  	github.com/novox/mesh-host/internal/apply	4.446s
ok  	github.com/novox/mesh-host/internal/bootstrap	1.615s
ok  	github.com/novox/mesh-host/internal/bundle	1.046s
ok  	github.com/novox/mesh-host/internal/declaration	1.089s
ok  	github.com/novox/mesh-host/internal/firewall	1.872s
ok  	github.com/novox/mesh-host/internal/identity	1.131s
ok  	github.com/novox/mesh-host/internal/image	1.038s
ok  	github.com/novox/mesh-host/internal/inventory	1.047s
ok  	github.com/novox/mesh-host/internal/link	10.363s
ok  	github.com/novox/mesh-host/internal/liveness	2.085s
ok  	github.com/novox/mesh-host/internal/network	1.061s
ok  	github.com/novox/mesh-host/internal/outward	1.053s
ok  	github.com/novox/mesh-host/internal/profile	1.507s
ok  	github.com/novox/mesh-host/internal/reachable	1.051s
ok  	github.com/novox/mesh-host/internal/store	1.232s
ok  	github.com/novox/mesh-host/internal/system	1.055s
ok  	github.com/novox/mesh-host/internal/tunnel	1.049s
ok  	github.com/novox/mesh-host/internal/upgrade	1.161s
ok  	github.com/novox/mesh-host/internal/witness	4.718s
ok  	github.com/novox/mesh-host/packaging	1.034s
ok  	github.com/novox/mesh-host/validate	1.045s
**Merge check** at `f8ef2de9` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Change plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host Run by the build seat on shanks as `build-1791392711587036375` (`builds --log build-1791392711587036375`). ``` --- the gate: mesh-host mesh-host: ok long-running resources without health: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-07T17:03:39Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-07T17:03:39Z machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): mesh-host --- its merge-check.sh (go toolchain) ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.012s ok github.com/novox/mesh-host/cmd/mesh-host 1.377s ok github.com/novox/mesh-host/examples 1.020s ok github.com/novox/mesh-host/internal/apply 4.446s ok github.com/novox/mesh-host/internal/bootstrap 1.615s ok github.com/novox/mesh-host/internal/bundle 1.046s ok github.com/novox/mesh-host/internal/declaration 1.089s ok github.com/novox/mesh-host/internal/firewall 1.872s ok github.com/novox/mesh-host/internal/identity 1.131s ok github.com/novox/mesh-host/internal/image 1.038s ok github.com/novox/mesh-host/internal/inventory 1.047s ok github.com/novox/mesh-host/internal/link 10.363s ok github.com/novox/mesh-host/internal/liveness 2.085s ok github.com/novox/mesh-host/internal/network 1.061s ok github.com/novox/mesh-host/internal/outward 1.053s ok github.com/novox/mesh-host/internal/profile 1.507s ok github.com/novox/mesh-host/internal/reachable 1.051s ok github.com/novox/mesh-host/internal/store 1.232s ok github.com/novox/mesh-host/internal/system 1.055s ok github.com/novox/mesh-host/internal/tunnel 1.049s ok github.com/novox/mesh-host/internal/upgrade 1.161s ok github.com/novox/mesh-host/internal/witness 4.718s ok github.com/novox/mesh-host/packaging 1.034s ok github.com/novox/mesh-host/validate 1.045s ```
mesh-admin merged commit fcca8d9ce8 into main 2026-10-07 18:16:09 +00:00
mesh-admin deleted branch feat/machine-network-health 2026-10-07 18:16:09 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-host#51