Skip to content

GB-185: the partner named to federate status is not a declared peering

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

What it means

goatbuilder federate status <partner> reads a peering declared in goatbuilder.yaml peerings: (on --env, when given). The name given is not one of them, so nothing was read.

Why it happens

  • the name is misspelled, or the peering is declared under another environment's config
  • the peering has not been declared yet

What to do

One line per step or alternative:

goatbuilder federate status (every declared peering)
declare it under peerings: in goatbuilder.yaml first (C1)

Read more

Exit code

goatbuilder exits with 1.