Skip to content

GB-231: the hand-written peering inventory puts one name in two peering groups

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

What it means

No peering declares hosts:, so ops/ansible/inventory/peering-edges.ini is hand-written, and it puts one inventory name in two peering groups. Ansible merges the group_vars of every group a name is in, so each peering would read the other's rendered values. Nothing was written.

Why it happens

  • one machine listed under the same name for two peerings

What to do

One line per step or alternative:

give each peering its own inventory name for the machine, with the same ansible_host
declare hosts: on every peering and let goatbuilder federate allocate render the inventory

Read more

Exit code

goatbuilder exits with 2.