Every machine was named twice over; only a machine on the private network is named (issue 079) #41

2026-09-21T23:55:40Z

jschoubben commented

2026-09-21 23:55:40 +00:00

The hosts-file and resolver-zones facts appended .internal to names the control plane had already suffixed, writing anchor.internal.internal on every machine. The facts now take the suffix the control plane composed the names with (Rendering.Suffix, from overlay.Suffix()), so it is written once, whatever the operator chose. The test fixture is keyed as production keys it; a test holds both keyings to the same files and an operator's own suffix to itself.
The names follow the resolver's rule for "on the private network": a machine that is placed but does not run the module that puts it there is not named (a name resolving to an address that does not answer hangs). One predicate, onTheNetwork, for both; a controller test unassigns one machine's networking and reads the names back.

Found by running the large mesh bed end to end. go test ./... with the test store passes. Proof: mesh.test.ts 21/21 with the controller image rebuilt from 6a64aba. Companion MRs on multiple-fixes: mesh-catalog, mesh-lab, hq.

- The hosts-file and resolver-zones facts appended `.internal` to names the control plane had already suffixed, writing `anchor.internal.internal` on every machine. The facts now take the suffix the control plane composed the names with (`Rendering.Suffix`, from `overlay.Suffix()`), so it is written once, whatever the operator chose. The test fixture is keyed as production keys it; a test holds both keyings to the same files and an operator's own suffix to itself. - The names follow the resolver's rule for "on the private network": a machine that is placed but does not run the module that puts it there is not named (a name resolving to an address that does not answer hangs). One predicate, `onTheNetwork`, for both; a controller test unassigns one machine's networking and reads the names back. Found by running the large mesh bed end to end. `go test ./...` with the test store passes. Proof: mesh.test.ts 21/21 with the controller image rebuilt from 6a64aba. Companion MRs on `multiple-fixes`: mesh-catalog, mesh-lab, hq.

jschoubben added 3 commits 2026-09-21 23:55:40 +00:00

A machine's names are not suffixed twice: the facts take the internal names the control plane hands them (novox/hq issue 079) b529c49cff

The facts write the suffix the control plane composed the names with, handed down rather than written twice (review of issue 079); the fixture is keyed as production keys it 8152665298

Only a machine on the private network is named: the names follow the resolver's rule, one predicate for both (novox/hq issue 079) 6a64aba506

jschoubben added 1 commit 2026-09-22 00:04:30 +00:00

One predicate for the private network: the filter's accept set is the set the names and the resolver mean; the catalogue is read once for the three mesh-wide questions 5150c0a0f8

jschoubben merged commit ff26ea959d into main

2026-09-22 00:19:14 +00:00

jschoubben deleted branch multiple-fixes

2026-09-22 00:19:14 +00:00

Sign in to join this conversation.