Skip to content

GB-222: the back-out survey did not complete

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

What it means

ops/ansible/peering-backout.yml failed before every host of the peering answered, or no host answered while the working folder holds the peering's agreement, so there is no plan to show and nothing was changed.

Why it happens

  • a host of <partner>_edge, <partner>_core or peering_forwarders is unreachable
  • neither ops/ansible/inventory/peering-edges.ini nor a per-peering peering-<edge group>.ini names the peering's hosts, so the play matched no host

What to do

One line per step or alternative:

read the play output above; fix reachability or the inventory, then goatbuilder federate backout <partner> --dry-run

Read more

Exit code

goatbuilder exits with 1.