GB-280: a joining site has no mesh DNS zone to serve¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-280 is printed by goatbuilder. The same text offline: goat explain GB-280 or goatbuilder explain GB-280.
What it means¶
join-node deploys a mesh DNS replica on a joining site's core node, so the site still resolves the goatnet's names when it is cut off from its founder (ADR 1235). The replica serves the goatnet's generated zone, an ops/dns/<dir>/mesh-hosts whose records carry the site's site_dns_zone (the founder's when the site declares none). No such file was found, or neither site declares site_dns_zone, so the plan was refused before any phase ran.
Why it happens¶
- the goatnet's zone was never generated or committed (ops/dns/generate-mesh-hosts.py)
- neither the joining site's nor the founder's group_vars declare site_dns_zone
What to do¶
One line per step or alternative:
python3 ops/dns/generate-mesh-hosts.py, or --init <site_id> for a zone that has no file yet, then commit ops/dns/<dir>/mesh-hosts
declare site_dns_zone in group_vars/<site>_hosts/vars.yml
Read more¶
Exit code¶
goatbuilder exits with 1.