GB-163: a forwarded peering has no allocated values yet¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-163 is printed by goatbuilder. The same text offline: goat explain GB-163 or goatbuilder explain GB-163.
What it means¶
The peering declares forwarder:, so phase 2 runs the forwarder play and copies the carrier keys, and both read the group_vars goatbuilder federate allocate renders from the allocation record. The record does not hold this peering, so those files do not exist. Nothing ran.
Why it happens¶
- forwarder: was added to the peering and goatbuilder federate allocate was not run since
What to do¶
One line per step or alternative:
goatbuilder federate allocate (then review and commit what it writes)
Read more¶
Exit code¶
goatbuilder exits with 2.