Skip to content

GB-321: a file a step of this run wrote is missing or is not what it wrote

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

What it means

A step of a federate run leaves its result in the working folder for the next one to read: phase 1's preflight result and the slot recheck's, the agreement, a back-out host record, the rotation id, an edge result on a two-driver peering. The file the next step read was not there, was not JSON, or did not hold what that step writes (another peering's name, a malformed id). Nothing after it ran.

Why it happens

  • the step that writes it stopped before writing it (its own failure is above, or in its log)
  • the file was edited, replaced or removed by hand between the steps
  • a different peering's working folder was named (--work, FED_WORK)

What to do

One line per step or alternative:

run the step that writes it again (the message names the file; its phase is the one before)
remove a file the message says is malformed, then run the same command again

Read more

Exit code

goatbuilder exits with 1.