mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-09-10 02:25:56 +00:00
cb12b6f35c
An in-progress PBS snapshot (reproduced on VM 117 at 9% written) was counted as a completed backup: the guest's LastBackup jumped to "now" the moment vzdump started, and the workloads badge showed a green healthy shield for a backup that did not exist yet. If the job aborted, that shield had never been true. Detect the in-flight state from what the PBS listing actually says - no size and no index.json.blob manifest in files - and flag the snapshot InProgress instead of complete. On the PVE side, correlate storage content entries with live vzdump tasks: a guest archive whose ctime falls inside a running task's window is that task's partial output, and a PBS-storage entry without a size has no manifest yet. In-flight artifacts now feed a new per-guest BackupInProgress flag rather than LastBackup, so the badge age always reflects the latest COMPLETED backup. The workloads badge gets a distinct blue "Running" state (green would claim success, None would hide that work is underway), with the last-completed age kept in the tooltip and accessible label. Recovery points map to OutcomeRunning with no completion time, keeping posture freshness and the Backups page's latest-restore pointers anchored to completed backups; the recoverable-artifact list shows a Running chip. A cached in-flight snapshot forces a per-poll re-fetch of its group so completion or abort is noticed promptly instead of after the cache TTL.