Skip to content

GB-064: the checkout is behind the trunk in what a deploy reads

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

What it means

A real run reads ops/ansible (roles, plays, group_vars, inventory, the rendered pins) and ops/pins from the checkout it runs in. The trunk carries commits to those paths that this checkout lacks, so a file rendered from it would remove on the host what those commits added, and the play would report success (contract C3, F-410). Refused before any host is touched, in both avenues (ops/scripts/fresh-source.sh).

Why it happens

  • the checkout was not brought onto the trunk after a merge
  • a feature branch was cut before a change to a role, group_vars or the pins landed

What to do

One line per step or alternative:

on main: git pull --ff-only <trunk remote> main
on a branch: git fetch <trunk remote> main && git rebase <trunk remote>/main

Read more

Exit code

goatbuilder exits with 1.