fix: make my_hypervisor non-critical when binary absent #111
No reviewers
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_compute!111
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "development_fix_my_hypervisor_noncritical"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The Compute dashboard fires a red 'Critical service(s) unavailable.' banner on any host without
my_hypervisoron PATH. Dev machines don't host VMs and shouldn't be banner-spammed.Related Issue
Closes #110
Changes
crates/hero_compute_admin/src/server.rs:681: critical flag for the my_hypervisor row is nowhyp_ok || Path::new("/usr/local/bin/my_hypervisor").exists(). Dev hosts (no binary) no longer flag it as critical; production hosts (binary present but doctor failing) still do.Test Results
Rebuilt and deployed on herodev. Pre-fix
/statusreturnedcritical: truefor my_hypervisor; post-fix returnscritical: false. Browser-side Compute island no longer shows the red banner.Please don't merge this one, the hypervisor is the core thing to have the compute running
Pull request closed