GB-253: a host's back-out survey answered for another peering¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-253 is printed by goatbuilder. The same text offline: goat explain GB-253 or goatbuilder explain GB-253.
What it means¶
Back-out surveys each host of the peering read-only before it plans what to remove, and every answer names the peering it read. One host's answer names another peering, so nothing is planned from it: removing that peering's resources would be removing someone else's.
Why it happens¶
- the inventory groups of two peerings share a host name
- the survey ran with another peering's working directory
What to do¶
One line per step or alternative:
goatbuilder federate backout <partner> --plan (survey again with this peering's own work directory)
give each peering its own inventory name for the machine (allocate does)
Read more¶
Exit code¶
goatbuilder exits with 2.