GB-271: the peering's WireGuard interface does not hold the agreed peer and address¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-271 is printed by goatbuilder. The same text offline: goat explain GB-271 or goatbuilder explain GB-271.
What it means¶
Phase 11 writes the agreement's link values (the counterparty's public key, its allowed address and our link address) to the link's environment file, restarts goat-peering-wg@<interface>.service and reads the interface back with wg show <interface> allowed-ips and ip -4 addr show dev <interface>. The read-back did not find them, so the link the agreement describes is not up on this edge. The end of the message lists what the interface holds: each peer's public key and allowed addresses, then its addresses. No peer and no address is the interface as it is before phase 11.
Why it happens¶
- the link unit is still running with the environment it had before phase 11: the agreement's peer and address were written to the link's environment file, but goat-peering-wg@<interface>.service was not restarted to read them (a phase 11 cut off between writing the file and the restart, or run by a role from before the restart-on-read check)
- the unit was restarted and goat-peering-wg-link up stopped partway: its journal says where
- something other than this role changed the interface after the unit set it up (another peering's unit, or wg set by hand)
What to do¶
One line per step or alternative:
on the edge: sudo systemctl restart goat-peering-wg@<interface>.service, then sudo wg show <interface> and ip -4 addr show dev <interface>: the agreed peer and link address are there
if they are not: sudo journalctl -u goat-peering-wg@<interface>.service -n 50
goatbuilder federate <peering> --from 11
Read more¶
Exit code¶
goatbuilder exits with 1.