Skip to content

GB-328: a rotation's values reach no play in the phases this run built

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

What it means

A key rotation of goatbuilder federate rotate passes its values (the rotation id, and for an IPsec rotation its kind and read-back) to the plays of one phase: phase 11 for ipsec-leaf and ipsec-ca, phase 2 for the peering key. It puts them before each play's -e fed_work=. The phase this run built has no such play, so the values would reach nothing and the phase would run as a plain one and report the rotation done. Nothing ran. The phases are built from the agreement each run, and the rotation already checked that the agreement chose its transport, so this is goatbuilder's own fault, not the peering's.

Why it happens

  • the phase's command in this goatbuilder no longer runs its play with -e fed_work=

What to do

One line per step or alternative:

goatbuilder federate rotate <partner> <key> --dry-run (it prints the phase's command)
report the command and this goatbuilder's version (goatbuilder --version); do not run the phase by hand in its place

Read more

Exit code

goatbuilder exits with 1.