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

Merged

jschoubben merged 2 commits from bed/one-push-and-a-patient-runtime into main

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

Author	SHA1	Message	Date
jschoubben	68133c2c56	The bed restarts the broker and reconnects across the overlay (issue 063) 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.	2026-09-18 02:21:48 +02:00
jschoubben	38a7180b8b	The bed enforces one-push provisioning and a patient runtime (057/058) 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.	2026-09-18 02:07:59 +02:00

Author

SHA1

Message

Date

jschoubben

68133c2c56

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

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.

2026-09-18 02:21:48 +02:00

jschoubben

38a7180b8b

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

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.

2026-09-18 02:07:59 +02:00