Skip to content

GB-126: a peering's inventory group is defined twice

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

What it means

Not every peering declares hosts:, so ops/ansible/inventory/peering-edges.ini stays hand-written and each peering that declares hosts: gets its own rendered inventory file (inventory/peering-<edge_group>.ini), which the driver reads beside it. That peering's group is also defined in the hand-written inventory, so the plays would see it twice. Nothing was written.

Why it happens

  • hosts: added to a peering whose group is still in the hand-written peering-edges.ini

What to do

One line per step or alternative:

remove that peering's groups from ops/ansible/inventory/peering-edges.ini
or remove hosts: from the peering and keep its groups in the hand-written inventory

Read more

Exit code

goatbuilder exits with 2.