Skip to content

GB-125: a peering file exists that goatbuilder did not generate

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

What it means

goatbuilder federate allocate writes the peering inventory and each peering's peering-values.yml. It never overwrites a file it did not generate (its first line says who did), and never renders a variable a hand-written file already sets for the same hosts (the group, its parent peering group, or the host_vars of its inventory names), because Ansible's file order would then pick the value. Nothing was written.

Why it happens

  • ops/ansible/inventory/peering-edges.ini or a peering-values.yml was written by hand before the values were allocated
  • a hand-written group_vars or host_vars file sets a variable allocate renders (a listen port, a certificate path)

What to do

One line per step or alternative:

move its values into goatbuilder.yaml (pins under the peering's values:, addresses under hosts:), remove the file, and run goatbuilder federate allocate again

Read more

Exit code

goatbuilder exits with 2.