Bug 1284913

Summary: Multiple same alerts about backup
Product: [oVirt] ovirt-engine Reporter: Lukas Svaty <lsvaty>
Component: Frontend.WebAdminAssignee: bugs <bugs>
Status: CLOSED NOTABUG QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.6.0.1CC: bugs, didi, ecohen, emesika, oourfali, ylavi
Target Milestone: ---Flags: rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-29 08:42:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lukas Svaty 2015-11-24 13:02:51 UTC
Description of problem:
Alert "There is no full backup available, please run engine-backup to prevent data loss in case of corruption." is displayed every 6/18 hours in alerts. It should be displayed only once (the last one) the same as alert about power management.

Version-Release number of selected component (if applicable):
rhevm-webadmin-portal-3.6.0.3-0.1.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1. Do not set up backup
2. See alerts in webadmin
3.

Actual results:
Multiple alerts about backup.

Expected results:
Only one should be displayed.

Additional info:
Same bug was previously about powermanagement not being configured alert, which was spamming the alerts tab. Decision was to show every alerts only once and do not repeat it if it already exist in alerts tab.

Comment 1 Einav Cohen 2015-11-25 17:13:07 UTC
marking as 'infra' as this seems related to the backup-awareness.

Comment 2 Oved Ourfali 2015-11-29 08:31:42 UTC
As far as I remember, this was as designed.
Eli/Yaniv?

Comment 3 Eli Mesika 2015-11-29 08:40:38 UTC
(In reply to Oved Ourfali from comment #2)
> As far as I remember, this was as designed.
> Eli/Yaniv?

Yes, it was intended and we wanted to insure that this alert is handled and not ignored.
So, best practice to remove this alert is to have a cron job that uses engine-backup to generate a daily backup