GB-110: the inventory does not name a federation host phase 3 can reach¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-110 is printed by goatbuilder. The same text offline: goat explain GB-110 or goatbuilder explain GB-110.
What it means¶
federate phase 3 measures the edge and the core from this machine, reaching each host the way the peering plays do: the host in the edge group and the host in the core group of inventory/peering-edges.ini, with its address, user, port, key and SSH options. The inventory could not be read, the group has no host or several, or the host uses a connection phase 3 does not use.
Why it happens¶
- ansible-inventory is not installed here, or the inventory does not parse
- the edge group (<partner>_edge) or the core group (<partner>_core) is empty or missing in inventory/peering-edges.ini
- the group has several hosts and none was named
- the host uses an ansible_connection other than ssh or local
What to do¶
One line per step or alternative:
cd ops/ansible && ansible-inventory -i inventory/peering-edges.ini --playbook-dir . --graph (what the plays see)
add the host to the group, or name it: goatbuilder federate init --edge-host <host> --core-host <host>
Read more¶
Exit code¶
goatbuilder exits with 1.