Bug 773049

Summary:	[Beaker] Deleted jobs are not really deleted.
Product:	[Retired] Beaker	Reporter:	Jeff Burke <jburke>
Component:	web UI	Assignee:	Raymond Mancy <rmancy>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	high
Version:	0.8	CC:	bpeck, dcallagh, ebaak, gozen, jstancek, mcsontos, pbunyan, rmancy, stl
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-15 00:16:37 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 Jeff Burke 2012-01-10 19:01:49 UTC

Description of problem:
 When looking at a matrix view using the filter. Results that were deleted are still tallied in the columns.

For example:
 https://beaker.engineering.redhat.com/matrix/?whiteboard=2.6.32-225.el6+KernelTier1+Official+Clone%3ARS+301402+[hp-dl385g7-03.lab.bos.redhat.com]&whiteboard=2.6.32-225.el6+KernelTier1+Official&whiteboard_filter=2.6.32-225.el6+KernelTier1+Official&toggle_nacks_on=on

The jobs that are found during the filter:
176533
177101
178726
178727
178728
178730

But if you try to view some of those jobs you get the following message:
Invalid J:178726, has been deleted
Invalid J:178727, has been deleted
Invalid J:178728, has been deleted

Comment 1 Raymond Mancy 2012-01-11 07:03:57 UTC

Easiest solution is to actually hard delete the jobs from the DB, which means deleting the results. Is there any reason why I can't go ahead and do this ?

Comment 2 Raymond Mancy 2012-01-13 06:20:05 UTC

Completely removing the Jobs from the DB does not allow us to show historical data, so I guess we can't

Comment 3 Jeff Burke 2012-01-13 13:31:15 UTC

Ray,
 You may have discussed this with other Beaker developers. But I don't understand why would you want to see historical data on something you have deleted? If I delete a job it is because I don't want people to see it.

Sorry if I am not getting it :/

Best,
Jeff

Comment 4 Raymond Mancy 2012-01-16 00:14:47 UTC

Hi Jeff,

From a users perspective, there is zero reason to keep jobs around for which the owner has indicated that they are no longer interested in. 

However, the data may be helpful to admins/developers for various reasons (historical queue times to measure potential degredation in QoS etc). Although we don't currently use the historical data, hard deleting jobs from the DB would mean that we will never have the option to in the future. I'll bring it up in the dev meeting and see what others think though.