Bug 1090350

Summary:	Clock skew detected when the dates of server and client have no big time drift.
Product:	Red Hat Enterprise Linux 5	Reporter:	qianzhan
Component:	python-rhsm	Assignee:	Bryan Kearney <bkearney>
Status:	CLOSED ERRATA	QA Contact:	John Sefler <jsefler>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5.11	CC:	bkearney, fsharath, gxing, liliu, qianzhan
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-16 00:22:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1039651

Description qianzhan 2014-04-23 07:08:57 UTC

Description of problem:
Clock skew detected when the dates of server and client have no big time drift.

Version-Release number of selected component (if applicable):
[root@localhost ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 1.4.3.26-1.el6sam_splice-Headpin
subscription-manager: 1.8.22-1.el5
python-rhsm: 1.8.18-1.el5


How reproducible:
always

Steps to Reproduce:
1. Make sure the dates of server and client have no big time drift.

(1) the server time
[root@samserv ~]# date
Wed Apr 23 07:02:37 EDT 2014

(2) the client time
[root@localhost ~]# date
Wed Apr 23 07:03:11 EDT 2014

2. Remove rhsm.log on client

[root@localhost ~]# rm -f /var/log/rhsm/rhsm.log 

3. Make response from the server. 

[root@localhost ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 1.4.3.26-1.el6sam_splice-Headpin
subscription-manager: 1.8.22-1.el5
python-rhsm: 1.8.18-1.el5

4. Check the rhsm.log for clock info.

[root@localhost ~]# grep -i "clock" /var/log/rhsm/rhsm.log -B2
2014-04-23 07:04:25,686 [DEBUG]  @connection.py:415 - Making request: GET /sam/api/
2014-04-23 07:04:25,796 [DEBUG]  @connection.py:434 - Response status: 200
2014-04-23 07:04:25,797 [WARNING]  @connection.py:438 - Clock skew detected, please check your system time
--
2014-04-23 07:04:25,799 [DEBUG]  @connection.py:415 - Making request: GET /sam/api/status
2014-04-23 07:04:25,827 [DEBUG]  @connection.py:434 - Response status: 200
2014-04-23 07:04:25,827 [WARNING]  @connection.py:438 - Clock skew detected, please check your system time

Actual results:
As step 4.

Expected results:
There is no 'Clock skew detected' warning in step 4.

Additional info:

Comment 1 Carter Kozak 2014-05-14 21:04:40 UTC

This is really a python-rhsm bug.

fixed in python-rhsm commit:

commit b597dae53aacf2d8a307b77b7f38756ce3ee6860
Author: ckozak <ckozak>
Date:   Wed May 14 15:22:06 2014 -0400

    1090350: fix time drift detection

Comment 2 RHEL Program Management 2014-05-14 21:19:05 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 3 RHEL Program Management 2014-05-14 22:18:28 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 4 Sharath Dwaral 2014-06-24 20:34:24 UTC

Version:

# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 0.9.20-1
subscription-manager: 1.11.3-6.el5
python-rhsm: 1.11.3-4.el5

Verification:

1)  Restart TOMCAT on server
    # systemctl restart tomcat
2)  Client
    # date
    Tue Jun 24 16:14:25 EDT 2014
3)  Server
    # date
    Tue Jun 24 16:14:16 EDT 2014
4)  Client
    # rm -rf /var/log/rhsm/rhsm.log
    # test -f /var/log/rhsm/rhsm.log
    # echo $?
    1         <<<<<<<  asserting file does not exist

    # subscription-manager version
    server type: Red Hat Subscription Management
    subscription management server: 0.9.20-1
    subscription-manager: 1.11.3-6.el5
    python-rhsm: 1.11.3-4.el5
 
    # grep -i "clock" /var/log/rhsm/rhsm.log -B2
                     <<<<<<<  no output
    ------------------------------------------


VERIFIED

Comment 7 errata-xmlrpc 2014-09-16 00:22:39 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1225.html