Bug 741960

Summary:	[Beaker] RFE report on broken machines
Product:	[Retired] Beaker	Reporter:	Jeff Burke <jburke>
Component:	reports	Assignee:	Dan Callaghan <dcallagh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nick Coghlan <ncoghlan>
Severity:	high	Docs Contact:
Priority:	high
Version:	0.6	CC:	asaha, azelinka, bpeck, dcallagh, mcsontos, mishin, mschick, rmancy, stl
Target Milestone:	0.11	Keywords:	FutureFeature, Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	Measurements
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-01-17 04:34:55 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:	883606
Bug Blocks:

Description Jeff Burke 2011-09-28 15:33:36 UTC

Description of problem:
I would like to see a report by machine. How many times a machine is set to
Broken by the scheduler. Also how many times a user clicks "Report a problem"
per machine.

Comment 1 Bill Peck 2011-12-06 14:32:39 UTC

*** Bug 752109 has been marked as a duplicate of this bug. ***

Comment 2 Bill Peck 2011-12-06 14:33:19 UTC

Additional info: A report that contains frequently broken systems would be very
useful. I'm not certain what the best metrics to use for generating such a
report would be - but something like "disabled X times in Y time period" would
fit the bill nicely. Ideally, we'd be able to define X and Y before running the
report, or leave those values set in a config file somewhere that could be
tweaked without needing any package updates.

Comment 5 Amit Saha 2012-12-05 09:05:15 UTC

Systems against which a problem was reported can be found using:

mysql> select system.fqdn,activity.created from system, system_activity, activity where system.id = system_activity.system_id and system_activity.id=activity.id and activity.action='Reported problem'


System status can be obtained using:

mysql> select * from system_status_duration order by system_id;

This gives us the status of a machine and the time period during which it remained in that status. We can use these details to obtain the information sought as part of this bug.

Comment 7 Amit Saha 2012-12-11 07:57:00 UTC

Admin guide updated to include the above information: http://gerrit.beaker-project.org/#/c/1546/

Comment 8 Dan Callaghan 2012-12-19 00:17:46 UTC

Re-opening this so it doesn't get lost...

Comment 9 Dan Callaghan 2012-12-19 03:16:39 UTC

http://gerrit.beaker-project.org/1580

Comment 11 Dan Callaghan 2013-01-07 04:31:30 UTC

http://gerrit.beaker-project.org/1608

Comment 12 Dan Callaghan 2013-01-17 04:34:55 UTC

Beaker 0.11.0 has been released.