Issues 094 and 095, both found in the first module's cutover #83

2026-09-22T23:57:42Z

jschoubben commented

2026-09-22 23:57:42 +00:00

Two bugs the first real migration of a service turned up.

094 — a port published as the machine side of a mapping cannot be moved, and trying blocks every push. A module that maps a machine port to a different port inside its container — the common shape when the software's own port collides with something the machine runs — cannot have that port moved by a node setting. The check collects only the container's inner port, so it refuses the very port the module publishes; naming the inner port is accepted and never consulted, because the lookup goes by what the module says it listens on. Worse, while that setting exists, composition fails and the node cannot be pushed to at all. The same blind spot seems to stop an opening being derived for such a port on an adopted node.

095 — a module assigned after genesis has no broker account. Its own-secret named broker is minted as a random value where the sidecar expects an account, so the service runs and its sidecar crash-loops. Issuing the account explicitly fixes it. Genesis does that for the foundation's own modules only, and nothing says the next module needs the same act — which every migrated module will.

Both are located; a fix for 094 is being written.

Two bugs the first real migration of a service turned up. **094 — a port published as the machine side of a mapping cannot be moved, and trying blocks every push.** A module that maps a machine port to a different port inside its container — the common shape when the software's own port collides with something the machine runs — cannot have that port moved by a node setting. The check collects only the container's inner port, so it refuses the very port the module publishes; naming the inner port is accepted and never consulted, because the lookup goes by what the module says it listens on. Worse, while that setting exists, composition fails and **the node cannot be pushed to at all**. The same blind spot seems to stop an opening being derived for such a port on an adopted node. **095 — a module assigned after genesis has no broker account.** Its own-secret named `broker` is minted as a random value where the sidecar expects an account, so the service runs and its sidecar crash-loops. Issuing the account explicitly fixes it. Genesis does that for the foundation's own modules only, and nothing says the next module needs the same act — which every migrated module will. Both are located; a fix for 094 is being written.

jschoubben added 1 commit 2026-09-22 23:57:43 +00:00

Issues 094 and 095, both found in the first module's cutover 515cb8adc1

jschoubben merged commit 1b8e5043ee into main

2026-09-22 23:57:49 +00:00

jschoubben deleted branch issues/094-095-from-the-first-cutover

2026-09-22 23:57:49 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#83