Raise genesis on the bus the mesh runs on, from one bundle (issue 146, ADR 0331) #96

Merged

mesh-admin merged 2 commits from fix/146-genesis-on-the-bus into main 2026-10-12 21:11:52 +00:00

Conversation 4 Commits 2 Files Changed 22

+801 -570

2 Commits

Author	SHA1	Message	Date
jochen	cb55a46400	Place the bus's users again on a re-run until the bus is adopted (hq issue 146, review 102) ... A re-run's apply writes the bundle's one-entry user list over the list placed at enrolment, and an enrolled machine skipped placing it: enrolled was taken for adopted, against ADR 0331 §5. Until the controller knows the nats module, the installer places the composed list again. Also drop the previous broker's AMQP and management ports, which nothing raises any more, and say why the bus always carries a ports setting.	2026-10-12 23:06:33 +02:00
jochen	37947ca4ee	Raise genesis on the bus the mesh runs on, from one bundle (hq issue 146, ADR 0331) ... The installer could not raise a first node: the old bundle's control plane had no MESH_BUS_NATS and crash-looped, and the NATS bundle was refused because rootsecrets only knew the previous broker's guest:guest@ template. One bundle now, the NATS one. rootsecrets makes the controller's bus account and puts it in both placeholders (the address and the bcrypt hash in the carried user list), kept with its hash so a re-run writes the same bundle. Preflight refuses a template naming no bus connection it knows, naming the placeholder, instead of waiting out the verify step. The broker step adopts the bus as the nats module and refuses, by name, a catalogue without it or a server that is not the foundation's container.	2026-10-12 22:49:49 +02:00