Skip to content

GB-189: a stage of goatbuilder federate was asked for the wrong way

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

What it means

The stages status, deploy and test take the partner after them and run their own phases; --plan and --approve-plan belong to deploy, whose start is phase 10 or, once the admission is done by hand, 11. Nothing ran.

Why it happens

  • the partner was left out, or given after a peering name instead of a stage word
  • --to, --resume or a --from other than 10 or 11 was given to a stage
  • --plan or --approve-plan was given outside deploy
  • --bilateral was given outside test
  • rotate <partner> <key> named a key whose rotation is designed and not built in this goatbuilder (transport or signing; this goatbuilder rotates the leaves and the carrier keys), or a key it does not know; the message says what is missing (for transport, that the partner cannot yet receive our new package)

What to do

One line per step or alternative:

goatbuilder federate deploy <partner> --approve-plan <hash> (or --from 11 after the admission)
goatbuilder federate test <partner>
goatbuilder federate rotate <partner> leaves (or carrier: the keys this goatbuilder rotates; the message lists them)

Read more

Exit code

goatbuilder exits with 1.