Bug 846604

Summary: 3.2 - [bootstrap] Time jumps back and forward in logs during boostrap installation (do not set time if ntpd is running)
Product: Red Hat Enterprise Virtualization Manager Reporter: Gadi Ickowicz <gickowic>
Component: vdsmAssignee: Douglas Schilling Landgraf <dougsland>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.1.2CC: acathrow, alonbl, asegundo, bazulay, cpelland, danken, dougsland, hateya, iheim, lpeer, nlevinki, Rhev-m-bugs, sgrinber, ykaul
Target Milestone: ---   
Target Release: 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-18 12:28:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
vdsm bootstrap installation log none

Description Gadi Ickowicz 2012-08-08 08:43:42 UTC
Created attachment 602965 [details]
vdsm bootstrap installation log

Description of problem:
In the bootstrap installation logs of a host, the timestamps of sequential entries jump back and then forward again. The host has ntp configured, however its clock is back in the boostrap. A few entries later the time jumps back forward.

Wed, 08 Aug 2012 10:33:22 DEBUG    ['/usr/sbin/hwclock', '-s']
Wed, 08 Aug 2012 10:27:58 DEBUG
Wed, 08 Aug 2012 10:27:58 DEBUG
Wed, 08 Aug 2012 10:27:58 DEBUG    setHostTime end. Return:True
Wed, 08 Aug 2012 10:27:58 DEBUG    <BSTRAP component='SET_SYSTEM_TIME' status='OK' message='setSystemTime ended successfully'/>
Wed, 08 Aug 2012 10:27:58 DEBUG    ['/sbin/service', 'cpuspeed', 'stop']
Wed, 08 Aug 2012 10:27:58 DEBUG
-----------------------------snip-------------------------------------------
ed, 08 Aug 2012 10:27:58 DEBUG    ['/usr/bin/openssl', 'req', '-new', '-key', '/etc/pki/vdsm/keys/vdsmkey.pem', '-config', '/tmp//req_1be959df-e608-47fe-9d0c-77bf9bf5fffb.conf', '-out', '/tmp//cert_1be959df-e608-47fe-9d0c-77bf9bf5fffb.req']
Wed, 08 Aug 2012 10:27:58 DEBUG
Wed, 08 Aug 2012 10:27:58 DEBUG
Wed, 08 Aug 2012 10:27:58 DEBUG    ['/usr/bin/openssl', 'dhparam', '-out', '/etc/pki/vdsm/keys/dh.pem', '2048']
Wed, 08 Aug 2012 10:33:32 DEBUG
Wed, 08 Aug 2012 10:33:32 DEBUG    Generating DH parameters, 2048 bit long safe prime, generator 2



Version-Release number of selected component (if applicable):
vdsm-4.9.6-26.0.el6_3.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Add a host with ntp to rhevm
2. SET_SYSTEM_TIME is run. 
  
Actual results:
Time may be inconsistent with NTP time

Expected results:
SET_SYSTEM_TIME should not run on a host with ntp

Additional info:
vdsm logs attached

Comment 3 Douglas Schilling Landgraf 2012-08-09 20:21:24 UTC
Patch:
http://gerrit.ovirt.org/#/c/7070/

Comment 4 Dan Kenigsberg 2012-08-10 13:36:14 UTC
The fact that ntpd is running does not mean that there is no lag in host time. It may make sense to avoid the sync - but only if ntp reports that we are on time already.

Note that I think that the proper solution is to requiring ntpd on the Engine, too.

Comment 5 Amador Pahim 2012-08-10 19:06:51 UTC
Engine rpm is already requiring ntp. Additionally we can check ntp during engine-setup (i'm working here).

Comment 7 Alon Bar-Lev 2013-01-15 16:09:20 UTC
Barak,

Why otopi?

This is legacy issue.

Alon