Skip to content

GB-067: a site's service presence is undeclared or contradicted

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

What it means

Every service the catalog lists must be declared present or absent for every governed site, by exactly one answer: a flag in the site's group_vars, the fleet pin table (an absent deviation), or the founder rule. The baseline ops/goatbuilder/endstate/baseline.txt lists the gaps that exist today and may only shrink: a new gap, or a baseline row that is no longer true, fails.

Why it happens

  • a new service in the catalog with no flag declared for a site
  • the fleet pin table renders a component the site's flag says it does not run (or the reverse)
  • a gap was closed and its baseline row was left behind

What to do

One line per step or alternative:

set the service's flag (its catalog `var:`) in ops/ansible/group_vars/<site>_hosts/vars.yml
add `absent: true` for the member in ops/pins/fleet-pins.yaml, then regenerate and re-sign the pins
delete the stale row from ops/goatbuilder/endstate/baseline.txt

Read more

Exit code

goatbuilder exits with 1.