Bug 797957

Summary:	TimeoutBase.getLegal() logic issue
Product:	[Retired] oVirt	Reporter:	Laszlo Hornyak <lhornyak>
Component:	ovirt-engine-core	Assignee:	Laszlo Hornyak <lhornyak>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	acathrow, dfediuck, herrold, iheim, ykaul
Target Milestone:	---	Keywords:	CodeChange
Target Release:	---
Hardware:	All
OS:	Unspecified
Whiteboard:	infra
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-13 08:12: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 Laszlo Hornyak 2012-02-27 15:57:34 UTC

Description of problem:

Two possible problems with TimeOutBase.getLegal():

 - synchronizes agains a global lock Object, but reads from a HashMap that is not synchronized
 - if there is a timeoutBase which has its timeout over, then the timeout will be just removed but no new timeout set, so this auditloggable could be logged twice in the period set

Comment 1 Itamar Heim 2012-12-13 08:12:37 UTC

Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.