Skip to content

GB-113: no core router to measure on the core host

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

What it means

Phase 3 measures the core router's image and version on the core host. It takes the router the operator names with --router-container, else the name the deployment's variables give (zenoh_stack, or site_id with the goat-zenoh role's default, as <zenoh_stack>-router), else the one running core router discovery finds. That router was not running, could not be read, or several candidates were found.

Why it happens

  • the declared router is not running on the core host, or the variables give a different name than the one deployed
  • nothing declares the router and no running container carries org.goat.component=zenoh-core or a standard name
  • several core routers run on the host

What to do

One line per step or alternative:

goatbuilder federate init --router-container <name> (name it by hand)
FED_ROUTER_CONTAINER=<name> goatbuilder federate <partner> (the one command passes it to phase 3 as --router-container)
set zenoh_stack or site_id for the core host in the deployment's group_vars or host_vars
ssh <user>@<core> sudo docker ps --format '{{.Names}} {{.Label "org.goat.component"}}' (what is running)

Read more

Exit code

goatbuilder exits with 1.