Skip to content

GB-277: an edge result cannot be imported

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

What it means

On a two-driver peering (drivers: two), the controller imports the file the edge driver wrote for a phase's edge half with goatbuilder federate import <peering> <phase> <file> --sha256 <code>, the confirm code the edge driver printed. The import refused it: the file cannot be read; the code is not hex, gives fewer than the 32 hex digits the edge driver prints, or is not the start of the file's sha256; the file is not that phase's edge result for this peering (another schema, another peering, another side); or this peering's journal here is not waiting on the edge driver at that phase. Nothing was placed or recorded.

Why it happens

  • the file was changed, or not copied whole, on its way from the edge driver
  • the confirm code was mistyped, or read from another run of the edge driver
  • the file is another peering's, another phase's, or the core side's result
  • the controller's run has not reached the phase's hand-off in this working directory

What to do

One line per step or alternative:

copy the file the edge driver wrote again, and give the confirm code it printed: goatbuilder federate import <peering> <phase> <file> --sha256 <code>
goatbuilder federate <peering> --from <phase> (on the controller, to reach the hand-off first)

Read more

Exit code

goatbuilder exits with 1.