Skip to content

GB-267: this part of a two-driver peering is not built yet

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

What it means

A peering declared with two drivers (drivers: two) is handed off between the edge driver and the controller only at phases 1, 2 and 3, where the hand-off is built. These cases are refused before anything runs: the edge driver's own run (goatbuilder federate <partner> --side edge) of a phase other than 1 or 3; the controller's goatbuilder federate import of a phase other than 1 or 3; a two-driver run that would reach a phase after 3 that needs the edge (11, 12, 13 or 14), whose hand-off is designed and not built; and a two-driver run from phase 3 with FED_MEASURE=here, which measures one machine and so has no halves to hand off. That includes every goatbuilder federate deploy, which runs phase 10 then 11: it is refused before its plan is approved or rechecked, so phase 10 never admits the edge on our core.

Why it happens

  • goatbuilder federate <partner> --side edge was run on the edge driver for a phase other than 1 or 3
  • goatbuilder federate import <partner> <phase> <result> --sha256 <code> was run for a phase other than 1 or 3
  • a two-driver run that would reach phase 11, 12, 13 or 14, such as --from 4 with no --to, or goatbuilder federate deploy (a run from 4 to 10 is not refused)
  • a two-driver run from phase 3 with FED_MEASURE=here

What to do

One line per step or alternative:

run the peering with one driver for now: remove drivers: two from its peerings: entry, from a machine that reaches both the edge host and the core host
for phase 3: unset FED_MEASURE (or set it to ssh), so phase 3 measures in halves over SSH

Read more

Exit code

goatbuilder exits with 1.