GB-121: two peerings would share a value¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-121 is printed by goatbuilder. The same text offline: goat explain GB-121 or goatbuilder explain GB-121.
What it means¶
A per-peering value (an interface, a UDP or TCP port, a link subnet, a forwarder port, a certificate directory, an inventory name) is pinned on one peering and already held by another, by a pin or by the allocation record, or a partner is declared twice on one environment. Two peerings on one edge or core host cannot share one.
Why it happens¶
- two peerings pin the same value under values:
- a pin takes a value the allocation record holds for another peering
- the same partner is declared twice on one environment
What to do¶
One line per step or alternative:
pin a different value on one of the two peerings, or remove the pin and run goatbuilder federate allocate to have one allocated
goatbuilder validate (every collision, each naming both peerings)
Read more¶
Exit code¶
goatbuilder exits with 2.