Skip to content

GB-230: allocate would move a peering that already runs

Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-230 is printed by goatbuilder. The same text offline: goat explain GB-230 or goatbuilder explain GB-230.

What it means

A peering the allocation record does not hold already runs from hand-written configuration (its edge group has hand group_vars, or the hand inventory names it), and the values allocation chose differ from the ones it runs on (its hand group_vars, else the role defaults). Rendering them would move its tunnel or ports on the next phase 2. Nothing was written.

Why it happens

  • goatbuilder federate allocate run for the first time in a deployment with a peering set up by hand

What to do

One line per step or alternative:

adopt it as it runs: pin the values the refusal names under the peering's values: in goatbuilder.yaml (a pin on 51820 needs that environment's peering_edge_reserved_udp to allow it)
move it on purpose: FED_ALLOCATE_MOVE=<with> goatbuilder federate allocate --yes

Read more

Exit code

goatbuilder exits with 2.