Skip to content

GB-235: a named allocate would change another peering's inventory lines

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

What it means

Every peering declares hosts:, so ops/ansible/inventory/peering-edges.ini is the whole generated peering inventory. goatbuilder federate allocate <peering> renders the named peering's groups into it and leaves every other line as it was; this run would change or drop a section of another peering (its hosts were changed in goatbuilder.yaml since the last allocate, or it is declared but not yet recorded). Nothing was written.

Why it happens

  • another peering's hosts: changed in goatbuilder.yaml since the inventory was last rendered
  • a peering in the generated inventory is declared but has no entry in the allocation record

What to do

One line per step or alternative:

goatbuilder federate allocate (every declared peering; review and commit what it changes)

Read more

Exit code

goatbuilder exits with 2.