feat(instance): add TenantState REPAIRING for online repair#1835
feat(instance): add TenantState REPAIRING for online repair#1835sunilkumar-nvidia wants to merge 4 commits into
Conversation
Add REPAIRING tenant state across proto, cloud workflow, and OpenAPI. Surface it only when the instance is tenant-ready and a repair health merge is active; repair_merge_active() and shared merge-source constants preserve Failed, Updating, Configuring, and Terminating precedence.
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Enterprise Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (19)
WalkthroughThe PR introduces repair state support across the codebase by adding health report merge-source constants, defining a new ChangesRepair State and Health Merge Integration
🎯 3 (Moderate) | ⏱️ ~25 minutes
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsGit: Failed to clone repository. Please run the Comment |
Description
Adds a tenant-visible REPAIRING instance status for hosts under active repair health merges (repair-request or request-online-repair). Tenants and cloud sync can distinguish “instance is up but site is repairing it” from Ready, Updating (reprovision/firmware), Configuring, or Failed.
Repairing is shown only when the instance would otherwise be tenant-ready: InstanceState::Ready with synced configs and extension services ready. Repair merges do not override Failed, Updating, Configuring, Provisioning, or Terminating.
Type of Change
Changes
Related Issues (Optional)
Breaking Changes
Testing
Additional Notes
Summary by CodeRabbit
Release Notes