Skip to content

GB-221: the back-out found a resource it cannot show is this peering's alone

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

What it means

The read-only survey found a resource under this peering's names that another peering holds (a WireGuard interface whose state file or peer names another partner, a carrier another peering's state names), or a core configuration it cannot prove changes by this peering alone (the live file is not seed + org fragment, partner ids overlap, a policy mixes partners). Nothing was changed on any host.

Why it happens

  • two peerings were given the same interface, carrier or stack name in their group values
  • the core's live configuration was edited by hand after the last assemble
  • the core keeps no seed/org split (slot-pool mode), so the admission cannot be located

What to do

One line per step or alternative:

read the REFUSED lines of goatbuilder federate backout <partner> --dry-run; give each peering its own names, or reconcile the core's live file with its seed and org fragment

Read more

Exit code

goatbuilder exits with 1.