Skip to content

GB-224: the core router was not restarted on the reviewed candidate

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

What it means

The core step installs only the candidate configuration whose digest the survey printed. The core's files changed since the survey (so the candidate's digest differs), more than one core router was found, or the restart failed. The org fragment kept beside it as <fragment>.before-backout-<partner> is the state before the step.

Why it happens

  • another change reached the core between the survey and the restart
  • several containers qualify as the core router

What to do

One line per step or alternative:

goatbuilder federate backout <partner> --dry-run, review the new candidate, then run it again
name the router with peering_backout_core_container or FED_ROUTER_CONTAINER

Read more

Exit code

goatbuilder exits with 3.