Bug 1389025

Summary:	Traceback during evaluation of alert when duration is not set
Product:	Red Hat CloudForms Management Engine	Reporter:	Satoe Imaishi <simaishi>
Component:	UI - OPS	Assignee:	Milan Zázrivec <mzazrivec>
Status:	CLOSED ERRATA	QA Contact:	Dmitry Misharov <dmisharo>
Severity:	medium	Docs Contact:
Priority:	high
Version:	5.6.0	CC:	cpelland, dclarizi, dmisharo, hkataria, jhardy, mpovolny, obarenbo, simaishi
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.6.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.6.3.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1379078	Environment:
Last Closed:	2016-11-30 19:57:30 UTC	Type:	---
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:	1379078
Bug Blocks:

Comment 2 CFME Bot 2016-11-03 20:36:37 UTC

New commit detected on ManageIQ/manageiq/darga:
https://github.com/ManageIQ/manageiq/commit/b15bfe7e68c9e57396d35ba62d8c2520bc53da07

commit b15bfe7e68c9e57396d35ba62d8c2520bc53da07
Author:     Harpreet Kataria <hkataria>
AuthorDate: Fri Oct 21 23:38:36 2016 -0400
Commit:     Oleg Barenboim <chessbyte>
CommitDate: Thu Nov 3 16:33:28 2016 -0400

    Merge pull request #11717 from mzazrivec/time_threshold_for_rt_performance_is_required
    
    Time threshold for real time performance has to be a required field
    (cherry picked from commit 210b52d0a31d17cf10aa9d14d4e5f3110f7584e9)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1389025

 app/controllers/miq_policy_controller/alerts.rb | 3 +++
 1 file changed, 3 insertions(+)

Comment 3 Dmitry Misharov 2016-11-16 10:17:46 UTC

Fixed and verified in 5.6.3.0.20161108115816_66df924.
Now an alert can't be created without filled "Field Meets Criteria for" field. Evaluation works fine.

Comment 5 errata-xmlrpc 2016-11-30 19:57:30 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-2839.html