Skip to content

GB-266: the controller's checkout is not clean, so no hand-off is given

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

What it means

A two-driver peering's hand-off pins the edge driver's checkout to the controller's commit, so the controller gives one only when its own checkout is a git checkout with nothing uncommitted. The run stopped at the phase that needs the edge, before acting, and names each file with changes.

Why it happens

  • phase 10 placed rendered files, or admission wrote peerings.yml, and they are not committed yet
  • a file was edited by hand and not committed
  • the deployment's directory is not a git checkout

What to do

One line per step or alternative:

commit each file the refusal names, then run the same command again

Read more

Exit code

goatbuilder exits with 1.