GB-076: the rollout is not cleanly reversible or not ready¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-076 is printed by goatbuilder. The same text offline: goat explain GB-076 or goatbuilder explain GB-076.
What it means¶
preflight graded the three rollout facts (State, Rollback, Scope) and the readiness half, and at least one row is not a clean, declared, validated pass. An undeclared fact fails closed (stateful, rollback none) and reads not-clean on purpose, so the gap is visible rather than guessed green; an UNKNOWN is not a pass either. The facts are still printed — a stateful, restore-required rollout is a valid state to deploy knowingly, with --ack.
Why it happens¶
- a fact is undeclared, so it failed closed (declare owns_state / rollback / restore_from / coupled_with in ops/pins/fleet-pins.yaml)
- a declared rollback contradicts the artifact type (pin-revert over a data/cert/forward-only component, or one flagged reversible false)
- a readiness check failed — the ref is not pullable, pins --check found drift, the secrets gate is unsatisfied, the checkout is stale, or the end state is not declared
- a validation could not answer (UNKNOWN) — no registry probe, or no reachable ledger for the rollback --dry-run
What to do¶
One line per step or alternative:
goatbuilder preflight <component> --env <goatnet> (each not-ok row with its reason)
declare the component's rollout facts in ops/pins/fleet-pins.yaml (owns_state, rollback, restore_from, coupled_with)
goatbuilder deploy --component <c> --env <goatnet> --ack "<you>" (deploy knowingly; the accepted risk is recorded)
Read more¶
Exit code¶
goatbuilder exits with 3.