GB-270: a backed-out partner's store was kept because the router does not yet run without it¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-270 is printed by goatbuilder. The same text offline: goat explain GB-270 or goatbuilder explain GB-270.
What it means¶
On a goat-zenoh role core, the back-out took the partner out of zenoh_sovereign_peerings, ran the role's play to restart the router without the partner's store, then ran ops/ansible/zenoh-drop-partner-store.yml, which deletes <storage path>/sovereign_from_<partner> only after the router runs without it (ADR 1234). One of the two plays did not get there: the partner is still declared, the live configuration still names the store, the router is not running, or it started before that configuration was written. The store was kept, and the back-out put the partner's entry back in peerings.yml, so running it again repeats the step.
Why it happens¶
- the role's play failed before or during the router's restart
- the router did not restart after the configuration without the store was written
- the partner is declared in another of the core router group's files
What to do¶
One line per step or alternative:
read the role play's output above, then goatbuilder federate backout <partner>
Read more¶
Exit code¶
goatbuilder exits with 3.