Skip to content

GB-129: a peering's offer would widen what federation.toml declares

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

What it means

federation.toml owns the release sets this party offers ([data] release). A peering's offer: may only narrow that list for one partner. It names a set federation.toml does not offer, is empty or malformed, or federation.toml cannot be read. Or the peering's federation.toml is hand-written (federation_toml: hand), whose [data] release phase 3 offers whole, and offer: is narrower than it; a peering whose federation.toml goatbuilder federate allocate generates gets the narrowed list. Nothing ran.

Why it happens

  • offer: names a set that is not in federation.toml's [data] release
  • offer: is narrower than the [data] release of a hand-written federation.toml (federation_toml: hand), which phase 3 offers whole
  • GOAT_PROFILE_DIR or GOAT_CONTEXT points at another goat context than the one phase 3 runs in

What to do

One line per step or alternative:

add the set to [data] release in federation.toml, the one owner of the offered sets, or remove it from offer:
declare federation_toml: rendered on the peering so goatbuilder federate allocate generates its federation.toml, or narrow [data] release in the hand-written file to what this partner receives, or remove offer:
goatbuilder validate (the offer's shape)

Read more

Exit code

goatbuilder exits with 2.