GB-303: the partner has not read back our new IPsec CA¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-303 is printed by goatbuilder. The same text offline: goat explain GB-303 or goatbuilder explain GB-303.
What it means¶
An ipsec-ca rotation switches the edge to a leaf issued by our new per-peering CA only once the partner trusts that CA. Nothing on our side can read the partner's trust store, so the switch needs the sha256 fingerprint the partner read back after placing our new CA (peering_edge_rotation_ca_readback, or goatbuilder federate rotate <partner> ipsec-ca --partner-holds-ipsec-ca <sha256>). It was not given, or it is not the staged CA's fingerprint. Nothing was moved.
Why it happens¶
- the partner has not placed our new CA yet, or has not read its fingerprint back on the call
- the fingerprint read back belongs to another file
What to do¶
One line per step or alternative:
have the partner place our new CA beside their current one and read back its sha256 fingerprint, then run the rotation again with that fingerprint
Read more¶
Exit code¶
goatbuilder exits with 2.