When disabling offline alerts for VMs/containers, the setting was being persisted correctly and honored by the alert system, but the UI always showed "Warn" instead of the actual saved state. Root cause: When reconstructing the overrides list from backend config, the guest override mapping was copying poweredOffSeverity but omitting disableConnectivity, causing ResourceTable to fall back to global defaults. Fix: Add disableConnectivity field to guest override reconstruction in Alerts.tsx (line 676), matching the pattern already used for Docker containers. |
||
|---|---|---|
| .. | ||
| __tests__ | ||
| Alerts.tsx | ||