Skip to content

GB-124: the peering allocation record cannot be used

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

What it means

ops/goatbuilder/peering-values.yaml, the record of the per-peering values goatbuilder federate allocate chose, is unreadable, has another schema, holds a malformed value, gives two peerings one value, or records a port the edge host already holds. Allocation reads it so a re-run never moves a value; it will not guess around a broken one.

Why it happens

  • a hand edit or a merge conflict in the record
  • a record from a newer goatbuilder

What to do

One line per step or alternative:

git log -p ops/goatbuilder/peering-values.yaml (restore it from its history)
remove the broken entry and run goatbuilder federate allocate to allocate it afresh (that peering's values may change)

Read more

Exit code

goatbuilder exits with 2.