Issue 188: a refusal inside "who is on the network" drops a machine silently #263

2026-10-01T16:15:18Z

mesh-admin commented

2026-10-01 16:15:18 +00:00

This evening's forty minutes: a controller build refused the control node (two issuers of one provision, since hotfixed by its author), and because the network filter skips a machine whose resolution refuses, every symptom pointed elsewhere — a ${machine:at} placeholder, every seat unheld, builds refused for want of the git seat, the roll-out refused. Located in onTheNetwork; the fix (say the dropped machine and the resolver's words) is on a controller branch. Checks pass.

This evening's forty minutes: a controller build refused the control node (two issuers of one provision, since hotfixed by its author), and because the network filter skips a machine whose resolution refuses, every symptom pointed elsewhere — a `${machine:at}` placeholder, every seat unheld, builds refused for want of the git seat, the roll-out refused. Located in `onTheNetwork`; the fix (say the dropped machine and the resolver's words) is on a controller branch. Checks pass.

mesh-admin added 2 commits 2026-10-01 16:15:19 +00:00

Issue 188: a refusal inside on-the-network drops a machine silently 187442ec7b

Issue 188: what the live fault was and how it was resolved a92e4bf121

jschoubben added 1 commit 2026-10-01 16:22:20 +00:00

Issue 188: the second fault beneath the first, and its fix 606fbb7add

mesh-admin merged commit 0278766dfb into main

2026-10-01 16:22:51 +00:00

mesh-admin deleted branch issue/188-a-refusal-inside-on-the-network-drops-a-machine-silently

2026-10-01 16:22:51 +00:00

Sign in to join this conversation.