Skip to content

GB-305: grow would replace a configuration that already exists

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

What it means

goatbuilder grow writes the full configuration to ops/goatbuilder/goatbuilder.yaml. That file already exists and holds another configuration (not the one this goatlite grows into, which a run that stopped part way would have left), so grow refused before changing anything: it never replaces a configuration someone wrote. When the file carries grow's own header, the message says it is grow's file from an earlier run, since edited (or goatlite.yaml changed). grow changes files in the checkout only, never a host: a finished grow is undone with git before it is committed (restore goatlite.yaml and the files whose generated header it took off, and delete ops/goatbuilder/goatbuilder.yaml), and goatbuilder grow --dry-run shows every write first.

Why it happens

  • the checkout already declares a full configuration of its own
  • the file was edited after an earlier grow wrote it, and goatlite.yaml is still there

What to do

One line per step or alternative:

move ops/goatbuilder/goatbuilder.yaml aside, then goatbuilder grow --dry-run
or merge what it declares into goatlite.yaml, then grow again
grow's own file from an earlier run, edited: merge the edits into goatlite.yaml and delete ops/goatbuilder/goatbuilder.yaml, or delete it to grow afresh

Read more

Exit code

goatbuilder exits with 1.