Issue 080: a cache grant let the consumer flush the server; 079: the names follow the resolver's rule for the private network

This commit is contained in:
2026-09-22 01:39:29 +02:00
parent e31e077fc8
commit f760bf632c
3 changed files with 45 additions and 0 deletions
@@ -15,3 +15,10 @@ tests, once its controller image is rebuilt from the fix.
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.
*Later.* With the suffix right, the large bed's name test asked the second half of its question:
a machine that leaves the private network must not be answered for. The names were every placed
machine with an address, while the resolver's "on the private network" is a machine that also
runs the module that puts it there. The names follow the resolver's rule now — one predicate,
used by both — held by a controller test that unassigns one machine's networking and reads the
names back.