fix: Don't process the DPU CR which is being deleted#4125
Merged
Conversation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (3)
Summary by CodeRabbit
WalkthroughThe DPF SDK now identifies terminating DPU resources as ChangesDPF reprovision readiness
Estimated code review effort: 3 (Moderate) | ~20 minutes Sequence Diagram(s)sequenceDiagram
participant WaitingForReady
participant get_dpu_phase
participant DPU_CR
WaitingForReady->>get_dpu_phase: Read current DPU phase
get_dpu_phase->>DPU_CR: Inspect DPU resource
DPU_CR-->>get_dpu_phase: Deleting, NotFound, or Ready
get_dpu_phase-->>WaitingForReady: Return phase or not-found error
WaitingForReady-->>WaitingForReady: Wait during Deleting or NotFound
WaitingForReady-->>WaitingForReady: Continue after Ready
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
wminckler
approved these changes
Jul 24, 2026
abvarshney-nv
enabled auto-merge (squash)
July 24, 2026 19:03
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.
When reprovisioning a DPU, reprovision_dpu deletes the DPU CR, but the DPF operator's finalizer keeps the old CR around briefly with a deletionTimestamp and a stale status.phase (specially Ready or Error). On the immediate requeue into WaitingForReady, NICO read that stale Ready/Error and jumped straight to next state — so reprovisioning was never actually observed.
get_dpu_phase now maps a set
deletionTimestamptoDpuPhase::Deleting, andhandle_dpf_waiting_for_readyshort-circuits to a wait on Deleting (and on NotFound, the brief gap before the fresh CR is created) before any side-effecting calls. NICO now waits for the operator to delete the old CR and create the new one, then proceeds only when that fresh CR reports Ready.Related issues
Type of Change
Breaking Changes
Testing
Additional Notes