You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
New version notice turns a successful backup report into WARNING and exit 1 (Healthchecks disabled) #346
ProxSave runs the nightly configuration backup on our Proxmox VE host in daemon mode. The report goes out by email. Healthchecks is disabled.
#334 was fixed in v0.42.1 for the Healthchecks result. The same case still exists for the backup report and the exit code when Healthchecks is not used.
What happens:
The backup completes. All files are in the archive. Both copies are written. There are no errors.
A newer ProxSave release is available.
The report title becomes WARNING, the warning count is 1, and the run exits with code 1.
A new release is not a backup problem. The report answers one question: is the backup good. When every release turns the report yellow, WARNING stops meaning "check the backup". People learn to ignore it, and a real warning gets lost in the noise.
We update on purpose. We read the release notes for the whole version range, then plan the change. A new release does not change that plan, so it should not change the backup status.
Request:
Base the report status, the warning count and the exit code only on the backup run.
Show an available update as an info line in the report, not as a warning. A separate notice is also fine.
Optional: a setting for this, for example UPDATE_NOTICE=info|warning|off.
Environment: ProxSave v0.44.0, Proxmox VE 9.2 on Debian 13, proxsave-daemon, email notification, HEALTHCHECK_ENABLED=false.
Activity
tis24dev commentedon Oct 31, 2026
Hi, thanks for your reply.
Let's move this discussion to the forum so we can explore it further.