-
Notifications
You must be signed in to change notification settings - Fork 1.3k
fix(server): keep Error-phase sandbox records through the prune sweep #3498
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
pkhodade-NV
wants to merge
1
commit into
windows
Choose a base branch
from
fix/mxc-sandbox-prune-keeps-error-phase
base: windows
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+46
−1
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Before this PR, a gateway-managed driver that returned
NotFoundduring startup left a temporaryBackendResourceMissingerror for clients to inspect, then the reconciliation sweep pruned it after the orphan grace period. By matching everyErrorhere, the sweep now returns beforespawn_driver_sandbox_cleanupandapply_deleted_if_version_lockedforBackendResourceMissing,StartFailed, and theComputeResourceMissingstate produced for missing Starting/Stopping/Stopped sandboxes. That affects Docker, Podman, VM, Kubernetes, and extension drivers as well as MXC: orphaned names and gateway-owned records remain indefinitely, and the idempotent driver cleanup for volumes/secrets is skipped until a user explicitly deletes the sandbox.This is broader than the MXC restart race described by the PR. Please narrow the exemption to the intended settled error categories or MXC-specific case. If blanket retention is intentional, update the startup/reconciliation lifecycle contract and architecture documentation, and add regression coverage for
BackendResourceMissingandComputeResourceMissingso the resource-retention behavior is explicit.