Bug 1260554

Summary:	Beaker UI should handle Panic more intelligent
Product:	[Retired] Beaker	Reporter:	Chao Ye <cye>
Component:	web UI	Assignee:	beaker-dev-list
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	tools-bugs <tools-bugs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	20	CC:	cye, dcallagh, mjia, rjoost
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-07 05:40:05 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:

Description Chao Ye 2015-09-07 08:52:30 UTC

Description of problem:
Now beaker only have ignore options for watchdog:
==================================================
<watchdog panic="ignore"/>

But those Paniced job were not highlighted, the red color is similar with failure job. I suggest new option can be add to highlight there is a panic happend on this job to indicate users to check it.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Dan Callaghan 2015-09-08 01:37:22 UTC

I'm not sure what you're asking for here.

There is already a special result for Panic, it shows up as blue to distinguish it from normal Fail and Warn. However if you disable panic detection using <watchdog panic="ignore"/> then Beaker will not detect and report the panic.

Can you please explain more detail about the situation you have and the expected behaviour? What problem are you trying to solve?

Maybe you want a way to have the panic be *detected* and reported by Beaker but not abort the recipe, continue letting it run?

Comment 2 Roman Joost 2016-05-27 20:36:27 UTC

Dear Chao,

it would be helpful if you can clarify your report as Dan commented in comment 1 otherwise I'll have to close this Bug.

Comment 3 Roman Joost 2016-06-07 05:40:05 UTC

Closing this one due to inactivity.