Bug 987272

Summary:	Dist-geo-rep : geo-rep checkpoint works but takes utc time for start time and local time for finish time.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Vijaykumar Koppad <vkoppad>
Component:	geo-replication	Assignee:	Bug Updates Notification Mailing List <rhs-bugs>
Status:	CLOSED ERRATA	QA Contact:	Vijaykumar Koppad <vkoppad>
Severity:	medium	Docs Contact:
Priority:	high
Version:	2.1	CC:	aavati, amarts, bbandari, csaba, grajaiya, rhs-bugs, vagarwal
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.4.0.39rhs-1	Doc Type:	Bug Fix
Doc Text:	Previously, the geo-replication's 'checkpoint now' option used to set the 'UTC' time in status, where as the CLI output used to be human readable local time. Now, with the current update release, CLI sets the epoch value, and while showing data to user, just logs everything in local time, solving dependency on UTC time.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-27 15:29:49 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:	1019515

Description Vijaykumar Koppad 2013-07-23 06:49:14 UTC

Description of problem: Checkpoint gives correct information about whether it has synced file to slave before checkpoint, but it takes utc time for start time and local time for finish while displaying.



Version-Release number of selected component (if applicable):3.4.0.12rhs.beta5-2.el6rhs.x86_64


How reproducible: Happens every time 


Steps to Reproduce:
1.create and start a geo-rep relationship between master and slave. 
2.create some data on the master.
3.set the checkpoint using geo-rep config and check the status. 

Actual results: It shows utc time for start time and local time for finish time.


Expected results: It should show proper time consistently 


Additional info:

[root@shaktiman ~]# gluster v geo master 10.70.43.23::imaster status
NODE                        MASTER    SLAVE                   HEALTH                                                                              UPTIME
---------------------------------------------------------------------------------------------------------------------------------------------------------------
shaktiman.blr.redhat.com    master    10.70.43.23::imaster    Stable  | checkpoint as of 2013-07-23 06:27:51 completed at 2013-07-23 11:58:23     00:00:54
snow.blr.redhat.com         master    10.70.43.23::imaster    Stable  | checkpoint as of 2013-07-23 06:27:51 not reached yet                      00:01:10
spartacus.blr.redhat.com    master    10.70.43.23::imaster    Stable  | checkpoint as of 2013-07-23 06:27:51 not reached yet                      00:01:10
stark.blr.redhat.com        master    10.70.43.23::imaster    Stable  | checkpoint as of 2013-07-23 06:27:51 completed at 2013-07-23 11:58:16     00:01:01

Comment 2 Amar Tumballi 2013-08-01 10:12:30 UTC

Csaba, can you please have a look on this ASAP. We need to have all the 'time' to be in UTC in the code (so failover-failback should be seemless).

Comment 3 Amar Tumballi 2013-11-02 17:25:40 UTC

https://code.engineering.redhat.com/gerrit/#/c/15089/

Comment 4 Vijaykumar Koppad 2013-11-05 10:52:16 UTC

It tried it on the build glusterfs-3.4.0.39rhs-1, it shows correct time but, the Bug 1025358 is still there.

Comment 5 Vijaykumar Koppad 2013-11-12 11:01:22 UTC

verified on the build glusterfs-3.4.0.43rhs-1. This is how checkpoint output looks now.

 
MASTER NODE                MASTER VOL    MASTER BRICK      SLAVE                  STATUS     CHECKPOINT STATUS                                                           CRAWL STATUS           
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
redcell.blr.redhat.com     master        /bricks/brick1    10.70.43.174::slave    Active     checkpoint as of 2013-11-12 16:24:17 is completed at 2013-11-12 16:24:38    Changelog Crawl        
redcloak.blr.redhat.com    master        /bricks/brick2    10.70.43.76::slave     Passive    N/A                                                                         N/A                    
redwood.blr.redhat.com     master        /bricks/brick4    10.70.42.151::slave    Passive    N/A                                                                         N/A                    
redlake.blr.redhat.com     master        /bricks/brick3    10.70.43.135::slave    Active     checkpoint as of 2013-11-12 16:24:17 is completed at 2013-11-12 16:24:38    Changelog Crawl

Comment 7 errata-xmlrpc 2013-11-27 15:29:49 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-2013-1769.html