Skip to content

GB-265: the run is waiting on the other driver

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

What it means

The peering is declared with two drivers (drivers: two): an edge driver that reaches only the edge host and a controller that reaches the core. This phase needs the edge, so the controller stopped before acting and handed it to the edge driver. The stop prints the exact command to run there, the file it writes, and the two commands to run here after it; with -o json the report carries them as the member handoff. It stops as a by-hand stop does (exit 0).

Why it happens

  • the peering's phase needs the edge host, and this machine is the controller

What to do

One line per step or alternative:

run the command the stop names on the edge driver, bring its result file here, then run the import and the command after it that the stop names

Read more

Exit code

goatbuilder exits with 0.