18 lines
1.2 KiB
Markdown
18 lines
1.2 KiB
Markdown
# Diagnosis — 2026-09-22
|
|
|
|
1. The control plane collects every placed machine's name and address for a resolution keyed by
|
|
the internal name (`homer.internal`), because that is the map every container is given as its
|
|
hosts. The facts that render the hosts file and the resolver's zones took the same map as bare
|
|
names and appended `.internal` to each — their unit tests fed them bare names and passed.
|
|
2. Fixed in the facts: a name is read as either form, and each machine is written once as
|
|
`<machine>.internal` with its bare name beside it. A test feeds both keyings and holds the files
|
|
equal, and holds the zones free of a doubled suffix.
|
|
|
|
**Located in:** the facts. Not a decision. Proven by the unit test and by the large mesh bed's name
|
|
tests, once its controller image is rebuilt from the fix.
|
|
|
|
*On review.* The first fix wrote the suffix a second time, in the facts, which is the shape that
|
|
produced the defect: two places composing one name. The control plane now hands the suffix it
|
|
composed the names with down to the facts, so an operator who chose another gets that one and
|
|
nothing appended. What remains unproven by a bed is a mesh with a suffix other than the default.
|