GB-225: resources of the peering are still present after the back-out¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-225 is printed by goatbuilder. The same text offline: goat explain GB-225 or goatbuilder explain GB-225.
What it means¶
The survey run after the removal still finds resources of this peering, or the removal play stopped partway. Every step is idempotent: running the back-out again removes what is left and reports the rest as absent.
Why it happens¶
- a host became unreachable during the removal
- a unit or container would not stop
What to do¶
One line per step or alternative:
goatbuilder federate backout <partner>
Read more¶
Exit code¶
goatbuilder exits with 3.