GB-181: a resource this peering needs is held by another peering on the same host¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-181 is printed by goatbuilder. The same text offline: goat explain GB-181 or goatbuilder explain GB-181.
What it means¶
Before a peering takes a resource on a shared host (a tunnel interface, a port, a link subnet, a certificate folder), goatbuilder reads every other peering's run journal in the same work root under <root>/.allocation.lock. One of them holds the same resource on the same host, or a journal there could not be read, so nothing was claimed and nothing changed.
Why it happens¶
- two peerings were given the same per-peering value (a pinned value in
peerings:or a hand-written group_vars file) - a journal in the work root is damaged, so the check cannot tell what it holds
What to do¶
One line per step or alternative:
give this peering a different value, or let allocation choose one, then make a new plan
read the other peering's journal named in the message: <root>/<peering>/state.json
Read more¶
Exit code¶
goatbuilder exits with 1.