From a92e4bf121ee48a7553ce1bdc9ef952018ad44ce Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 1 Oct 2026 18:14:37 +0200 Subject: [PATCH] Issue 188: what the live fault was and how it was resolved --- .../00-report.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/04-ISSUES/188-a-refusal-inside-on-the-network-drops-a-machine-silently/00-report.md b/04-ISSUES/188-a-refusal-inside-on-the-network-drops-a-machine-silently/00-report.md index 7efa488..d85abc9 100644 --- a/04-ISSUES/188-a-refusal-inside-on-the-network-drops-a-machine-silently/00-report.md +++ b/04-ISSUES/188-a-refusal-inside-on-the-network-drops-a-machine-silently/00-report.md @@ -43,6 +43,11 @@ where it happens and discovered where it hurts. ## Resolved in the live mesh, 2026-10-01 -By hand: `pin novox acme-ca novox step-ca`, the provider the previous controller had in fact bound -the proxy to (read from its plan), after which the control node resolved, every seat read as held -and the roll-out proceeded. The design fault above stands. +The refusal itself was a fault of mesh-controller 195, already corrected on main by its author's +hotfix (196) when the control node was found refusing; the running controller was the one build in +between. Found by running the previous image and main's image as one-shots beside the running one +and reading which resolved. Resolved by pushing the control node from a one-shot of main's image, as +the recipe for a controller that cannot roll itself says. A pin naming the proxy's issuer +(`step-ca`, the one the previous plan had bound) was made first and kept; it changes nothing. The +design fault above stands and is fixed by mesh-controller PR `fix/a-machine-not-on-the-network-is-said`: +the dropped machine and the resolver's words are said where the drop happens.