GB-309: the retire step finds no confirmed rotation to retire¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-309 is printed by goatbuilder. The same text offline: goat explain GB-309 or goatbuilder explain GB-309.
What it means¶
The retire step of an IPsec credential rotation (goat-peering-edge, peering_edge_rotation_retire) removes the set-aside key in .previous-<id>/ on the edge, and nothing else: it never moves the live pair, the staged pair or our CA. It removes the key only once the new leaf is live: the confirm recorded it in .previous-<id>/confirmed (the unique id of the IKE SA the re-authentication made, and the time), the live pair is not the set-aside one, the live key is the live certificate's, and that SA, or one established after the confirm's time, has an installed CHILD SA. The confirm is recorded only once the SAs from before the re-authentication are gone, and a roll-back removes the record. This edge has no .previous-<id>/ for the id given, or the rotation is not confirmed live, so nothing was moved or removed.
Why it happens¶
- the id is mistyped, or names a rotation of another edge
- the rotation stopped before its switch, so the live pair is still the set-aside one
- the rotation was not confirmed: it stopped after the switch and before its confirm wrote .previous-<id>/confirmed
- the confirm's record is unreadable: it lacks the id= or at= line the confirm writes
- neither the IKE SA the confirm recorded nor one established since is up, or the live key is not the live certificate's
- goatbuilder federate rotate --retire: this side's ledger (<work>/ipsec-rotations.json) shows no such rotation whose phase 11 switched and whose phase 14 passed here after the switch, or it is already retired
What to do¶
One line per step or alternative:
check the id the rotation printed (ls /etc/swanctl/.previous-*, or <work>/ipsec-rotations.json)
run the rotation again with the same id: it re-authenticates, confirms and writes .previous-<id>/confirmed; retire once phase 14 passed here after the switch, and the partner says theirs did
Read more¶
Exit code¶
goatbuilder exits with 2.