Backup alert status is overwritten by last module result, causing missed alerts

[gsanchietti]

Steps to reproduce

• Schedule a backup involving multiple modules (e.g., Samba and Traefik).
• Cause a backup failure in one module (e.g., stop the Samba container so its backup fails).
• Ensure at least one other module in the backup succeeds (e.g., Traefik).
• Observe the backup status and alerting behavior.

Expected behavior

A backup failure in any module should trigger an alert and set the backup status to failure for the whole backup job.

Actual behavior

If any module's backup succeeds, the backup status is set to success, and no alert is raised, even if other modules failed. The status is determined by the last evaluated module in the loop, which is arbitrary.

Components

• core 3.9.1

See also

• Helpdesk ticket #191650

---

Thanks to Nicola for reproducing the issue and providing a test environment.

[gsanchietti]

Testing image: core-3.9.2-dev.1

Test case 1

• Check the issue is not reproducible: make sure the alert is on both on Grafana and NOC (if the machine has a subscription)

Test case 2

• After test case 1
• Fix the backup error
• Check the alert is gone

[nrauso]

all test cases VERIFIED