Bug 1145076 - enable host time drift validation by default
Summary: enable host time drift validation by default
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.5.0
Assignee: Eli Mesika
QA Contact: Petr Kubica
URL:
Whiteboard: infra
Depends On:
Blocks: rhev3.5beta3
TreeView+ depends on / blocked
 
Reported: 2014-09-22 10:40 UTC by Oved Ourfali
Modified: 2016-02-10 19:11 UTC (History)
12 users (show)

Fixed In Version: org.ovirt.engine-root-3.5.0-13
Doc Type: Enhancement
Doc Text:
Feature: The difference between the time on the engine and the hosts is now checked by default, and a proper audit is being issued. Reason: There is a need alert on a time difference between the engine and the hosts. Result: There will be a proper alert in case a host has different time than the engine. This validation will be on by default.
Clone Of:
Environment:
Last Closed: 2015-02-17 17:17:21 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 33200 0 master MERGED core: enable host time drift validation by default Never
oVirt gerrit 33203 0 ovirt-engine-3.5 MERGED core: enable host time drift validation by default Never

Description Oved Ourfali 2014-09-22 10:40:00 UTC 
Description of problem:
Today, when the clock of the engine and a host aren't synced, it isn't validated by default. This issue is important, thus it should be validated by default.
The config entry name is EnableHostTimeDrift.
Comment 1 Eyal Edri 2014-09-28 11:29:58 UTC 
this bug was moved to MODIFIED before vt4 build date thus moving to ON_QA.
if you belive this bug isn't in vt4, please report to rhev-integ
Comment 2 Petr Kubica 2014-10-01 13:04:23 UTC 
Verified in 3.5.0-0.13.beta.el6ev
Comment 3 Eyal Edri 2015-02-17 17:17:21 UTC 
rhev 3.5.0 was released. closing.
Note You need to log in before you can comment on or make changes to this bug.