The bed enforces one-push provisioning, a patient runtime, and a broker restart (057/058/063) #35

2026-09-18T00:53:45Z

jschoubben commented

2026-09-18 00:53:45 +00:00

The built-store-cross-node bed gains the enforcement for three fixes it now gates:

057: the provider's workaround re-push is removed — pushing the consumer's node must cascade to the provider, and the vhost assertion is what says so.
058: the joined consumer must show a container-runtime restart count of zero — a runtime whose broker is not up yet waits in-process rather than crash-looping.
063: after adoption the broker is restarted deliberately, and the joined node must still reach it across the overlay — proving the forward rule, not a surviving conntrack entry, carries the connection.

Green fresh on run 16 against mesh-controller 97c076e, mesh-tools patient-runtime, mesh-catalog catalog-builds.

The built-store-cross-node bed gains the enforcement for three fixes it now gates: - **057**: the provider's workaround re-push is removed — pushing the consumer's node must cascade to the provider, and the vhost assertion is what says so. - **058**: the joined consumer must show a container-runtime restart count of zero — a runtime whose broker is not up yet waits in-process rather than crash-looping. - **063**: after adoption the broker is restarted deliberately, and the joined node must still reach it across the overlay — proving the forward rule, not a surviving conntrack entry, carries the connection. Green fresh on run 16 against mesh-controller 97c076e, mesh-tools patient-runtime, mesh-catalog catalog-builds.

jschoubben added 2 commits 2026-09-18 00:53:46 +00:00

The bed enforces one-push provisioning and a patient runtime (057/058) 38a7180b8b

The provider's workaround re-push is gone: pushing the consumer's node
must cascade to the provider (issue 057), and the vhost assertion is
what says so. The joined consumer must also show zero container-runtime
restarts (issue 058): a runtime whose broker is not up yet waits for it
in-process, so overlay-after-container ordering produces no churn.

The bed restarts the broker and reconnects across the overlay (issue 063) 68133c2c56

A broker that is reachable only until its conntrack entry drops passes
every test written before it restarts. The bed now restarts mesh-broker
after adoption and asserts the joined node can still reach 5671 — the
forward rule, not a surviving entry, carrying the connection.

jschoubben merged commit 27665501dc into main

2026-09-20 10:53:19 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-lab#35