GB-293: the back-out cannot tell what our core router's leaf held before this peering¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-293 is printed by goatbuilder. The same text offline: goat explain GB-293 or goatbuilder explain GB-293.
What it means¶
Our core router's leaf (its certificate and key) holds the leaf this peering's admission placed, and no admission run in the peering's working folder recorded what was there before (both peerings admitted by hand, say), so the back-out can neither put it back nor remove it. No other peering is set up from this machine (no working folder beside this one holds an agreement); when one is, the leaf is kept for it and the back-out goes on. Nothing was changed on any host.
Why it happens¶
- the leaf was placed by hand, not by goatbuilder federate admission
- the admission folder of the peering's working folder was removed or moved
What to do¶
One line per step or alternative:
read the unknown core leaf lines of goatbuilder federate backout <partner> --dry-run; put back what each path held before this peering, or remove it when nothing did, then run the back-out again
Read more¶
Exit code¶
goatbuilder exits with 1.