GB-227: the core still admits the partner through its own configuration¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-227 is printed by goatbuilder. The same text offline: goat explain GB-227 or goatbuilder explain GB-227.
What it means¶
The core router was configured by roles/goat-zenoh from zenoh_sovereign_peerings, which declares the partner's subject and grants as sovereign-<partner> ids. The back-out takes the partner's entry out of group_vars/<core router group>/peerings.yml, the file admission writes it into, and runs the role's play, which restarts the router without the partner's store and then deletes that store whole (ADR 1234). After the back-out the core still declares the partner: the entry is in a file admission does not write, the back-out could not rewrite peerings.yml (GB-237), the core was admitted through the deployment's own route (FED_CORE_*), or the role's play failed. The partner has no edge left to reach the core through.
Why it happens¶
- the core admits the peering from a zenoh_sovereign_peerings entry the back-out did not write, or could not take out
- the role's play failed after the entry was taken out, and the entry was put back
What to do¶
One line per step or alternative:
remove the partner's entry from zenoh_sovereign_peerings by review where it is declared and run the core play (a router restart); the role then reports sovereign_from_<partner> in .undeclared-stores
after a failed play: read its output, then goatbuilder federate backout <partner> again
Read more¶
Exit code¶
goatbuilder exits with 3.