Skip to content

GB-137: the core router's configuration could not be read

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

What it means

preflight found the core router but could not read its configuration, so the receive stores were not checked. Reported SKIP, never PASS; FED_PREFLIGHT_STRICT=1 refuses on it.

Why it happens

  • the core router reads its configuration from another path than /etc/zenoh/config.json5
  • the account behind FED_ROUTER_DOCKER_HOST may list containers but not exec in them

What to do

One line per step or alternative:

export FED_CORE_CONFIG_PATH=<path inside the core container>
inspect the core's storages through its own approved workflow

Read more

Exit code

goatbuilder exits with 1.