Skip to content

GB-128: a federate run disagrees with the peering's allocated values

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

What it means

The allocation record holds this peering, and the run's working directory, edge group or core group is not the allocated one. Phase 8 would mint certificates where the edge does not read them, or the plays would run on another peering's hosts. Nothing ran.

Why it happens

  • --work or FED_WORK names a directory whose pki is not the allocated cert_dir
  • --edge-group names another group than the allocated edge_group
  • a partner declared on a second environment, or a core_group pin: the driver runs the republisher on <with>_core and does not read the allocated core group yet

What to do

One line per step or alternative:

goatbuilder federate allocate --dry-run (the allocated values)
pass the --work and --edge-group the refusal names, or pin cert_dir and edge_group under the peering's values: to what you pass

Read more

Exit code

goatbuilder exits with 2.