Bug 720046

Summary:	RFE: Power command history should be included in the History Tab
Product:	[Retired] Beaker	Reporter:	Sean Waite <swaite>
Component:	web UI	Assignee:	Steven Lawrance <stl>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.6	CC:	bpeck, dcallagh, jnicolet, mcsontos, rmancy, stl
Target Milestone:	---	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-08-12 02:43:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Sean Waite 2011-07-08 20:27:53 UTC

Description of problem:
We only keep track of the 10 most recent power actions. We would like those to be included in the History tab, as well, for a more complete picture of what is going on.

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


Actual results:
Power commands are only logged in the power tab, and only the 10 most recent commands

Expected results:
All power commands should show up on the history tab, for a permanent record of what was done

Comment 1 Steven Lawrance 2011-07-19 05:26:02 UTC

How much log detail would you like to see in the History tab?  Just the result of each command, or one entry each for submission, processing/sending to cobbler and completion?

Or perhaps it would be enough to have the full history available via the power tab?  I actually thought it was an improvement to have "transient" power info cleaned up from the system history tab, making it easier to find any configuration changes etc.

Comment 2 Sean Waite 2011-08-01 13:43:44 UTC

We'd basically like the information that is on the power tab to also be in the history tab. Who power cycled the machine, what service they used, when they did it, what they did, and if it worked or not. 

The idea behind this is that we can go back and find who power cycled a machine a fair amount of time ago, rather than losing all of that data as soon as the 10th power cycle rolls around. Having it on the history tab also provides a clearer look at what is going on, we can see failed (or successful) power cycles amid the tests being kicked off. 

We can deal with one entry per action on the history tab, we don't need to see it being queued, running, and then being completed/failed. If it, for some reason, never exits the queued or running status, it might be nice to see that, but otherwise the final status is all we really need. If it does get stuck in the running/queued status - it'd fail, and we can grab that additional info from the Power tab.