docs: document candidate reservation cleanup on VM confirm#916
Open
cortex-ai-agents[bot] wants to merge 1 commit into
Open
docs: document candidate reservation cleanup on VM confirm#916cortex-ai-agents[bot] wants to merge 1 commit into
cortex-ai-agents[bot] wants to merge 1 commit into
Conversation
cortex-ai-agents
Bot
requested review from
PhilippMatthes,
SoWieMarkus,
auhlig,
juliusclausnitzer,
mblos and
umswmayj
as code owners
Contributor
Test Coverage ReportTest Coverage 📊: 69.5% |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR #871 added proactive candidate reservation cleanup when a VM is confirmed on a reservation. When a VM transitions from Spec-only to Spec+Status (newly confirmed on the expected host), the controller immediately removes that VM's UUID from Spec.Allocations on all other candidate reservations. This frees phantom capacity blocks on non-selected hosts immediately rather than waiting for each candidate's grace period expiry or periodic requeue. This behavior was undocumented.
Assisted-by: Claude Code:claude-sonnet-4-20250514 [Bash] [Read]