GB-232: a rendered deployment half needs a site value no declaration yields¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-232 is printed by goatbuilder. The same text offline: goat explain GB-232 or goatbuilder explain GB-232.
What it means¶
The peering declares deployment: rendered, so goatbuilder federate allocate renders the edge's and the core's deployment halves (peering-deployment.yml). Each required site value is taken from the group_vars of the environment's groups (environments[].groups) or all when one sets it, and is otherwise derived from the declaration that owns it: the core's address from peerings[].hosts.core or its line in the peering inventory, the core router's port from goat_zenoh_listen_port (group_vars, else the goat-zenoh role default), the images from the role defaults and ops/pins/fleet-pins.yaml, the core's certificate name from its name in the site inventory (ops/ansible/inventory/*.ini). One of them could be found in none of these places; the message names each place it read. Nothing is invented and nothing was written.
Why it happens¶
- the peering declares no hosts: and the peering inventory has no single host for its core group
- no role default and no fleet-pins component pins the image the message names
- the site values live in a group the environment does not name in environments[].groups
What to do¶
One line per step or alternative:
declare what the message names where it looked (peerings[].hosts, the core group's inventory line, the image pin)
or set the named variable once in the group_vars of one of the environment's groups
or declare deployment: hand on the peering and keep writing its deployment halves by hand
Read more¶
Exit code¶
goatbuilder exits with 2.