Skip to content

fix(ops): release terminal cutover lease after carrier revoke - #506

Merged
James3014 merged 1 commit into
mainfrom
fix/505-m5-lease-release
Oct 11, 2026
Merged

James3014 merged 1 commit into
mainfrom
fix/505-m5-lease-release

Conversation

@James3014

Copy link
Copy Markdown
Owner

Closes #505

Summary

  • Run the carrier revoke before the terminal lease release in scripts/ops/m5-cutover/m5-cutover.sh step 10. release-terminal-lease / releaseClosedCutoverLeaseLocal requires the exact revoked root carrier.
  • Pass the revoked carrier's current DB version (carrier_bindings.version where revoked=1) instead of the approval-time $CVER (1). The CLI rejects versions below 2.

Evidence

On the Dev M5 cutover 5c008b0 → 8553fc5 (cutover 349621ba, 2026-10-11T20:22Z), the summary showed lease release FAILED. Running the release manually with revoked carrier version 2 returned terminalState: released, leaseVersion: 4.

Test plan

🤖 Generated with Claude Code

release-terminal-lease requires the exact revoked root carrier at its
current version (>=2); the script ran it before revoke with the
approval-time version, so it always failed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@James3014
James3014 enabled auto-merge (squash) October 11, 2026 20:26
@James3014
James3014 merged commit b0639e8 into main Oct 11, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

m5-cutover.sh: terminal lease release uses wrong carrier version and runs before revoke

1 participant