Skip to content

GB-134: the committed slot list differs from the slot registry

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

What it means

ops/scripts/sync-slot-anchors.py --check found live slots with no declared store or declared stores for slots that are not live. A core router restarted on this list drops or misses receive stores. Slots minted between the fix and the restart drift it again, so the restart step runs this check once more.

Why it happens

  • slots were minted or revoked since the list was last regenerated and committed
  • the list was regenerated, and a slot was minted before the core router restarted

What to do

One line per step or alternative:

python3 ops/scripts/sync-slot-anchors.py --env <goatnet> --db <registry.db> (writes the list; commit it)
python3 ops/federation/standup/preflight.py <partner> --work <dir> --only slot-anchors (re-check just before the restart)

Read more

Exit code

goatbuilder exits with 1.