fix(flow): find untracked hosts when expected inventory is empty - #4909
fix(flow): find untracked hosts when expected inventory is empty#4909chet wants to merge 1 commit into
Conversation
Flow keeps a drift report comparing the hosts Cloud expects with the hosts Core discovers. As it stood, removing the final expected host made Flow stop asking Core for machines altogether. Hosts still visible to Core then disappeared from the report, while DPU records could sometimes be reported as unexpected hosts. So, machine sync now asks Core what is present even when Cloud expects zero hosts, and it builds the report from `HOST` machine records only. If Core cannot answer, Flow keeps the last reliable report instead of replacing it with an empty one. Key updates include: - Untracked hosts remain visible after the final expected host is removed. - DPUs are excluded from host matching and drift reporting. - A valid empty response and a failed Core request remain meaningfully different. Tests added! This supports NVIDIA#4356 Signed-off-by: Chet Nichols III <chetn@nvidia.com>
|
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 (4)
💤 Files with no reviewable changes (1)
Summary by CodeRabbit
WalkthroughMachine synchronization now filters NICo inventory to ChangesInventory synchronization
Estimated code review effort: 3 (Moderate) | ~25 minutes Mergeability Score: ⚪ Minimal · up to This localized inventory-sync fix is merge-ready after normal checks and review; no actionable merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@coderabbitai full_review, thanks! |
|
✅ Action performedFull review finished. |
🔐 TruffleHog Secret Scan✅ No secrets or credentials found! Your code has been scanned for 700+ types of secrets and credentials. All clear! 🎉 🕐 Last updated: 2026-08-13 00:41:27 UTC | Commit: cd59638 |
Flow keeps a drift report comparing the hosts Cloud expects with the hosts Core discovers. As it stood, removing the final expected host made Flow stop asking Core for machines altogether. Hosts still visible to Core then disappeared from the report, while DPU records could sometimes be reported as unexpected hosts.
So, machine sync now asks Core what is present even when Cloud expects zero hosts, and it builds the report from
HOSTmachine records only. If Core cannot answer, Flow keeps the last reliable report instead of replacing it with an empty one.Key updates include:
Related issues
This supports #4356
Type of Change
Breaking Changes
Testing