Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.
Go aialertsdashboarddockerdocker-monitoringgohomelabinfrastructure-monitoringkubernetesmonitoringmspproxmoxproxmox-backup-serverproxmox-mail-gatewayproxmox-veself-hostedtruenastypescriptvspherewebhooks
Integrate reviewed legacy sensor cleanup containment
pulse-triage[bot]648df92d5123
diff --cc docs/release-control/v6/internal/subsystems/deployment-installability.mdindex ab83d236ed,9dd27223f1..b68fb58229--- a/docs/release-control/v6/internal/subsystems/deployment-installability.md+++ b/docs/release-control/v6/internal/subsystems/deployment-installability.md@@@ -15,21 -15,36 +15,51 @@@## Purpose+### Legacy installer identity recovery is a whole-file decision++An installer recovering a pre-descriptor-helper agent-ID file accepts exactly+one bounded ID and its optional final newline. It must not accept a plausible+first line from an oversized, multi-line or NUL-bearing file. Portable byte-size+inspection precedes the bounded shell read, and every file byte must be accounted+for. Existing root-boundary ownership/mode/parent checks and descriptor-first+selection remain in force; no signature, service, token or enrolment rule changes.++`TestInstallSHLegacyAgentIDRecoveryAccountsForEveryByte` verifies normal and+maximum-length compatibility alongside rejected valid-prefix corruptions. The+Unix real-agent controls keep their independent two-second watchdog, with+process-group cancellation and separate build/probe timings. These source+fixtures do not establish signed native installation, persistence or recovery.++ ### Legacy sensor cleanup requires observed stopped targets++ The legacy sensor uninstaller must confirm each existing unit has stopped and+ was disabled before removing keys, mounts or files. Missing units are a no-op;+ failed or unknown service observation/stop/disable blocks further cleanup.+ Local container enumeration must succeed. Only current (pre-snapshot) legacy+ mount entries are eligible: snapshots and unrelated mounts remain unchanged.+ For each affected exact container, a successful status read must identify+ running or stopped. Previously running targets require a successful bounded+ stop and an explicit stopped readback; every subsequent configuration mutation+ requires a fresh stopped readback. Unknown state or failed stop means no edits+ or restart of that target. A failed `pct set` never falls back to direct edits.+ Direct legacy-line removal preserves file ownership/mode and reports errors.++ Only a previously running target may be restarted after cleanup or a confirmed+ mutation failure, and its running state must be observed. Lost stopped state+ prevents both further edits and automatic restoration. Failed enumeration,+ container edits/restoration, service cleanup or reload returns nonzero and+ cannot report whole cleanup complete. Incomplete container cleanup preserves+ legacy files and API access for local recovery. This does not remove the need+ for the guide's planned outage, backups and independent workload checks.++ `TestUninstallSensorProxyMountSafety`, `TestUninstallSensorProxyServiceSafety`+ and `TestUninstallSensorProxyMainReportsIncompleteLocalCleanup` execute isolated+ shell fixtures for status/stop/set/edit/start failures, lost state, only-prior-+ active restoration, snapshots, absent units and completion propagation. Only+ the fixed config directory is substituted; lifecycle tools are mocks, not native+ Proxmox or installed systemd acceptance. Remote SSH trust, purge consent and+ API-user removal opt-in remain unchanged.+### Audit report cleanup belongs to the original invoking processThe npm audit wrapper retains a captured advisory until the parent classifies