Bug 1188140

Summary:	[RFE] - If engine-backup last run fails, notification in the UI should refer user to it's log.
Product:	[Retired] oVirt	Reporter:	Yaniv Lavi <ylavi>
Component:	ovirt-engine-installer	Assignee:	Doron Fediuck <dfediuck>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.5	CC:	bugs, ecohen, gklein, iheim, lsurette, oourfali, rbalakri, yeylon, ylavi
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	3.6.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	integration
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-22 15:30:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1188127
Bug Blocks:	1188119

Description Yaniv Lavi 2015-02-02 07:22:22 UTC

Description of problem:
Since users may define 3rd party backups that run engine-backup automatically, we should refer them to last run log location in the notifications in the UI about backup not preformed.

Comment 1 Oved Ourfali 2015-03-22 13:13:32 UTC

In my opinion this one and Bug 1188143 are identical.
The engine-backup procedure should add events straight to the database either on success, or on failure (no need for "started" as the backup process should be fast, even on large datacenters). The failure/success should come with a message as well, that will be put in the events table, and should contain the message (with the log path, for example).

Yaniv?

Comment 2 Yaniv Lavi 2015-03-22 15:30:40 UTC

(In reply to Oved Ourfali from comment #1)
> In my opinion this one and Bug 1188143 are identical.
> The engine-backup procedure should add events straight to the database
> either on success, or on failure (no need for "started" as the backup
> process should be fast, even on large datacenters). The failure/success
> should come with a message as well, that will be put in the events table,
> and should contain the message (with the log path, for example).
> 
> Yaniv?

Sounds good to me. Add this to the other bug and closing this one.

*** This bug has been marked as a duplicate of bug 1188143 ***