Skip to content

GB-135: the slot registry could not be read

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

What it means

sync-slot-anchors.py exited 2: the registry was unreadable, or it reported zero live slots. That is not a verdict on drift, and the check is not passed.

Why it happens

  • FED_SLOT_DB names a file that is not the portal registry, or it cannot be opened read-only
  • the management host named by FED_SLOT_PG_SSH is unreachable, or its portal database container differs

What to do

One line per step or alternative:

check FED_SLOT_DB, or FED_SLOT_REGISTRY_STORE=postgres with FED_SLOT_PG_SSH (portal_store in group_vars/<goatnet>_hosts says which)

Read more

Exit code

goatbuilder exits with 1.