GB-223: the slot recheck did not allow the core router restart¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-223 is printed by goatbuilder. The same text offline: goat explain GB-223 or goatbuilder explain GB-223.
What it means¶
Immediately before the core router restarts without this peering's admission, the committed slot list is checked against the registry, as the admission path does. It drifted, the registry could not be read, or no registry was named, so the core was not restarted. The edge side of the peering is already removed and the partner has no path to the core.
Why it happens¶
- slots were minted or revoked since the list was committed
- FED_SLOT_DB (or FED_SLOT_REGISTRY_STORE=postgres with FED_SLOT_PG_SSH) is not set for a deployment with lazy slot storage
What to do¶
One line per step or alternative:
regenerate and commit the slot list (ops/scripts/sync-slot-anchors.py --env <env> ...), then goatbuilder federate backout <partner>
Read more¶
Exit code¶
goatbuilder exits with 3.