Bug 1394287

Summary:	[RFE] Notification severity levels should match the levels of $evm.log
Product:	Red Hat CloudForms Management Engine	Reporter:	Peter McGowan <pmcgowan>
Component:	Appliance	Assignee:	John Hardy <jhardy>
Status:	CLOSED WONTFIX	QA Contact:	Dave Johnson <dajohnso>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.7.0	CC:	abellott, jhardy, jocarter, mkanoor, obarenbo, tfitzger
Target Milestone:	GA	Keywords:	FutureFeature
Target Release:	cfme-future
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-08 12:06:17 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:

Description Peter McGowan 2016-11-11 15:02:57 UTC

Description of problem:
It would be more intuitive to use if the severity levels for $evm.create_notification (currently 'success', 'info', 'warning' and 'error') were the same as the severity levels for $evm.log (currently 'unknown', 'fatal', 'error', 'warn', 'info' and 'debug'). 

This RFE is to suggest keeping 'success', change 'warning' to 'warn', and add 'fatal' and possibly 'unknown' to the severity levels for $evm.create_notification.

Version-Release number of selected component (if applicable):
5.7.0.10-beta3.20161109111947_9a61b18

Comment 2 Greg McCullough 2016-11-11 15:27:57 UTC

Gregg - Can you review this request as I think these changes need to be made on the backend first before automate can utilize them.  Let me know if you want to discuss.