GB-234: the site inventory does not name one edge and one core for a peering without hosts¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-234 is printed by goatbuilder. The same text offline: goat explain GB-234 or goatbuilder explain GB-234.
What it means¶
A peering declares no hosts:, so goatbuilder federate allocate takes its machines from the site inventory (the environment's inventory:, else ops/ansible/inventory/*.ini but the peering-*.ini files): the group of the peering's edge_class and of the site's other class, each named as the class, <site><class>, <environment><class> or <environment><site><class>. More than one file names them, a class has no machine or several, or the two machines are reached as different users. The message names the candidates and where it looked. Nothing was written.
Why it happens¶
- two inventory files define the site's class groups
- a class group lists several machines, or the edge class group lists none
- the edge and the core have different ansible_user values
What to do¶
One line per step or alternative:
declare hosts: {edge: <address>, core: <address>, user: <user>} on the peering
declare the environment's inventory: so only that file is read
make the site inventory name one machine per class
Read more¶
Exit code¶
goatbuilder exits with 2.