Skip to content

GB-290: the staged IPsec certificate is not right for this link

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

What it means

Before an IPsec credential rotation moves anything, goat-peering-edge checks the staged certificate: its key is the staged key, it chains to the CA it must chain to (our current CA for ipsec-leaf, the staged new CA for ipsec-ca), its subject CN is peering_edge_local_id, its key is ECDSA P-384 (secp384r1) as the proposals require, it is valid now, and it stays valid for peering_edge_min_valid_days more days (default 30). The message names each check that failed. Nothing was moved.

Why it happens

  • the leaf was issued for another peering or another identity
  • the leaf was issued by another CA, or the staged key belongs to another certificate
  • the leaf uses another key type, or expires too soon

What to do

One line per step or alternative:

have the ceremony issue the leaf again with Subject CN = peering_edge_local_id and an ECDSA P-384 key, from the right CA, then stage it and run the rotation again

Read more

Exit code

goatbuilder exits with 2.