From 42550dbe43b74fa96b27bdee372910c3b64f8492 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 27 Sep 2026 21:13:13 +0200 Subject: [PATCH] lavinmq keeps mesh-broker until something else can take it MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Taking the claim off made the seat unheld, and the controller dereferences that seat to find its own bus (to-be 26, "the one exception is the controller itself"). Unheld, the composed address fell back to a default port nothing serves, and the control plane crash-looped: "cannot reach the broker named in MESH_BROKER_AMQP: dial tcp 127.0.0.1:5672". The broker itself never stopped — it is healthy on the port the mesh actually assigned it. lavinmq becoming an ordinary provider is right, and it is still a provider of amqp here. What was wrong is the order: the seat has to pass from one holder to the next, and it cannot be empty in between, because the thing that reads it is the thing that would have to fix it. --- modules/lavinmq/module.json | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/modules/lavinmq/module.json b/modules/lavinmq/module.json index 31f76e4..f78368a 100644 --- a/modules/lavinmq/module.json +++ b/modules/lavinmq/module.json @@ -7,6 +7,12 @@ "scope": "mesh" } ], + "claims": [ + { + "name": "mesh-broker", + "scope": "mesh" + } + ], "capabilities": [ "container-runtime" ],