Skip to content

fix(ctf): keep spare teardown retryable after dispatch failure - #2386

Merged
Brad-Edwards merged 1 commit into
devfrom
fix/ctf-spare-cleanup-retry
Sep 25, 2026
Merged

Brad-Edwards merged 1 commit into
devfrom
fix/ctf-spare-cleanup-retry

Conversation

@Brad-Edwards

Copy link
Copy Markdown
Owner

Summary

  • Preserve a spare range owner and nonterminal pool status when teardown dispatch fails or its range ID has not resolved yet, so a later cleanup attempt can retry.
  • Resolve a late range ID from the recorded request before dispatching teardown.
  • Add regression coverage for transient dispatch failure and delayed range resolution.

ADR Impact

  • No ADR impact

ADRs touched: None.

Exceptions added or renewed: None.

Guardrail Changes

  • No guardrail files changed

Guardrail files changed: None.

Verification

  • Full ADR guard passed.
  • Import-linter and Ruff checks passed.
  • Relevant CTF tests passed (128 tests across spare cleanup, recovery, lifecycle, capacity, and teardown).
  • Docs updated where behavior or enforcement changed (not applicable; this restores retryability on an error path).

@sonarqubecloud

Copy link
Copy Markdown

@Brad-Edwards
Brad-Edwards merged commit 8a31d04 into dev Sep 25, 2026
80 checks passed
@Brad-Edwards
Brad-Edwards deleted the fix/ctf-spare-cleanup-retry branch September 25, 2026 01:55
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.

1 participant