Issue 145: a machine reads healthy while its modules cannot reach each other #179

2026-09-29T10:37:09Z

mesh-admin commented

2026-09-29 10:37:09 +00:00

No description provided.

mesh-admin added 1 commit 2026-09-29 10:37:10 +00:00

Issue 145: a machine reads healthy while its modules cannot reach each other 492ac7be18

Converging the control node closed every path by which a module reached another by
the machine's own name, and it ran for eleven hours while the mesh answered 'all
doing what they were told, all heard from, running what the mesh would send them,
and every module current with its source'.

6,154 database failures in one module's log, beginning at the minute of the flip.
The service accepted TCP and never answered HTTP. Every check the mesh makes
passed, because every check the mesh makes is about the relationship between the
mesh and a machine — applied, current, containers running. None asks whether a
module can reach what it requires, though the mesh composes every grant and so
knows exactly who requires what.

The filter fault is fixed. The eleven hours are the measurement, not the bug.

Also records on 144 that 'more closed than the mesh believes' was harmless only
for what is reached from outside, and an outage for what is reached from within.

mesh-admin merged commit f65664640a into main

2026-09-29 10:37:10 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#179