GB-203: two peerings would bind the same value on one machine¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-203 is printed by goatbuilder. The same text offline: goat explain GB-203 or goatbuilder explain GB-203.
What it means¶
this peering and another declared peering would bind the same WireGuard interface, tunnel UDP port or republisher metrics port, or overlapping link subnets, on the same machine (by inventory address), so one would break the other.
Why it happens¶
- two environments, or two hand-named inventory groups, place their edges or cores on one machine
- a value was pinned or declared by hand without looking at the other peerings on that machine
What to do¶
One line per step or alternative:
give this peering another value in its edge or core group's vars (or its allocation pin), then goatbuilder federate plan <partner>
Read more¶
Exit code¶
goatbuilder exits with 1.