Skip to content

GB-282: rotating our CA needs a decision before it can be built

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

What it means

goatbuilder federate rotate <partner> ca would replace the CA that signs our peering leaves. In package v1 every check accepts exactly one CA per party, the one fingerprint our package carries (federation-package-spec.md §5.1), so the partner could not trust the new CA beside the old one while our leaves change over, and data would stop. The overlap of both CAs is decided (ADR 1242: our next CA is announced in package v2) and designed in the key-rotation design §4, but this goatbuilder does not build it yet. Nothing ran.

Why it happens

  • rotate <partner> ca was asked for, and this goatbuilder does not yet build the CA overlap ADR 1242 decides

What to do

One line per step or alternative:

rotate the leaves instead, under the same CA: goatbuilder federate rotate <partner> leaves
read ADR 1242 and the key-rotation design §4 for the CA overlap a later goatbuilder builds

Read more

Exit code

goatbuilder exits with 1.