GB-160: two peerings on one forwarder would share a value¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-160 is printed by goatbuilder. The same text offline: goat explain GB-160 or goatbuilder explain GB-160.
What it means¶
The peerings one forwarder relays must share no carrier interface, public port, carrier port or carrier address on it: the forwarder sends each packet by its port alone. Allocation keeps them apart across every environment the forwarder relays (by its endpoint); this refusal is the backstop for values that collide anyway.
Why it happens¶
- a hand edit of peering-values.yaml gives two relayed peerings one forwarder value
- a pin under values: (public_port, carrier_port, carrier_interface, carrier_subnet) repeats another peering's value
What to do¶
One line per step or alternative:
pin different public_port, carrier_port, carrier_interface and carrier_subnet values under one peering's values:
or give each environment its own forwarder (forwarder: group:)
Read more¶
Exit code¶
goatbuilder exits with 2.