Repository navigation
Conversation
Add a strict real-microVM process regression that kills the control plane during an infinite guest workload, requires bounded Firecracker reclamation and judge-node exit, then restarts the control plane and proves expired-lease recovery through a second Attempt and terminal result. Refs: FR-SCHED-001, FR-JUDGE-003, ACC-P0-003, ACC-P0-016, ACC-P0-017 Tests: cargo fmt --all -- --check; cargo check --workspace --all-targets --locked; cargo clippy --workspace --all-targets --locked -- -D warnings; focused process E2E compiled and skipped without KVM; python3 scripts/check-workspace.py; bash scripts/check-docs.sh Unverified: strict real-KVM execution is blocked because /dev/kvm is not read-write accessible in this environment Security: No production boundary changes; the test asserts fail-closed teardown and lease recovery across a control-plane outage. Compatibility: No protocol, schema, runtime image, or persisted data changes. Migration: None.
CN059
force-pushed
the
agent/operator-cancel-command
branch
from
August 31, 2026 00:51
b980fa4 to
528a369
Compare
CN059
force-pushed
the
agent/real-microvm-control-disconnect
branch
from
August 31, 2026 00:51
83ad71f to
c8841ca
Compare
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
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.
Scope
Add one strict real-microVM process regression for the remaining control-channel outage gap. The test kills the control plane while an infinite C workload is running, requires Firecracker API/vsock reclamation and judge-node exit within three seconds, restarts the control plane, waits for expired-lease recovery into Attempt 2, and proves a fresh judge node persists the terminal timeout result.
Refs: FR-SCHED-001, FR-JUDGE-003, ACC-P0-003, ACC-P0-016, ACC-P0-017.
Non-scope
No production behavior, public or guest protocol, schema, migration, runtime image, network policy, authentication, authorization, or audit changes.
Verification
Passed locally:
cargo fmt --all -- --checkcargo check --workspace --all-targets --lockedcargo clippy --workspace --all-targets --locked -- -D warningspython3 scripts/check-workspace.pybash scripts/check-docs.shUnverified: strict real-KVM execution is blocked in the current environment because
/dev/kvmis not read-write accessible. A strict KVM runner should execute:OPENOJ_REQUIRE_KVM=1 OPENOJ_FC_TEST_IMAGES=<verified-runtime-out> cargo test -p openoj-control-plane --test process_e2e real_microvm_control_disconnect_reclaims_and_recovers --locked -- --nocapture --test-threads=1Risk and rollback
Risk is confined to test runtime/flakiness on KVM hosts; the assertions use the existing three-second reclamation contract. Roll back the single test commit if the environment contract proves invalid. No data rollback is needed.
Stack
This PR is intentionally stacked on #16, which is stacked on #15 and the real-microVM E2E series.